Date   

Current high bug count owners for Yocto Project 3.2

Stephen Jolley
 

All,

Below is the list as of top 50 bug owners as of the end of WW22 of who have open medium or higher bugs and enhancements against YP 3.2.   There are 106 possible work days left until the final release candidates for YP 3.2 needs to be released.

Who

Count

richard.purdie@...

30

david.reyna@...

19

bluelightning@...

17

bruce.ashfield@...

12

akuster808@...

11

kai.kang@...

10

ross@...

9

Qi.Chen@...

9

mark.morton@...

8

JPEWhacker@...

8

randy.macleod@...

7

trevor.gamblin@...

7

changqing.li@...

6

timothy.t.orling@...

6

michael@...

5

pbarker@...

4

rpjday@...

4

mingli.yu@...

4

yi.zhao@...

3

jon.mason@...

3

kexin.hao@...

3

hongxu.jia@...

3

raj.khem@...

3

jaewon@...

2

seebs@...

2

mostthingsweb@...

2

dl9pf@...

2

alejandro@...

2

akuster@...

2

chee.yang.lee@...

2

anuj.mittal@...

2

kergoth@...

2

jpuhlman@...

2

mark.hatle@...

2

ycnakajsph@...

2

alex.kanavin@...

2

liu.ming50@...

1

denis@...

1

limon.anibal@...

1

maxime.roussinbelanger@...

1

zhe.he@...

1

naveen.kumar.saini@...

1

jackie.huang@...

1

jason.wessel@...

1

joe.slater@...

1

sakib.sajal@...

1

matthew.zeng@...

1

kai.ruhnau@...

1

yang.wang@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley
 

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (6/2) 

 

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

When            Monthly from 8am to 8:30am on the first Tuesday Pacific Time

Where           Zoom Meeting: https://zoom.us/j/990892712

 

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them.  The world should have view access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Eclipse GDB setup issues; can't determine cause for SIGSEGV

Bryan Evenson
 

All,

I have a AT91SAM9G25 system that has been idle for a couple years (running morty, yocto version 2.2.1) and I am working on updating to the latest Yocto production branch. Before I get there, I'm trying to confirm the old setup and I'm having problems with remote debugging. I know there have been changes since yocto version 2.7 for debugging support, so I want to make sure I can get the old setup to work first prior to changing everything. I'm looking for assistance in tracking down my debug issues.

My stable production image is based off of core-image-minimal, with a few additional packages for our proprietary applications (proprietary applications are written in C). I also have a development image, based off of our production image, with the following additions:

IMAGE_FEATURES += "package-management dev-pkgs eclipse-debug allow-empty-password empty-root-password"

IMAGE_INSTALL += " \
#same additional packages as production image \
#"-dbg" version of proprietary applications \
gdbserver \
"
# Strip python from the image to reduce the image size
PACKAGE_EXCLUDE = "python"

I have the Eclipse Yocto plugin installed and it is setup to use the SDK that I have built based on the development image. I've confirmed that I can start a debug session on one of our proprietary applications. I can set breakpoints and run the debugger. However, the debugger always stops at the first call to uuid_compare with a SIGSEGV. The last line in the call stack states "<symbol is not available> 0x00000000". From my understanding, the stack pointer is getting set to NULL when uuid_compare is getting called. If I stop the debugger and just run the application on the hardware, the application runs without errors. I have confirmed with syslog messages that I do not have the same NULL stack pointer issue when I run the application outside of the debugger.

Any suggestions on where to start looking? I don't see any obvious possible causes and I don't know where to start looking for the problem.

Thanks,
Bryan


Re: QA completion for completed autobuilder build (yocto-2.7.4.rc2)

akuster
 

On 6/1/20 12:25 AM, Jain, Sangeeta wrote:
Hello all,

This is the full report for yocto-2.7.4.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
Thank you.

- Armin

======= Summary ========
No high milestone defects.
No new defects are found in this cycle.

Note: Few failures are observed. These are setup issues, not real yocto issue.

Thanks,
Sangeeta


#yocto #raspberrypi SND_BCM2835 doesn't load if vc4-kms-v3d-overlay set #yocto #raspberrypi

Bastien0530 <bastien.gallet-pesenti@...>
 

Hi,
I was struggling for days about playing a simple wav file with aplay on a raspberry 3b+ jack 3.5mm output.

I had built-in snd_bcm2835 and all the required modules and when booting the raspberry, I couldn't play any song :
------------------------------------------------------------------

