Software Application Development - Recent Threads

RE: microZed : compiling u-boot image (and creating BOOT.BIN)

adielement — Mon, 02 Jun 2025 09:22:29 GMT

[quote userid="2121" url="~/products/devtools/avnetboardscommunity/avnetboard-forums/f/software-application-development/34234/microzed-compiling-u-boot-image-and-creating-boot-bin/125853"]
http://microzed.org/content/u-boot-wont-boot[/quote]

the link you provided does not respond now. I need to resolve same issue. can you elaborate please?

microZed : compiling u-boot image (and creating BOOT.BIN)

Former Member — Sun, 30 Aug 2015 19:28:08 GMT

I cloned the u-boot.git from xilinx and compiled it

[om@hexcore (v2015.2)/export/space/xilinx/src/u-boot-xlnx.git]
[791]$ ls u-boot*
2.3M u-boot* 4.0K u-boot.lds 1.2M u-boot.srec*
408K u-boot.bin* 372K u-boot.map

I created a .BIF file.
$ cat u-boot0.bif
the_ROM_image:
{
t[bootloader]/export/space/XXXX/workspace/microzed-fsbl/Debug/microzed-fsbl.elf
t/export/space/XXXX/microzed-sd-images/system.bit
t/export/space/xilinx/src/u-boot-xlnx.git/uImage.bin
}

Created BOOT.BIN
$ bootgen -image ./u-boot0.bif -o BOOT.BIN -w -log

When I boot this image, from FSBL I get the following message

.....
DMA Done !

FPGA Done !
In FsblHookAfterBitstreamDload function
Partition Number: 2
Header Dump
Image Word Len: 0x000195B6
Data Word Len: 0x000195B6
Partition Word Len:0x000195B6
Load Addr: 0x00000000
Exec Addr: 0x00000000
Partition Start: 0x000858C0
Partition Attr: 0x00000010
Partition Checksum Offset: 0x00000000
Section Count: 0x00000001
Checksum: 0xFFF2E3AC
Application
Handoff Address: 0x00000000
In FsblHookBeforeHandoff function
No Execution Address JTAG handoff

Obviously, the image does not have a load/exec address associated with.

uImage.bin is in fact the renamed binary u-boot.img.

[792]$ file uImage.bin
uImage.bin: u-boot legacy uImage, U-Boot 2015.04 for zynq board, Firmware/ARM, Firmware Image (Not compressed), 415384 bytes, Sun Aug 30 11:35:51 2015, Load Address: 0x04000000, Entry Point: 0x04000000, Header CRC: 0x9B6F14AF, Data CRC: 0xAA06E3B8

in uImage.bin, the entry point as well as load address is defined. But bootgen seems to ignore these two parameters.

How are you people compiling u-boot and creating the BOOT.BIN image? How to specify the load and entry points in the bootgen parameter list / bif file?

Thanks
BlueDev

Zynq FSBL is unable to Load BOOT.bin from user selected EMMC offset sector (partition)

adielement — Mon, 19 May 2025 09:29:43 GMT

I am working on Zynq-7030 custom board, (software: Vivado 2019.1 → SDK 2019.1).

I have successfully accessed emmc (mmc1 in my case). Created partitions and made understanding of all emmc related commands. My board has two boot modes. One is for SD card and other is QSPI boot.

To load images from EMMC, I need to store bootloader at QSPI (since boot mode is QSPI), so that bootloader boots first and then proceeds to other images loading, that are placed at emmc.

I want to separately load boot.bin, kernel image, dtb and rootfs for each partition of emmc, based on whatever user selects at bootup. In simple words, there should be a user code that asks from user to select the partition to boot from. Say partition 3 is selected, the boot.bin , kernel image, dtb and rootfs corresponding that partition 3 will be booted up and others will not be booted.

I did research on this and found that BootROM allows FSBL to boot from QSPI to OCM. Now I am stuck in customizing FSBL to take user input and then load corresponding images. I made a simple design in Vivado and enabled only EMMC (mmc1/ sd1) and disabled SD (mmc0/sd0) then generated fsbl.elf from SDK. The fsbl.elf is generated by default method, so it does not take user input and then can load corresponding images according to that user input.

