Jump to content

Manoj Dahal

Members
  • Posts

    13
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Manoj Dahal's Achievements

Member

Member (2/4)

0

Reputation

  1. Below is memory mapping set in linker script: Do you think something needs to be changed here or elsewhere to load the .elf correctly in R5_0?
  2. I rebooted the device and tried again. This time I see different error: Mar 25 04:55:07 GenesysZU user.info kernel: [ 931.996881] remoteproc remoteproc0: powering up r5@0 Mar 25 04:55:07 GenesysZU user.info kernel: [ 932.002254] remoteproc remoteproc0: Booting fw image rpu_app_r5_0.elf, size 379744 Mar 25 04:55:07 GenesysZU user.err kernel: [ 932.016237] remoteproc remoteproc0: bad phdr da 0x100000 mem 0xd740 Mar 25 04:55:07 GenesysZU user.err kernel: [ 932.022503] remoteproc remoteproc0: Failed to load program segments: -22 Mar 25 04:55:07 GenesysZU user.err kernel: [ 932.029248] remoteproc remoteproc0: Boot failed: -22
  3. Yes it's elf file only. root@GenesysZU:/lib/firmware# ls -lt total 300 -rwxr-xr-x 1 root root 303428 Mar 20 01:10 rpu_app_r5_0.elf drwxr-xr-x 2 root root 0 Mar 18 18:30 mchp root@GenesysZU:/lib/firmware# mv rpu_app_r5_0.elf rpu_app_r5_0 root@GenesysZU:/lib/firmware# echo rpu_app_r5_0 > /sys/class/remoteproc/remoteproc0/firmware; echo start /sys/class/remoteproc/remoteproc0/state
  4. Hi, I used the platform file sw/3eg_hw_pf/hw/system_wrapper.xsa from https://digilent.com/reference/lib/exe/fetch.php?tok=3832a5&media=https%3A%2F%2Fgithub.com%2FDigilent%2FGenesys-ZU%2Freleases%2Fdownload%2F3EG%2FHELLO-WORLD%2F2020.1-2%2FGenesys-ZU-3EG-HELLO-WORLD-sw.ide.zip to build the Hello World Application rpu_app_r5_0 on R5_0 using Vitis 2020.1. Then copied the rpu_app_r5_0.elf file to /lib/firmware/ on the device. And ran it as following: echo rpu_app_r5_0 > /sys/class/remoteproc/remoteproc0/firmware echo start /sys/class/remoteproc/remoteproc0/state It does not display anything. Looking into /var/log/messages, I can see the following error: Mar 18 18:49:06 GenesysZU user.info kernel: [ 1145.985079] remoteproc remoteproc0: powering up r5@0 Mar 18 18:49:06 GenesysZU user.warn kernel: [ 1145.990094] remoteproc remoteproc0: Direct firmware load for rpu_app_r5_0 failed with error -2 Mar 18 18:49:06 GenesysZU user.err kernel: [ 1145.998712] remoteproc remoteproc0: request_firmware failed: -2 Mar 18 18:49:06 GenesysZU user.err kernel: [ 1146.004631] remoteproc remoteproc0: Boot failed: -2 I added following dtsi details to system-user.dtsi for building the linux image with PetaLinix v2020.1: / { reserved-memory { #address-cells = <2>; #size-cells = <2>; ranges; rpu0vdev0vring0: rpu0vdev0vring0@3ed40000 { no-map; reg = <0x0 0x3ed40000 0x0 0x4000>; }; rpu0vdev0vring1: rpu0vdev0vring1@3ed44000 { no-map; reg = <0x0 0x3ed44000 0x0 0x4000>; }; rpu0vdev0buffer: rpu0vdev0buffer@3ed48000 { no-map; reg = <0x0 0x3ed48000 0x0 0x100000>; }; rproc_0_reserved: rproc@3ed00000 { no-map; reg = <0x0 0x3ed00000 0x0 0x40000>; }; }; zynqmp-rpu { compatible = "xlnx,zynqmp-r5-remoteproc-1.0"; #address-cells = <2>; #size-cells = <2>; ranges; core_conf = "split"; reg = <0x0 0xFF9A0000 0x0 0x10000>; r5_0: r5@0 { #address-cells = <2>; #size-cells = <2>; ranges; memory-region = <&rproc_0_reserved>, <&rpu0vdev0buffer>, <&rpu0vdev0vring0>, <&rpu0vdev0vring1>; pnode-id = <0x7>; mboxes = <&ipi_mailbox_rpu0 0>, <&ipi_mailbox_rpu0 1>; mbox-names = "tx", "rx"; tcm_0_a: tcm_0@0 { reg = <0x0 0xFFE00000 0x0 0x10000>; pnode-id = <0xf>; }; tcm_0_b: tcm_0@1 { reg = <0x0 0xFFE20000 0x0 0x10000>; pnode-id = <0x10>; }; }; }; zynqmp_ipi1 { compatible = "xlnx,zynqmp-ipi-mailbox"; interrupt-parent = <&gic>; interrupts = <0 29 4>; xlnx,ipi-id = <7>; #address-cells = <1>; #size-cells = <1>; ranges; /* APU<->RPU0 IPI mailbox controller */ ipi_mailbox_rpu0: mailbox@ff990600 { reg = <0xff990600 0x20>, <0xff990620 0x20>, <0xff9900c0 0x20>, <0xff9900e0 0x20>; reg-names = "local_request_region", "local_response_region", "remote_request_region", "remote_response_region"; #mbox-cells = <1>; xlnx,ipi-id = <1>; }; }; }; Anything wrong? I will be grateful for any help to resolve the issue. ~Manoj
  5. Further to this, what are the proper steps to build and add an RPU Application (running on R5) to this PetaLinux image?
  6. 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!
  7. 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?
  8. 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
  9. 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
  10. 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
  11. 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
  12. Hi, Is there Genesys ZU Out-of-Box Petalinux Project github repo for supporting PetaLinux 2023.1 or 2023.2 for Genesys ZU-3EG (Zynq Ultrascale+ MPSoC ZU-3EG)? Also we need it supporting Vitis/Vivado 2023.1 or 2023.2. Though out-of-box os repo (https://github.com/Digilent/Genesys-ZU-OS) is there for PetaLinux2020.1 but it doesn't support latest Linux e.g. Ubuntu 22.04. The petalinux build fails. Kindly help if possible. Thanks, Manoj
  13. Hi, I am trying create a custom Linux image using Yocto project for the board Genesys ZU: Zynq Ultrascale+ MPSoC ZU-3EG (XCZU3EG). What should be configured in the machine type to target the build? I tried the machine type as "zcu102-zynqmp", but it didn't boot with XCZU3EG board. Any help will be greatly appreciated! Thanks, Manoj
×
×
  • Create New...