root@raspberrypi3:~# aplay /usr/share/sounds/alsa/Noise.wav
aplay: main:828: audio open error: No such file or directory
------------------------------------------------------------------

Also, there was only VC4 HDMI playback devices :
------------------------------------------------------------------
root@raspberrypi3:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: vc4hdmi [vc4-hdmi], device 0: MAI PCM vc4-hdmi-hifi-0 [MAI PCM vc4-hdmi-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
------------------------------------------------------------------

And can't find SND_BCM2835 with the command "lsmod | grep snd_bcm2835".

However, I finally figured out that this error was brought by the vc4-kms-v3d-overlay. (Thanks to this topic : https://github.com/raspberrypi/linux/issues/3181).
If I comment the "dtoverlay=vc4-kms-v3d" line in config.txt, then all is fine and I can see the SND_BCM2835 as Alsa playback device :
------------------------------------------------------------------
root@raspberrypi3:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 7/7
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
------------------------------------------------------------------

So, I would like to know if there is any recipe or image config to disable vc4-kms-v3d-overlay?

As it is set in the meta-raspberry/conf/machine/include/rpi-base.inc, I cannot make any bbappend recipe to modify this behavior.

What would be the better solution?

Best regards,
Bastien


QA completion for completed autobuilder build (yocto-2.7.4.rc2)

Sangeeta Jain
 

Hello all,

This is the full report for yocto-2.7.4.rc2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.
No new defects are found in this cycle.

Note: Few failures are observed. These are setup issues, not real yocto issue.

Thanks,
Sangeeta


Re: Yocto dunfell - strange error when building npm package without dependence

Jean-Marie Lemetayer
 

Hi Edson,

You're right. I have seen seen this too. I have already created a bug
to track this issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13901

For now, as a workaround, you can just delete the npmsw:// line in
the generated recipe (and the shrinkwrap file).

Best Regards,
Jean-Marie


On Sat, May 30, 2020 at 4:07 PM Edson Seabra
<edson.seabra@zpesystems.com> wrote:

Hi, all

I used recipetool to create the recipe for NPM packages

If the npm package has dependence(s) it works great.

But if not, the error below happens.

I just add a fake dependence in npm-shrinkwrap.json then it works

# cat google-protobuf/npm-shrinkwrap.json
{
"name": "google-protobuf",
"version": "3.3.0",
"lockfileVersion": 1,
"requires": true,
"dependencies": {
"nan": {
"version": "2.14.1",
"resolved": "https://registry.npmjs.org/nan/-/nan-2.14.1.tgz";,
"integrity": "sha512-isWHgVjnFjh2x2yuJ/tj3JbwoHu3UC2dX5G/88Cm24yB6YopVgxvBObDY7n5xW6ExmFhJpSEQqFPvq9zaXc8Jw=="
}
}
}

Another way to make it work is to replace the npmsw with file in SRC_URI

======== nan.bb =======
SRC_URI = " \
npm://registry.npmjs.org;package=nan;version=${PV} \
file://npm-shrinkwrap.json;subdir=npm \
"
S = "${WORKDIR}/npm"

inherit npm

======= google-protobuf.bb ==========

SRC_URI = " \
npm://registry.npmjs.org/;package=google-protobuf;version=${PV} \
npmsw://${THISDIR}/${BPN}/npm-shrinkwrap.json \
"

S = "${WORKDIR}/npm"

inherit npm

====== error ======

ERROR: google-protobuf-3.3.0-r0 do_fetch: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Logfile of failure stored in: /home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/log.do_fetch.33980
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/edson/ng-trunk/meta-extended/meta-oe/recipes-oe/node/nodejs_12.14.1.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['nodejs-native', 'pkgconfig-native', 'zlib-native', 'brotli-native', 'openssl-native', 'xz-native', 'quilt-native', 'python3-native', 'icu-native', 'c-ares-native', 'libuv-native', 'gnu-config-native', 'libtool-native', 'automake-native', 'autoconf-native', 'ninja-native', 'cmake-native', 'gettext-minimal-native', 'readline-native', 'libffi-native', 'bzip2-native', 'sqlite3-native', 'libtirpc-native', 'util-linux-native', 'gdbm-native', 'libnsl2-native', 'unzip-native', 'texinfo-dummy-native', 'm4-native', 're2c-native', 'expat-native', 'ncurses-native', 'curl-native', 'libpcre2-native', 'libcap-ng-native']
| NOTE: Skipping as already exists in sysroot: []
| DEBUG: sed -e 's:^[^/]*/:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native/:g' /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/nodejs-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pkgconfig-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/openssl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/quilt-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/python3-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/icu-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/gnu-config-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libtool-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/automake-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/autoconf-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/ncurses-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/curl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libpcre2-native/fixmepath | xargs sed -i -e 's:FIXMESTAGINGDIRTARGET:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot:g; s:FIXMESTAGINGDIRHOST:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native:g' -e 's:FIXME_PSEUDO_SYSROOT:/home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pseudo-native:g' -e 's:FIXME_HOSTTOOLS_DIR:/home/edson/ng-trunk/nodegrid/tmp/hosttools:g' -e 's:FIXME_PKGDATA_DIR:/home/edson/ng-trunk/nodegrid/tmp/pkgdata/genericx86-64:g' -e 's:FIXME_PSEUDO_LOCALSTATEDIR:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/pseudo/:g' -e 's:FIXME_LOGFIFO:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/fifo.33980:g'
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing python function do_fetch
| DEBUG: Executing python function base_do_fetch
| DEBUG: Python function base_do_fetch finished
| DEBUG: Python function do_fetch finished
| ERROR: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Task (/home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3501 tasks of which 3500 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Thanks in advance.

Edson Seabra

Principal Engineer

M +1 510 579 0843

E edson.seabra@zpesystems.com


46757 Fremont Blvd., Fremont, CA 94538
zpesystems.com | Request a Nodegrid Demo


Re: Can I build Yocto Arm Image without QEMU?

Alexander Kanavin
 

Qemu is also used to run target binaries during build (when there is a need to generate some data files that can only be produced by running those binaries). If you see a build of qemu-native, it will not end up in the target image.

What is your use case specifically?

Alex


On Sun, 31 May 2020 at 19:52, Олег Гаврильченко via lists.yoctoproject.org <reffum=bk.ru@...> wrote:
May I ask you to clarify, how can I do that? 
I build Yocto image for XILINX ZYNQ7 board and set MACHINE = zybo-zynq7. And then run "bitbake core-image-minimal". QEMU is downloaded, compiled and installed.


Re: Can I build Yocto Arm Image without QEMU?

Олег Гаврильченко <reffum@...>
 

May I ask you to clarify, how can I do that? 
I build Yocto image for XILINX ZYNQ7 board and set MACHINE = zybo-zynq7. And then run "bitbake core-image-minimal". QEMU is downloaded, compiled and installed.


Re: Can I build Yocto Arm Image without QEMU?

Sergei Nikulov
 



вс, 31 мая 2020 г., 14:15 Олег Гаврильченко via lists.yoctoproject.org <reffum=bk.ru@...>:
Hello!
Sorry for my English. My first language is Russian.
I have a question about build yocto image. Can I build image without build any QEMU packages? And how can I do it?

Yes, you can.
Check MACHINE variable in documentation.
You should set it to specific HW you're using.

I do not neet QEMU, I run Linux only in hardware.
Thank you for answers.
 
 


Can I build Yocto Arm Image without QEMU?

reffum@...
 

Hello!
Sorry for my English. My first language is Russian.
I have a question about build yocto image. Can I build image without build any QEMU packages? And how can I do it?
I do not neet QEMU, I run Linux only in hardware.
Thank you for answers.
 
 


Re: python3, pyscard, setuptools ModuleNotFound. Why?

Tim Orling
 



On Sat, May 30, 2020 at 5:14 AM Mauro Ziliani <mauro@...> wrote:
Hi all.

I'd like to include pyscard from pypi in my bsp.

I'm using zeus and python3.


The recipe for pyscard is placed in recipes-devtools/python of my layer

The recipe name s python3-pyscard_1.9.9.bb

This is the recipe


# PYScard
#
#
LICENSE="LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d0227c3c90dc0a9eae8b0a64acd8c6e1"

PYPI_PACKAGE="pyscard"

You don't need this as this is the default value. 

inherit pypi setuptools3

SRC_URI[md5sum] = "a8e94032ca8dec22a6c559a7afd41998"
SRC_URI[sha256sum] =
"e6bde541990183858740793806b1c7f4e798670519ae4c96145f35d5d7944c20"


DEPENDS = " \
     swig \
This has to be swig-native. When in doubt, DEPENDS should be the -native version.

After this, you will be missing <winscard.h>, which comes from pcsc-lite recipe in meta-oe, but it didn't readily build even with RDEPENDS_${PN} += "python3-core pcsc-lite" (or pcsc-lite in DEPENDS for that matter).

You'll probably have to figure out how to tell swig where to look for the file.
 
"

Why bitbake tell this error?

Sstate summary: Wanted 5 Found 0 Missed 5 Current 168 (0% match, 97%
complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 678 of 773
(/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure)
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Started
ERROR: python3-pyscard-1.9.9-r0 do_configure: Execution of
'/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232'
failed with exit code 1:
Traceback (most recent call last):
   File "setup.py", line 31, in <module>
     from setuptools import setup, Extension
ModuleNotFoundError: No module named 'setuptools'
WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in:
/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/log.do_configure.1232
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of
'/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232'
failed with exit code 1:
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
|
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Failed
ERROR: Task
(/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 765 tasks of which 764 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Thanks all

MZ



Yocto dunfell - strange error when building npm package without dependence

Edson Seabra
 

Hi, all

I used recipetool to create the recipe for NPM packages

If the npm package has dependence(s) it works great.

But if not, the error below happens.

I just add a fake dependence in npm-shrinkwrap.json  then it works

# cat google-protobuf/npm-shrinkwrap.json
{
  "name": "google-protobuf",
  "version": "3.3.0",
  "lockfileVersion": 1,
  "requires": true,
  "dependencies": {
    "nan": {
      "version": "2.14.1",
      "resolved": "https://registry.npmjs.org/nan/-/nan-2.14.1.tgz",
      "integrity": "sha512-isWHgVjnFjh2x2yuJ/tj3JbwoHu3UC2dX5G/88Cm24yB6YopVgxvBObDY7n5xW6ExmFhJpSEQqFPvq9zaXc8Jw=="
    }
  }
}

Another way to make it work is to replace the npmsw with file in SRC_URI

======== nan.bb =======
SRC_URI = " \
    npm://registry.npmjs.org;package=nan;version=${PV} \
    file://npm-shrinkwrap.json;subdir=npm \
    "
S = "${WORKDIR}/npm"

inherit npm

======= google-protobuf.bb ==========

 SRC_URI = " \
    npm://registry.npmjs.org/;package=google-protobuf;version=${PV} \
    npmsw://${THISDIR}/${BPN}/npm-shrinkwrap.json \
    "

S = "${WORKDIR}/npm"

inherit npm

====== error ======

ERROR: google-protobuf-3.3.0-r0 do_fetch: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Logfile of failure stored in: /home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/log.do_fetch.33980
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/edson/ng-trunk/meta-extended/meta-oe/recipes-oe/node/nodejs_12.14.1.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: ['nodejs-native', 'pkgconfig-native', 'zlib-native', 'brotli-native', 'openssl-native', 'xz-native', 'quilt-native', 'python3-native', 'icu-native', 'c-ares-native', 'libuv-native', 'gnu-config-native', 'libtool-native', 'automake-native', 'autoconf-native', 'ninja-native', 'cmake-native', 'gettext-minimal-native', 'readline-native', 'libffi-native', 'bzip2-native', 'sqlite3-native', 'libtirpc-native', 'util-linux-native', 'gdbm-native', 'libnsl2-native', 'unzip-native', 'texinfo-dummy-native', 'm4-native', 're2c-native', 'expat-native', 'ncurses-native', 'curl-native', 'libpcre2-native', 'libcap-ng-native']
| NOTE: Skipping as already exists in sysroot: []
| DEBUG: sed -e 's:^[^/]*/:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native/:g' /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/nodejs-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pkgconfig-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/openssl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/quilt-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/python3-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/icu-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/gnu-config-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libtool-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/automake-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/autoconf-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/ncurses-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/curl-native/fixmepath /home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/libpcre2-native/fixmepath | xargs sed -i -e 's:FIXMESTAGINGDIRTARGET:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot:g; s:FIXMESTAGINGDIRHOST:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/recipe-sysroot-native:g' -e 's:FIXME_PSEUDO_SYSROOT:/home/edson/ng-trunk/nodegrid/tmp/sysroots-components/x86_64/pseudo-native:g' -e 's:FIXME_HOSTTOOLS_DIR:/home/edson/ng-trunk/nodegrid/tmp/hosttools:g' -e 's:FIXME_PKGDATA_DIR:/home/edson/ng-trunk/nodegrid/tmp/pkgdata/genericx86-64:g' -e 's:FIXME_PSEUDO_LOCALSTATEDIR:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/pseudo/:g' -e 's:FIXME_LOGFIFO:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/google-protobuf/3.3.0-r0/temp/fifo.33980:g'
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing python function do_fetch
| DEBUG: Executing python function base_do_fetch
| DEBUG: Python function base_do_fetch finished
| DEBUG: Python function do_fetch finished
| ERROR: Failure expanding variable TUNE_FEATURES_tune-core2-64, expression was ${TUNE_FEATURES_tune-x86-64} core2 which triggered exception RecursionError: maximum recursion depth exceeded while calling a Python object
ERROR: Task (/home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3501 tasks of which 3500 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/google-protobuf/google-protobuf_3.3.0.bb:do_fetch
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Thanks in advance.

Edson Seabra

Principal Engineer

M +1 510 579 0843

1506169147061_OutlookEmoji-1505330244060_ZPELogo_Email.png1e6c5898-d340-4c90-8c28-e559c26bc7d1.png
46757 Fremont Blvd., Fremont, CA 94538
zpesystems.com | Request a Nodegrid Demo


python3, pyscard, setuptools ModuleNotFound. Why?

Mauro Ziliani
 

Hi all.

I'd like to include pyscard from pypi in my bsp.

I'm using zeus and python3.


The recipe for pyscard is placed in recipes-devtools/python of my layer

The recipe name s python3-pyscard_1.9.9.bb

This is the recipe


# PYScard
#
#
LICENSE="LGPL-2.1"
LIC_FILES_CHKSUM = "file://LICENSE;md5=d0227c3c90dc0a9eae8b0a64acd8c6e1"

PYPI_PACKAGE="pyscard"


inherit pypi setuptools3

SRC_URI[md5sum] = "a8e94032ca8dec22a6c559a7afd41998"
SRC_URI[sha256sum] = "e6bde541990183858740793806b1c7f4e798670519ae4c96145f35d5d7944c20"


DEPENDS = " \
    swig \
"

Why bitbake tell this error?

Sstate summary: Wanted 5 Found 0 Missed 5 Current 168 (0% match, 97% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
NOTE: Running task 678 of 773 (/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure)
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Started
ERROR: python3-pyscard-1.9.9-r0 do_configure: Execution of '/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232' failed with exit code 1:
Traceback (most recent call last):
  File "setup.py", line 31, in <module>
    from setuptools import setup, Extension
ModuleNotFoundError: No module named 'setuptools'
WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in: /home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/log.do_configure.1232
Log data follows:
| DEBUG: Executing shell function do_configure
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/mauro/yocto/zeus/qt10-build/tmp-glibc/work/core2-32-oe-linux/python3-pyscard/1.9.9-r0/temp/run.do_configure.1232' failed with exit code 1:
| Traceback (most recent call last):
|   File "setup.py", line 31, in <module>
|     from setuptools import setup, Extension
| ModuleNotFoundError: No module named 'setuptools'
| WARNING: exit code 1 from a shell command.
|
NOTE: recipe python3-pyscard-1.9.9-r0: task do_configure: Failed
ERROR: Task (/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 765 tasks of which 764 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/mauro/yocto/zeus/sources/meta-custom/recipes-devtools/python/python3-pyscard_1.9.9.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Thanks all

MZ


error while adding meta-python,meta-gnone,meta-multimedia layer #linux #raspberrypi #yocto

Pankaj Vinadrao Joshi
 

Hi,
when i am trying to add meta-python  from meta-openembedded i am getting following error i have kept meta-openembedded,meta-raspberrypi into same branch dunfell
/Raspberrypi4-yocto$ bitbake-layers add-layer /home/ritesh/source_meta/meta-openembedded/meta-python/
NOTE: Starting bitbake server...
Traceback (most recent call last):
  File "/home/ritesh/Yocto_practice/poky/bitbake/bin/bitbake-layers", line 95, in <module>
    ret = main()
  File "/home/ritesh/Yocto_practice/poky/bitbake/bin/bitbake-layers", line 63, in main
    tinfoil.prepare(True)
  File "/home/ritesh/Yocto_practice/poky/bitbake/lib/bb/tinfoil.py", line 414, in prepare
    self.run_command('parseConfiguration')
  File "/home/ritesh/Yocto_practice/poky/bitbake/lib/bb/tinfoil.py", line 470, in run_command
    raise TinfoilCommandFailed(result[1])
bb.tinfoil.TinfoilCommandFailed: Traceback (most recent call last):
  File "/home/ritesh/Yocto_practice/poky/bitbake/lib/bb/command.py", line 74, in runCommand
    result = command_method(self, commandline)
  File "/home/ritesh/Yocto_practice/poky/bitbake/lib/bb/command.py", line 275, in parseConfiguration
    command.cooker.parseConfiguration()
  File "/home/ritesh/Yocto_practice/poky/bitbake/lib/bb/cooker.py", line 433, in parseConfiguration
    self.handleCollections(self.data.getVar("BBFILE_COLLECTIONS"))
  File "/home/ritesh/Yocto_practice/poky/bitbake/lib/bb/cooker.py", line 1225, in handleCollections
    raise CollectionError("Errors during parsing layer configuration")
bb.cooker.CollectionError: Errors during parsing layer configuration

this is bblayer.conf

[1:06 PM, 5/29/2020] ¶£: my  bblayer.conf is as following
[1:06 PM, 5/29/2020] ¶£: POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
 
BBPATH = "${TOPDIR}"
BBFILES ?= ""
 
BBLAYERS ?= " \
  /home/pankajjoshi/Yocto_practice/poky/meta \
  /home/pankajjoshi/Yocto_practice/poky/meta-poky \
  /home/pankajjoshi/Yocto_practice/poky/meta-yocto-bsp \
  /home/pankajjoshi/source_meta/meta-raspberrypi \
  /home/pankajjoshi/source_meta/meta-openembedded/meta-oe \
  /home/pankajjoshi/source_meta/meta-openembedded/meta-filesystems \
  /home/pankajjoshi/source_meta/meta-openembedded/meta-networking \
  "

why i am getting an error while adding layer into??





Generating a genericx86_64 - bad hddimg #yocto

fnx_qt
 

Hello,

I'm trying to generate a simple genericx86_64 with Yocto 2.7 Warrior. Problem is that my hddimg is completely messed up upon generation.
I have not made any particular configuration apart from adding layers and modiying the local.conf file. Here is the content of the hddimg file:


% fdisk -l core-image-minimal-genericx86-64.hddimg images/genericx86-64 wagner
Disk core-image-minimal-genericx86-64.hddimg: 535.4 MiB, 561386496 bytes, 1096458 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x20ac7dda

Device Boot Start End Sectors Size Id Type
core-image-minimal-genericx86-64.hddimg1 3224498923 3657370039 432871117 206.4G 7 HPFS/NTFS/exFAT
core-image-minimal-genericx86-64.hddimg2 3272020941 5225480974 1953460034 931.5G 16 Hidden FAT16
core-image-minimal-genericx86-64.hddimg3 0 0 0 0B 6f unknown
core-image-minimal-genericx86-64.hddimg4 50200576 974536369 924335794 440.8G 0 Empty


Here is the bblayers.conf file:

% cat bblayers.conf build/conf wagner
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
${TOPDIR}/../sources/poky/meta \
${TOPDIR}/../sources/poky/meta-poky \
${TOPDIR}/../sources/poky/meta-yocto-bsp \
${TOPDIR}/../sources/meta-openembedded/meta-oe \
${TOPDIR}/../sources/meta-openembedded/meta-python \
${TOPDIR}/../sources/meta-openembedded/meta-networking \
${TOPDIR}/../sources/meta-openembedded/meta-filesystems \
${TOPDIR}/../sources/meta-intel \
${TOPDIR}/../sources/meta-virtualization \
"


And here is the local.conf file (only the uncommented lines):

MACHINE ??= "genericx86-64"
DL_DIR ?= "/home/username/workspace/downloads"
SSTATE_DIR ?= "/home/username/workspace/sstate-cache"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-system-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"

# Include SystemD and SystemCTL
DISTRO_FEATURES_append = " systemd virtualization"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"

# Added Docker container to the image
IMAGE_INSTALL_append = " docker python3-docker-compose"
 



Do anyone have an idea of what the problem is ?


Re: Yocto,core-image-minimal for RPI4 #linux #yocto

Siddhartha V
 

Am soory paul,

 But i was actually trying to check if sdimage is generated or not. I was unaware of . wic. bz2 image. So suggested the above commands.

Sorry pankaj. 


Thanks 
Siddhartha V

On Fri, 29 May, 2020, 2:13 PM Paul Barker, <pbarker@...> wrote:
On Fri, 29 May 2020 at 09:23, Siddhartha V <Siddhuvgowda.18695@...> wrote:
>
> Please follow below steps to check the image.
>
> In build directory :
> to check the sdimage for installing on SD card.
>
> $: ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg
>
> Check the image by running above command and then follow the steps i mentioned previously.

Siddhartha, you're confusing the issue here by giving inaccurate advice.

The original command posted by Pankaj was nearly correct: `sudo dd
if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb`. The only
issue is that the data in the wic.bz2 file needs to be de-compressed
before writing to an SD card.

I recommend installing bmap-tools and using that to copy the data, it
handles decompression automatically and uses the block map in the
wic.bmap file to allow it to only write blocks which actually contain
data (saving lots of time that would be otherwise wasted writing
blocks of zeros). You can run `sudo bmaptool copy
core-image-minimal-raspberrypi4.wic.bz2 /dev/sdb`.

Thanks,
Paul

--
Paul Barker
Konsulko Group


Re: Yocto,core-image-minimal for RPI4 #linux #yocto

 

On Fri, 29 May 2020 at 09:23, Siddhartha V <Siddhuvgowda.18695@gmail.com> wrote:

Please follow below steps to check the image.

In build directory :
to check the sdimage for installing on SD card.

$: ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg

Check the image by running above command and then follow the steps i mentioned previously.
Siddhartha, you're confusing the issue here by giving inaccurate advice.

The original command posted by Pankaj was nearly correct: `sudo dd
if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb`. The only
issue is that the data in the wic.bz2 file needs to be de-compressed
before writing to an SD card.

I recommend installing bmap-tools and using that to copy the data, it
handles decompression automatically and uses the block map in the
wic.bmap file to allow it to only write blocks which actually contain
data (saving lots of time that would be otherwise wasted writing
blocks of zeros). You can run `sudo bmaptool copy
core-image-minimal-raspberrypi4.wic.bz2 /dev/sdb`.

Thanks,
Paul

--
Paul Barker
Konsulko Group


Re: Yocto,core-image-minimal for RPI4 #linux #yocto

Siddhartha V
 

Please follow below steps to check the image. 

In build directory :
to check the sdimage for installing on SD card.

$: ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg

Check the image by running above command and then follow the steps i mentioned previously. 

Regards, 
Siddhartha V 

On Fri, 29 May, 2020, 1:17 PM Pankaj Vinadrao Joshi, <Pankaj.VJ@...> wrote:
Hi,
i dont have image with .rpi-sdimg i have image with 

core-image-minimal-raspberrypi4.wic.bz2
core-image-minimal-raspberrypi4.wic.bmap
core-image-minimal-raspberrypi4.testdata.json
core-image-minimal-raspberrypi4.tar.bz2  
core-image-minimal-raspberrypi4.manifest  
core-image-minimal-raspberrypi4.ext3

dont have core-image-base-raspberrypi3.rpi-sdimg


From: siddhartha v <siddhuvgowda.18695@...>
Sent: Friday, May 29, 2020 1:07 PM
To: Pankaj Vinadrao Joshi <Pankaj.VJ@...>
Cc: yocto@... <yocto@...>
Subject: Re: [yocto] Yocto,core-image-minimal for RPI4 #linux #yocto
 
Hello Pankaj,

  Try below mentioned steps, Hope it helps you, (there my image was"core-image-base-raspberrypi3.rpi-sdimg"  replace it by your image )


plug sd card to pc then

$: lsblk
$: sudo umount /dev/sdb*

$: sudo dd if=tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg of=/dev/sdb bs=4M

  >> This task will take some time and at the end we will get the output something similar(not exact it depends on build files) to below :

        46+0 records in
46+0 records out
192937984 bytes (193 MB, 184 MiB) copied, 10.2155 s, 18.9 MB/s


$: sync
$: sudo umount /dev/sdb*


Best Regards,
Siddhartha V

On Fri, May 29, 2020 at 12:48 PM Pankaj Vinadrao Joshi <pankaj.vj@...> wrote:
Hi,
I have built the image for raspberrypi4 and i have got the following images 
 
 
core-image-minimal.env                                                              rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo
core-image-minimal-raspberrypi4-20200518130120.rootfs.ext3                          rpi-ft5406.dtbo
core-image-minimal-raspberrypi4-20200518130120.rootfs.manifest                      rpi-ft5406-raspberrypi4.dtbo
 
core-image-minimal-raspberrypi4-20200518130120.rootfs.tar.bz2                       rpi-hwup-image.env
 
core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bmap                      rpi-hwup-image-
 
raspberrypi4-20200521111428.rootfs.ext3
 
core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bz2                       rpi-hwup-image-
 
raspberrypi4-20200521111428.rootfs.manifest
 
core-image-minimal-raspberrypi4-20200518130120.testdata.json                        rpi-hwup-image-
 
raspberrypi4-20200521111428.rootfs.tar.bz2
 
core-image-minimal-raspberrypi4.ext3                                                rpi-hwup-image-raspberrypi4-
 
20200521111428.rootfs.wic.bmap
 
core-image-minimal-raspberrypi4.manifest                                            rpi-hwup-image-raspberrypi4-
 
20200521111428.rootfs.wic.bz2
 
core-image-minimal-raspberrypi4.tar.bz2                                    
core-image-minimal-raspberrypi4.testdata.json                                       
core-image-minimal-raspberrypi4.wic.bmap                                            
 
core-image-minimal-raspberrypi4.wic.bz2                    
 
and  i am trying to copy core-image-minimal-raspberrypi4.wic.bz2 by using
 
$sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb 
 
but my image is not getting copied into sd card(used two sd cards ,tried formatting with FAT,Linux),i am missing anything ,do i need to copy anything else with this core-image-minimal.
which extension of image i should use to bringup my RPI4??
 
Thanks!



--
Thanks and Regards.
Siddhartha V.
 
[EXT]


Re: Yocto,core-image-minimal for RPI4 #linux #yocto

Pankaj Vinadrao Joshi
 

Hi,
i dont have image with .rpi-sdimg i have image with 

core-image-minimal-raspberrypi4.wic.bz2
core-image-minimal-raspberrypi4.wic.bmap
core-image-minimal-raspberrypi4.testdata.json
core-image-minimal-raspberrypi4.tar.bz2  
core-image-minimal-raspberrypi4.manifest  
core-image-minimal-raspberrypi4.ext3

dont have core-image-base-raspberrypi3.rpi-sdimg


From: siddhartha v <siddhuvgowda.18695@...>
Sent: Friday, May 29, 2020 1:07 PM
To: Pankaj Vinadrao Joshi <Pankaj.VJ@...>
Cc: yocto@... <yocto@...>
Subject: Re: [yocto] Yocto,core-image-minimal for RPI4 #linux #yocto
 
Hello Pankaj,

  Try below mentioned steps, Hope it helps you, (there my image was"core-image-base-raspberrypi3.rpi-sdimg"  replace it by your image )


plug sd card to pc then

$: lsblk
$: sudo umount /dev/sdb*

$: sudo dd if=tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg of=/dev/sdb bs=4M

  >> This task will take some time and at the end we will get the output something similar(not exact it depends on build files) to below :

        46+0 records in
46+0 records out
192937984 bytes (193 MB, 184 MiB) copied, 10.2155 s, 18.9 MB/s


$: sync
$: sudo umount /dev/sdb*


Best Regards,
Siddhartha V

On Fri, May 29, 2020 at 12:48 PM Pankaj Vinadrao Joshi <pankaj.vj@...> wrote:
Hi,
I have built the image for raspberrypi4 and i have got the following images 
 
 
core-image-minimal.env                                                              rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo
core-image-minimal-raspberrypi4-20200518130120.rootfs.ext3                          rpi-ft5406.dtbo
core-image-minimal-raspberrypi4-20200518130120.rootfs.manifest                      rpi-ft5406-raspberrypi4.dtbo
 
core-image-minimal-raspberrypi4-20200518130120.rootfs.tar.bz2                       rpi-hwup-image.env
 
core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bmap                      rpi-hwup-image-
 
raspberrypi4-20200521111428.rootfs.ext3
 
core-image-minimal-raspberrypi4-20200518130120.rootfs.wic.bz2                       rpi-hwup-image-
 
raspberrypi4-20200521111428.rootfs.manifest
 
core-image-minimal-raspberrypi4-20200518130120.testdata.json                        rpi-hwup-image-
 
raspberrypi4-20200521111428.rootfs.tar.bz2
 
core-image-minimal-raspberrypi4.ext3                                                rpi-hwup-image-raspberrypi4-
 
20200521111428.rootfs.wic.bmap
 
core-image-minimal-raspberrypi4.manifest                                            rpi-hwup-image-raspberrypi4-
 
20200521111428.rootfs.wic.bz2
 
core-image-minimal-raspberrypi4.tar.bz2                                    
core-image-minimal-raspberrypi4.testdata.json                                       
core-image-minimal-raspberrypi4.wic.bmap                                            
 
core-image-minimal-raspberrypi4.wic.bz2                    
 
and  i am trying to copy core-image-minimal-raspberrypi4.wic.bz2 by using
 
$sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb 
 
but my image is not getting copied into sd card(used two sd cards ,tried formatting with FAT,Linux),i am missing anything ,do i need to copy anything else with this core-image-minimal.
which extension of image i should use to bringup my RPI4??
 
Thanks!



--
Thanks and Regards.
Siddhartha V.
 
[EXT]

3041 - 3060 of 52576