I need way out for this. I have beginner level expertise in embedded C so I need help in how to read the offset sector of EMMC to laod BOOT.bin (that was stored using dd command in the EMMC).

Is my understanding of this approach is correct or I need to adapt alternate for this? If it is correct then I will appreciate help in FSBL code customization.

RE: Zynq FSBL is unable to Load BOOT.bin from user selected EMMC offset sector (partition)

tony56887 — Tue, 27 May 2025 19:01:21 GMT

Primary boot from QSPI with only fsbl, which then hands off to boot from eMMC as secondary boot with full image. Sounds like you have this understood and I also believe this part is achievable.

But what you need is user prompt and the ability to select which image/partition to load out of multiple partitions on the eMMC? This seems more advanced, and is not provided easily as default functionality by xilinx that i'm aware of. If it's possible you would need to customize your fsbl. I would recommend asking about this on the Xilinx forums.

RE: Zynq FSBL is unable to Load BOOT.bin from user selected EMMC offset sector (partition)

adielement — Tue, 27 May 2025 05:59:01 GMT

tony56887 do you have any idea on this?

RE: Zynq FSBL is unable to Load BOOT.bin from user selected EMMC offset sector (partition)

adielement — Tue, 20 May 2025 07:12:42 GMT

Can anyone please help me with this. I am stuck in it for many days.

RE: Zynq FSBL cannot read BOOT.bin from SD card

iksevas — Fri, 16 May 2025 04:10:45 GMT

Have you tried something simple like Hello World and create BOOTIMAGE for that. It should be super simple to do.

another option is to look at MicroZed Chronicles articles as they will walk you through creating a successful bootable design.

Also, have you followed the getting started guide to prove to yourself that this works? This would be with a known good design.

Zynq FSBL cannot read BOOT.bin from SD card

Former Member — Wed, 24 Sep 2014 09:05:52 GMT

Hello,

