Ionel

What have you tried? What issues have you encounter? The process is documented here https://docs.amd.com/r/2023.1-English/ug1144-petalinux-tools-reference-guide/petalinux-boot-jtag-Options

Do you have a dhcp or use static ip? why 10.48.30.255 a broadcast address is used for GW?

Did you recognized the data or you were expecting to be filled with zeros instead of random data? If there is still a issue check this <for 32-bit Cortex-A9 Zynq>: https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841683/Linux+Reserved+Memory Also you can try to reserve a different section of memory.

1. check if BOOT.BIN contains al needed binaries: petalinux-package --boot --fpga --fsbl --u-boot --force 2. Try connect early to console to view fsbl messages if any. 3. make sure you umount partitions before you unplug the sdcard (everything was written to the boot partition)

Elf file may not be usable on RPU

It looks like the u-booot is working just fine you can check by pressing a key when this message is shown during boot: Also this message: Leads me to think that there is either some issues with the u-boot image(FIT) or the control was already passed to the loaded kernel and the kernel device-tree or cmdline arguments are not ok to setup the console (BAUD RATE or console settings).

There is no meta-digilent layer to add a machine conf for Genesys ZU 3EG You can construct your own layer machine conf base on meta-xilinx-core/conf/machine/zynqmp-eg-generic.conf

This line most likely means that file rpu_app_r5_0 was not find in /lib/firmware/ are you sure the file to be place there is an .elf and not a plain binary file? Note: the remoteproc0 is looking for rpu_app_5_0 not searching for file rpu_app_r5_0.elf

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`

fnInitZmod is declared in reg.h and defined in reg.c the linker is not finding the .so|.o file for the reg.c

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 .

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.

If your image file is less then 16MB then you can use Xilinx hardware manage to write it to the QSPI flash The process is documented here: https://docs.xilinx.com/r/en-US/ug908-vivado-programming-debugging/Programming-Configuration-Memory-Devices

Hi @user32, A a more recent version than 2017 of Petalinux project for Cora-07S can be found here: https://github.com/Digilent/Cora-Z7-OS/tree/07S/master Some tips if you start from scratch with newer version of petalinux: Start with a simple hardware-desgin After adding the hw-description(.xsa file) to your petalinux project enable fsbl debug. Wait on serial COMx|/dev/ttyUSBx to see what is happening with the boot process BOOT.BIN file on first fat32 partition is where the fsbl is stored and the entry point of the boot process that you can control.

@ManiS As long as that image starts with a fat partition containing BOOT.BIN (includes a fsbl) the boot process should start. The rest of the process follows the image instructions. By default the boot partition should contain BOOT.BIN, boot.scr, image.ub. last two files are required for u-boot but other files can replace them. Try inspecting petalinux-sdimage.wic image. Eg. use `losetup` tool in linux or mount -o loop,offset=<bytes count> <imagefile> /mount/point To find offset use fdisk -lu <imagefile> and multiply start sector number for partition you want to mount by 512 usually 2048 or 4096 for first partition => 1048576 respectively 2097152