Booting fails for Genesys ZU-3EG image from Petalinux 2020.1 build

[Manoj Dahal]

Hi,

I have built image for Genesys ZU-3EG board (https://www.tme.eu/Document/34f661f70806c492861090265f309a71/410-383-3EG.pdf) using PetaLinux v2020.1 but while booting it fails.

I have cloned https://github.com/Digilent/Genesys-ZU-OS.git and checkout the branch 3eg/oob/next

Then followed the steps mentioned in https://docs.xilinx.com/v/u/2020.1-English/ug1144-petalinux-tools-reference-guide to build the image.

After writing the files BOOT.BIN, image.ub and boot.scr to the 1st partition of SD card, I tried to boot the device with SD card but it stuck at following lines:

[    6.868202] printk: console [ttyPS0] enabled
[    6.872666] printk: bootconsole [cdns0] disabled
[    6.872666] printk: bootconsole [cdns0] disabled
[    6.881989] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 47, base_baud = 6250000) is a xuartps
[    6.895245] of-fpga-region fpga-full: FPGA Region probed

I have attached the full log.

Any help in resolving this issue will be greatly appreciated.

Thanks & regards,

 

Manoj

 

boot_fails_zu3eg.txt

[Ionel]

From the size diference it looks like the bitstream was not included.

Use --fpga  for package command: `petalinux-package --boot --fsbl --fpga --u-boot --force`

[Manoj Dahal]

 

The next one goes little further and hangs again:
 

[    6.881077] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 47, base_baud = 6250000) is a xuartps
[    6.894331] of-fpga-region fpga-full: FPGA Region probed
[   96.998611] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[   97.004530] rcu:     2-...0: (5 ticks this GP) idle=2d2/1/0x4000000000000000 softirq=1255/1256 fqs=2614
[   97.013744]  (detected by 0, t=5255 jiffies, g=-239, q=1)
[   97.019134] Task dump for CPU 2:
[   97.022354] kworker/2:1     R  running task        0    31      2 0x0000000a
[   97.029411] Workqueue: events deferred_probe_work_func
[   97.034549] Call trace:
[   97.036992]  __switch_to+0x1c4/0x288
[   97.040564]  0xffffff887f7e4e00

This time zeroed 1st sector of SD card with following command:

sudo dd if=/dev/zero of=/dev/mmcblk0 bs=1024 count=1

And I copied boot files using rsync command and

boot_fails_zu3eg-II.txt

[Ionel]

Is there no message after `[    6.895245] of-fpga-region fpga-full: FPGA Region probed`?

The log you posted looks manually edited.
Where are log entries before [    6.268877] ?
There is no error.
If you have problems with serial console try using default settings and disable/remove any PL changes you made that are related to UART.
Maybe the system is working fine and it is the console that has a problem.

[Manoj Dahal]

Thanks for your response.

No, the logs were not manually edited before sending. It was copy pasted as is.

And I didn't make any changes in original repo. I just checked out and built.

Where do I set the default settings ?

Best regards,

Manoj

[Ionel]

If there is no edited log how do you know is failing? it just means that there in no output to the console.
branch `3eg/oob/next` is not stable and is prone to changes use `3eg/oob/master` or `3eg/master` for default settings .

[Manoj Dahal]

I have checkout `3eg/oob/master`, built the image without any changes and tried to boot the device with the new image.
And the result is same. Rather I can see some failure messages in the log this time:

unable to select a mode
device_remove: Device 'mmc@ff170000.blk' failed to remove, but children are gone
mmc fail to send stop cmd

This time, I tried to connect an Ethernet cable between the device and wifi router.
The device didn't get allocated any IP address either.

Full log attached.
It's getting dragged too far for me. Kindly help.

Bootload0314.txt

[Manoj Dahal]

I have noticed something unusual. The size of freshly built BOOT.BIN is significantly lesser than that of pre-built one genesys-zu-3eg.img (from https://github.com/Digilent/Genesys-ZU/releases/tag/3eg%2Foob%2Frelease%2Fv2.2?_ga=2.190008491.1408856705.1709925355-688906959.1707783043).

Pre-built image files list:

$ ls -lt /mnt/3eg_img/
total 86972
-rwxr-xr-x 1 root root  5275932 Mar 20  2023 BOOT.BIN
-rwxr-xr-x 1 root root     2007 Mar 20  2023 boot.scr
-rwxr-xr-x 1 root root 83775308 Mar 20  2023 image.ub

Freshly built image files list:

$ ls -lt /mnt/sd1_boot/
total 83092
-rwxr-xr-x 1 root root  1300380 Mar 14 10:45 BOOT.BIN
-rwxr-xr-x 1 root root 83778932 Mar 14 10:41 image.ub
-rwxr-xr-x 1 root root     2007 Mar 14 09:37 boot.scr

Is something wrong?
 

[Manoj Dahal]

Thanks a lot for your help!

The BOOT.BIN size looks similar now after running the command `petalinux-package --boot --fsbl --fpga --u-boot --force`.
The boot succeeds this time!

[Manoj Dahal]

Further to this, what are the proper steps to build and add an RPU Application (running on R5) to this PetaLinux image?