I also posted my problem in the Xilinx forums (http://forums.xilinx.com/t5/Embedded-Linux/Zynq-FSBL-cannot-read-BOOT-bin-from-SD-card/m-p/522631/highlight/false), but as they couldn't help me yet and it also might be a MicroZed related problem, I'm posting it here now as well.

I have a MicroZed board with a Zynq 7020. I created a Project in Vivado and applied the board definition files provided here: http://zedboard.org/support/documentation/1519. Then I created a FSBL project in the SDK based on that hardware project. As a minimal example I generated a bootimage using the FSBL I generated and the u-boot.elf from the SD card image provided by Avnet, from the same link as above. I enabled the debug output of the FSBL and it tells me this:

Xilinx First Stage Boot Loader
Release 2014.2 Sep 22 2014-14:34:28
Devcfg driver initialized
Silicon Version 3.1
Boot mode is SD
SD: rc= 0
SD: Unable to open file BOOT.BIN: 3
SD_INIT_FAIL
FSBL Status = 0xA009

This Boot Mode Doesn't Support Fallback
In FsblHookFallback function

I am able to boot from the original BOOT.bin provided by Avnet, so neither my SD card, nor my MicroZed should be broken. As suggested in related threads, I also verified that the CD and WP pins are configured right and that the SD card clock is set to 50MHz. I tried routing the WP pin to an EMIO without any success. I also tried it with and without a .bit file. Is there anything else I could try?

Thanks,
Alain

RE: Zynq FSBL cannot read BOOT.bin from SD card

adielement — Fri, 16 May 2025 03:39:25 GMT

panasonic. it's sdhc

RE: Zynq FSBL cannot read BOOT.bin from SD card

iksevas — Thu, 15 May 2025 16:25:04 GMT

What type of SD card are you using? Must be SDHC type. I like using SDHC from Sandisk Class 10.

RE: Zynq FSBL cannot read BOOT.bin from SD card

adielement — Thu, 15 May 2025 11:18:27 GMT

I have same issue. Zynq FSBL cannot load SD Card BOOT.bin. I am getting following error

Xilinx First Stage Boot Loader
Release 2019.1 May 15 2025-15:52:49
Devcfg driver initialized
Silicon Version 3.1
Booting Device is MMC
SD: rc= 0
MMC Init Done
Flash Base Address: 0xE0100000
Reboot status register: 0x60400000
Multiboot Register: 0x0000C000
Image Start Address: 0x00000000
Partition Header Offset:0x00000C80
Partition Count: 3
Partition Number: 0
Header Dump
Image Word Len: 0x00007002
Data Word Len: 0x00007002
Partition Word Len:0x00007002
Load Addr: 0x00000000
Exec Addr: 0x00000000
Partition Start: 0x000005C0
Partition Attr: 0x00000010
Partition Checksum Offset: 0x00000000
Section Count: 0x00000001
Checksum: 0xFFFEA7E8
Application
Handoff Address: 0x00000000
In FsblHookBeforeHandoff function
No Execution Address JTAG handoff

How can I fix this issue. I need to further move towards booting EMMC BOOT.bin in place of SD card BOOT.bin, after resolving this issue.
Any help in this regard is highly appreciated.

RE: Mysterious syntax error with "set" command in TCL script

padudle — Thu, 09 May 2024 12:15:59 GMT

I think you should make that a relative pathname like ./temp/workspace/system_build.xsa for better portability.

Sometimes putting the path in {} brackets helps. I think it tells Xilinx TCL to convert to the native path format of the local machine.

Mysterious syntax error with "set" command in TCL script

quadzilla — Mon, 06 May 2024 13:49:29 GMT

Another Linux vs Windows issue. We have a TCL script that works under Linux when we use "vitis -s <scriptname>", but it gives us problems at the following line under Windows. Any idea what's going wrong here?

RE: Mysterious syntax error with "set" command in TCL script

quadzilla — Mon, 06 May 2024 15:23:05 GMT

Found the problem. A co-worker let me astray when he said we should use "vitis -s". I had to dig deeper to learn that this is only for Python scripts. In othe words, it was a documentation error on his part. Sorry for the confusion, and thanks everyone.

RE: Mysterious syntax error with "set" command in TCL script

Jan Cumps — Mon, 06 May 2024 15:12:59 GMT

yes but that's not /temp/workspace

RE: Mysterious syntax error with "set" command in TCL script

quadzilla — Mon, 06 May 2024 14:45:38 GMT

Nope. Those are the very first lines.

Could Vitis not be invoking the TCL interpreter? I suppose so, but I wouldn't know how this could happen or why.

RE: Mysterious syntax error with "set" command in TCL script

shabaz — Mon, 06 May 2024 14:12:00 GMT

Are there any TCL commands above the snippet you supplied? Maybe the TCL interpreter isn't invoked and Windows is executing it as a different script, throwing the error. You could test with other TCL commands. It's been a decade since I last used TCL so I cannot remember a single TCL command any more : (

RE: Mysterious syntax error with "set" command in TCL script

quadzilla — Mon, 06 May 2024 14:00:13 GMT

Since you asked, this is what Notepad++ shows me. I don't see anything unusual there.

RE: Mysterious syntax error with "set" command in TCL script

quadzilla — Mon, 06 May 2024 13:56:46 GMT

No, c:/temp/workspace definitely exists.

RE: Mysterious syntax error with "set" command in TCL script

Jan Cumps — Mon, 06 May 2024 13:55:54 GMT

/temp/workspace is most likely not a windows root directory.

RE: Mysterious syntax error with "set" command in TCL script

dyessgg — Mon, 06 May 2024 13:53:55 GMT

I'm assuming you're moving the file between the platforms in a way that converts the line endings.

It would be helpful to see a few lines above and below the offending line.

Maybe try turning on your editor's option to visualize "white space" characters. There might be something lurking there Windows doesn't like.

RE: Build errors, petalinux 2022.2, u96v2_sbc_base_2022_2.bsp

minita — Sun, 05 May 2024 22:59:14 GMT

Hello, at the end I did fix my issues, I had to copy the avnet files /u96v2-sbc.conf to the Yocto machine list of Petalinux.

I had another issue which was fixed with a library missing in my Ubuntu machine.

But you are right, that seems to be the better way to do the Petalinux pipeline process. Now, that I understand it more.

Build errors, petalinux 2022.2, u96v2_sbc_base_2022_2.bsp

rgallic — Thu, 02 Mar 2023 15:05:55 GMT

I am seeing many errors when trying to build a petalinux project using u96v2_sbc_base_2022_2.bsp.

First error is:

rsync: link_stat "/opt/pkg/petalinux/2022.2/components/misc/yocto_machines/u96v2-sbc.conf" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1207) [sender=3.1.3]

I can find u96v2-sbc.conf in directory ./project-spec/meta-avnet/conf/machine/u96v2-sbc.conf.

Do I need to copy this to /opt/pkg/petalinux/2022.2/components/misc/yocto_machines/ ?

Next is a warning:

WARNING: /home/developer/u96v2_sbc_base_2022_2/project-spec/meta-avnet/recipes-apps/factest-launcher/factest-launcher.bb: Unable to get checksum for factest-launcher SRC_URI entry factest-launcher.sh: file could not be found

Followed by:

WARNING: cmake-3.21.1-r0 do_package_write_rpm_setscene: Failed to fetch URL file://1c/2a/sstate:cmake:cortexa72-cortexa53-xilinx-linux:3.21.1:r0:cortexa72-cortexa53:7:1c2afefcb6e91e36c93f739dbcefbfbad6c908b3ff78153003ab3651ef81f3d3_package_write_rpm.tgz.siginfo;downloadfilename=1c/2a/sstate:cmake:cortexa72-cortexa53-xilinx-linux:3.21.1:r0:cortexa72-cortexa53:7:1c2afefcb6e91e36c93f739dbcefbfbad6c908b3ff78153003ab3651ef81f3d3_package_write_rpm.tgz.siginfo, attempting MIRRORS if available
ERROR: cmake-3.21.1-r0 do_package_write_rpm_setscene: Fetcher failure: Unable to find file file://1c/2a/sstate:cmake:cortexa72-cortexa53-xilinx-linux:3.21.1:r0:cortexa72-cortexa53:7:1c2afefcb6e91e36c93f739dbcefbfbad6c908b3ff78153003ab3651ef81f3d3_package_write_rpm.tgz.siginfo;downloadfilename=1c/2a/sstate:cmake:cortexa72-cortexa53-xilinx-linux:3.21.1:r0:cortexa72-cortexa53:7:1c2afefcb6e91e36c93f739dbcefbfbad6c908b3ff78153003ab3651ef81f3d3_package_write_rpm.tgz.siginfo anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: whetstone-1.2-r0 do_populate_lic_setscene: Failed to fetch URL file://9c/a2/sstate:whetstone::1.2:r0::7:9ca2225568727487f5a1ef1ebc4175a179bc0bcc64335ad596ff49d3179a630f_populate_lic.tgz.siginfo;downloadfilename=9c/a2/sstate:whetstone::1.2:r0::7:9ca2225568727487f5a1ef1ebc4175a179bc0bcc64335ad596ff49d3179a630f_populate_lic.tgz.siginfo, attempting MIRRORS if available
ERROR: whetstone-1.2-r0 do_populate_lic_setscene: Fetcher failure: Unable to find file file://9c/a2/sstate:whetstone::1.2:r0::7:9ca2225568727487f5a1ef1ebc4175a179bc0bcc64335ad596ff49d3179a630f_populate_lic.tgz.siginfo;downloadfilename=9c/a2/sstate:whetstone::1.2:r0::7:9ca2225568727487f5a1ef1ebc4175a179bc0bcc64335ad596ff49d3179a630f_populate_lic.tgz.siginfo anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: cpufrequtils-008-r5 do_package_qa_setscene: Failed to fetch URL file://25/24/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:252444a1ac5305b43a92253533a8c421b932e84f69611bfe5f1314f836aea409_package_qa.tgz.siginfo;downloadfilename=25/24/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:252444a1ac5305b43a92253533a8c421b932e84f69611bfe5f1314f836aea409_package_qa.tgz.siginfo, attempting MIRRORS if available
ERROR: cpufrequtils-008-r5 do_package_qa_setscene: Fetcher failure: Unable to find file file://25/24/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:252444a1ac5305b43a92253533a8c421b932e84f69611bfe5f1314f836aea409_package_qa.tgz.siginfo;downloadfilename=25/24/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:252444a1ac5305b43a92253533a8c421b932e84f69611bfe5f1314f836aea409_package_qa.tgz.siginfo anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: cpufrequtils-008-r5 do_package_write_rpm_setscene: Failed to fetch URL file://ff/6c/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:ff6c93769a8b05714727b28455aa9401c1850fc1d470d863744bf518d7f356ef_package_write_rpm.tgz.siginfo;downloadfilename=ff/6c/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:ff6c93769a8b05714727b28455aa9401c1850fc1d470d863744bf518d7f356ef_package_write_rpm.tgz.siginfo, attempting MIRRORS if available
ERROR: cpufrequtils-008-r5 do_package_write_rpm_setscene: Fetcher failure: Unable to find file file://ff/6c/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:ff6c93769a8b05714727b28455aa9401c1850fc1d470d863744bf518d7f356ef_package_write_rpm.tgz.siginfo;downloadfilename=ff/6c/sstate:cpufrequtils:cortexa72-cortexa53-xilinx-linux:008:r5:cortexa72-cortexa53:7:ff6c93769a8b05714727b28455aa9401c1850fc1d470d863744bf518d7f356ef_package_write_rpm.tgz.siginfo anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: cpufrequtils-008-r5 do_populate_lic_setscene: Failed to fetch URL file://bc/07/sstate:cpufrequtils::008:r5::7:bc0720160359303365bdcff2452660f93d388ecaf517791f630e2b8280a4cfb0_populate_lic.tgz.siginfo;downloadfilename=bc/07/sstate:cpufrequtils::008:r5::7:bc0720160359303365bdcff2452660f93d388ecaf517791f630e2b8280a4cfb0_populate_lic.tgz.siginfo, attempting MIRRORS if available
ERROR: cpufrequtils-008-r5 do_populate_lic_setscene: Fetcher failure: Unable to find file file://bc/07/sstate:cpufrequtils::008:r5::7:bc0720160359303365bdcff2452660f93d388ecaf517791f630e2b8280a4cfb0_populate_lic.tgz.siginfo;downloadfilename=bc/07/sstate:cpufrequtils::008:r5::7:bc0720160359303365bdcff2452660f93d388ecaf517791f630e2b8280a4cfb0_populate_lic.tgz.siginfo anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: lighttpd-1.4.59-r0 do_packagedata_setscene: Failed to fetch URL file://72/b7/sstate:lighttpd:cortexa72-cortexa53-xilinx-linux:1.4.59:r0:cortexa72-cortexa53:7:72b767ebb5b45d493d2a710804abeae65aac0e41b2cd5f14b610aa4e6817a62d_packagedata.tgz.siginfo;downloadfilename=72/b7/sstate:lighttpd:cortexa72-cortexa53-xilinx-linux:1.4.59:r0:cortexa72-cortexa53:7:72b767ebb5b45d493d2a710804abeae65aac0e41b2cd5f14b610aa4e6817a62d_packagedata.tgz.siginfo, attempting MIRRORS if available
ERROR: lighttpd-1.4.59-r0 do_packagedata_setscene: Fetcher failure: Unable to find file file://72/b7/sstate:lighttpd:cortexa72-cortexa53-xilinx-linux:1.4.59:r0:cortexa72-cortexa53:7:72b767ebb5b45d493d2a710804abeae65aac0e41b2cd5f14b610aa4e6817a62d_packagedata.tgz.siginfo;downloadfilename=72/b7/sstate:lighttpd:cortexa72-cortexa53-xilinx-linux:1.4.59:r0:cortexa72-cortexa53:7:72b767ebb5b45d493d2a710804abeae65aac0e41b2cd5f14b610aa4e6817a62d_packagedata.tgz.siginfo anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: whetstone-1.2-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/whetstone/1.2-r0/temp/log.do_package_write_rpm_setscene.27713
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-benchmark/whetstone/whetstone_1.2.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: lmsensors-3.6.0-r0 do_package_qa_setscene: No sstate archive obtainable, will run full task instead.
WARNING: lmsensors-3.6.0-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/lmsensors/3.6.0-r0/temp/log.do_package_write_rpm_setscene.27812
WARNING: lmsensors-3.6.0-r0 do_populate_lic_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/lmsensors/3.6.0-r0/temp/log.do_populate_lic_setscene.27820
WARNING: libnet-1.2-rc3-r0 do_package_qa_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/libnet/1.2-rc3-r0/temp/log.do_package_qa_setscene.27828
WARNING: libnet-1.2-rc3-r0 do_populate_lic_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/libnet/1.2-rc3-r0/temp/log.do_populate_lic_setscene.27847
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/lmsensors/3.6.0-r0/temp/log.do_package_qa_setscene.27800
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-connectivity/libnet/libnet_1.2-rc3.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-bsp/lm_sensors/lmsensors_3.6.0.bb:do_populate_lic_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-connectivity/libnet/libnet_1.2-rc3.bb:do_populate_lic_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-bsp/lm_sensors/lmsensors_3.6.0.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-bsp/lm_sensors/lmsensors_3.6.0.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: libnet-1.2-rc3-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/libnet/1.2-rc3-r0/temp/log.do_package_write_rpm_setscene.27834
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-connectivity/libnet/libnet_1.2-rc3.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: ocl-icd-2.3.0-r0 do_populate_lic_setscene: No sstate archive obtainable, will run full task instead.
WARNING: opencl-clhpp-2.0.15+gitAUTOINC+f7237f3799-r0 do_package_qa_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/ocl-icd/2.3.0-r0/temp/log.do_populate_lic_setscene.27905
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/opencl-clhpp/2.0.15+gitAUTOINC+f7237f3799-r0/temp/log.do_package_qa_setscene.27906
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/ocl-icd_2.3.0.bb:do_populate_lic_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/opencl-clhpp_git.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
WARNING: ocl-icd-2.3.0-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/ocl-icd/2.3.0-r0/temp/log.do_package_write_rpm_setscene.27904
WARNING: opencl-clhpp-2.0.15+gitAUTOINC+f7237f3799-r0 do_populate_lic_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/opencl-clhpp/2.0.15+gitAUTOINC+f7237f3799-r0/temp/log.do_populate_lic_setscene.27914
WARNING: ocl-icd-2.3.0-r0 do_package_qa_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/ocl-icd/2.3.0-r0/temp/log.do_package_qa_setscene.27897
WARNING: opencl-clhpp-2.0.15+gitAUTOINC+f7237f3799-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/opencl-clhpp/2.0.15+gitAUTOINC+f7237f3799-r0/temp/log.do_package_write_rpm_setscene.27907
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/ocl-icd_2.3.0.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/ocl-icd_2.3.0.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/opencl-clhpp_git.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/opencl-clhpp_git.bb:do_populate_lic_setscene) failed with exit code '1' - real task will be run instead
WARNING: linux-firmware-1_20211216-r0 do_packagedata_setscene: Failed to fetch URL file://b6/d9/sstate:linux-firmware:all-xilinx-linux:20211216:r0:allarch:7:b6d9ba067b54e4c67964bc57b4d205cc2befc598b5e5b61747025d753b38d229_packagedata.tgz.siginfo;downloadfilename=b6/d9/sstate:linux-firmware:all-xilinx-linux:20211216:r0:allarch:7:b6d9ba067b54e4c67964bc57b4d205cc2befc598b5e5b61747025d753b38d229_packagedata.tgz.siginfo, attempting MIRRORS if available
ERROR: linux-firmware-1_20211216-r0 do_packagedata_setscene: Fetcher failure: Unable to find file file://b6/d9/sstate:linux-firmware:all-xilinx-linux:20211216:r0:allarch:7:b6d9ba067b54e4c67964bc57b4d205cc2befc598b5e5b61747025d753b38d229_packagedata.tgz.siginfo;downloadfilename=b6/d9/sstate:linux-firmware:all-xilinx-linux:20211216:r0:allarch:7:b6d9ba067b54e4c67964bc57b4d205cc2befc598b5e5b61747025d753b38d229_packagedata.tgz.siginfo anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: linux-firmware-1_20211216-r0 do_packagedata_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/all-xilinx-linux/linux-firmware/1_20211216-r0/temp/log.do_packagedata_setscene.27927
WARNING: iptraf-ng-1.1.4-r0 do_package_write_rpm_setscene: Failed to fetch URL file://13/0c/sstate:iptraf-ng:cortexa72-cortexa53-xilinx-linux:1.1.4:r0:cortexa72-cortexa53:7:130c01f7801c30fde366c2cf30c8e2a3998ffe19458626890269288780062d4e_package_write_rpm.tgz;downloadfilename=13/0c/sstate:iptraf-ng:cortexa72-cortexa53-xilinx-linux:1.1.4:r0:cortexa72-cortexa53:7:130c01f7801c30fde366c2cf30c8e2a3998ffe19458626890269288780062d4e_package_write_rpm.tgz, attempting MIRRORS if available
ERROR: iptraf-ng-1.1.4-r0 do_package_write_rpm_setscene: Fetcher failure: Unable to find file file://13/0c/sstate:iptraf-ng:cortexa72-cortexa53-xilinx-linux:1.1.4:r0:cortexa72-cortexa53:7:130c01f7801c30fde366c2cf30c8e2a3998ffe19458626890269288780062d4e_package_write_rpm.tgz;downloadfilename=13/0c/sstate:iptraf-ng:cortexa72-cortexa53-xilinx-linux:1.1.4:r0:cortexa72-cortexa53:7:130c01f7801c30fde366c2cf30c8e2a3998ffe19458626890269288780062d4e_package_write_rpm.tgz anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: nodejs-14.17.1-r0 do_package_write_rpm_setscene: Failed to fetch URL file://34/fa/sstate:nodejs:cortexa72-cortexa53-xilinx-linux:14.17.1:r0:cortexa72-cortexa53:7:34fa991c1f59b42174c7b7197c09029f794580d9f00ddbe6abe9e6beb9b1487b_package_write_rpm.tgz;downloadfilename=34/fa/sstate:nodejs:cortexa72-cortexa53-xilinx-linux:14.17.1:r0:cortexa72-cortexa53:7:34fa991c1f59b42174c7b7197c09029f794580d9f00ddbe6abe9e6beb9b1487b_package_write_rpm.tgz, attempting MIRRORS if available
ERROR: nodejs-14.17.1-r0 do_package_write_rpm_setscene: Fetcher failure: Unable to find file file://34/fa/sstate:nodejs:cortexa72-cortexa53-xilinx-linux:14.17.1:r0:cortexa72-cortexa53:7:34fa991c1f59b42174c7b7197c09029f794580d9f00ddbe6abe9e6beb9b1487b_package_write_rpm.tgz;downloadfilename=34/fa/sstate:nodejs:cortexa72-cortexa53-xilinx-linux:14.17.1:r0:cortexa72-cortexa53:7:34fa991c1f59b42174c7b7197c09029f794580d9f00ddbe6abe9e6beb9b1487b_package_write_rpm.tgz anywhere. The paths that were searched were:
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
/home/developer/u96v2_sbc_base_2022_2/build/sstate-cache
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/core/meta/recipes-kernel/linux-firmware/linux-firmware_20211216.bb:do_packagedata_setscene) failed with exit code '1' - real task will be run instead
WARNING: opencl-headers-git-r0 do_populate_lic_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/opencl-headers/git-r0/temp/log.do_populate_lic_setscene.27937
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/opencl-headers_git.bb:do_populate_lic_setscene) failed with exit code '1' - real task will be run instead
WARNING: nodejs-14.17.1-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/nodejs/14.17.1-r0/temp/log.do_package_write_rpm_setscene.27951
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs_14.17.1.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: iptraf-ng-1.1.4-r0 do_populate_lic_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/iptraf-ng/1.1.4-r0/temp/log.do_populate_lic_setscene.27940
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-devtools/iptraf/iptraf-ng_1.1.4.bb:do_populate_lic_setscene) failed with exit code '1' - real task will be run instead
WARNING: nodejs-14.17.1-r0 do_package_qa_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/nodejs/14.17.1-r0/temp/log.do_package_qa_setscene.27941
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs_14.17.1.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
WARNING: iptraf-ng-1.1.4-r0 do_package_qa_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/iptraf-ng/1.1.4-r0/temp/log.do_package_qa_setscene.27938
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-devtools/iptraf/iptraf-ng_1.1.4.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
WARNING: opencl-headers-git-r0 do_package_qa_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/opencl-headers/git-r0/temp/log.do_package_qa_setscene.27933
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/opencl-headers_git.bb:do_package_qa_setscene) failed with exit code '1' - real task will be run instead
WARNING: iptraf-ng-1.1.4-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/iptraf-ng/1.1.4-r0/temp/log.do_package_write_rpm_setscene.27939
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-devtools/iptraf/iptraf-ng_1.1.4.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead
WARNING: opencl-headers-git-r0 do_package_write_rpm_setscene: No sstate archive obtainable, will run full task instead.
ERROR: Logfile of failure stored in: /home/developer/u96v2_sbc_base_2022_2/build/tmp/work/cortexa72-cortexa53-xilinx-linux/opencl-headers/git-r0/temp/log.do_package_write_rpm_setscene.27936
WARNING: Setscene task (/home/developer/u96v2_sbc_base_2022_2/components/yocto/layers/meta-openembedded/meta-oe/recipes-core/opencl/opencl-headers_git.bb:do_package_write_rpm_setscene) failed with exit code '1' - real task will be run instead

I stopped the build here.

Has anyone been able to get a clean build on Petalinux 2022.2 using this BSP?

Why use Linux instead of Windows?

quadzilla — Fri, 03 May 2024 20:05:25 GMT

I have seen people recommend doing development under Linux rather than Windows. Can anyone give me a list of reasons for or against using Linux for the development environment? I'd like to present a case to my bosses.

RE: Why use Linux instead of Windows?

DAB — Sun, 05 May 2024 19:23:17 GMT

I use Windows for most of my work, though since I have been using the Rpi boards, I have conceded that Linux is not as bad as the old Unix OS I avoided like the plague.

Over the last few years I have seen a convergence in IDE formats that make it more easy to move back and forth between the environments.

As others have said, for software development, you probably want to stick with the same environment that the final product will reside.

Cross platform issues will always exist.

As for the old Unix, I can tell you many horror stories.

I sent a team to Australia, after we had told them the specific system configuration they needed for our software.

The team arrived, four that the Australians were using something else.

They did their best to get it installed, but finally handed them the software, told them that if they ever get the right environment to install it and give them a call.

I also listened to one of the head Astronomy professors at the University of Arizona who swore he would never develop another software tool on Unix because every 6 months, everyone of his users got a new Unix update and his team had to do hundreds of modifications to get things working again.

But then I can also point to issues similar issues with Windows base software.

Though we could run our software on multiple Windows releases without problems.