can't boot up the PS on ZCU102 Rev1.1 board

[bwtang]

Thank you for your detailed tutorial. It helps me a lot to follow your work. Until now, I have finished the long building process. I successfully built the BOOT.bin & image.ub and load them into my SDcard. But when I powered on my board, it just printed two sentences "Xilinx Zynq MP First Stage Boot Loader \n Release 2017.1 Aug 16 2018 - 17:25:43\n" and then blocked. I used the same version Vivado, SDK, Petalinux and BSP, so I'm confused why it happened.
Then, I found a discussion about the same problem on Xilinx forum. I guess the root cause is the version of my board. My version is "ZCU102 Revision 1.1". It may be newer than your board. The older FSBL or pmu.elf may not work on the new board. So I used the pre-built BOOT.bin & image.ub from Xilinx wiki. This time, it started the PS linux system successfully. So I tried rebuilding with the newest BSP and Petalinux, but it reported some errors during petalinux-build process (I have correct the project config file). So I gave up this solution and tried to repackage the BOOT.bin replacing the original fsbl.elf and pmu.elf with the newest version which downloaded from the above link. This time, the u-boot executed successfully but the kernel failed. Now I have no idead about how to fix it?

[li3tuo4]

@bwtang
My board version is HW-Z1-ZCU102 revision 1.1.
I guess even with the same revision number, the boards can be different in the PS due to some unknown reasons.
Anyway, it seems this issue is solved in this post.
It looks like you can just try to use a newer BSP file (this might require you to use a newer petalinux).

So I tried rebuilding with the newest BSP and Petalinux, but it reported some errors during petalinux-build process (I have correct the project config file).

What error did you get?
According to that post and your results (2019.2 version works), this might be the right way.
You basically need to configure the same things that are configured in the config files located in soft_config. And, you need to fix the device tree using .dsti file in the same folder. The things that you need to do with petalinux is in this script.

Good luck.

[bwtang]

Thanks for your reply. Like your advise, I fixed my config file and system-user.dsti (slightly different from the original file) and then rebuild PS kernel with the newest BSP (2019.2) and petalinux (2019.2). But it also reported some errors like that:

[INFO] building project
[INFO] sourcing bitbake
[INFO] generating user layers
[INFO] generating workspace directory
INFO: bitbake petalinux-user-image
Loading cache: 100% |######################################################################################################################| Time: 0:00:02
Loaded 3979 entries from dependency cache.
Parsing recipes: 100% |####################################################################################################################| Time: 0:00:13
Parsing of 2893 .bb files complete (2891 cached, 2 parsed). 3980 targets, 154 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Initialising tasks: 100% |#################################################################################################################| Time: 0:00:07
Checking sstate mirror object availability: 100% |#########################################################################################| Time: 0:16:10
Sstate summary: Wanted 165 Found 16 Missed 298 Current 765 (9% match, 83% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: device-tree-xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0 do_configure: Function failed: do_configure (log file is located at /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/temp/log.do_configure.27820)
ERROR: Logfile of failure stored in: /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/temp/log.do_configure.27820
Log data follows:
| DEBUG: Executing shell function do_configure
| MISC_ARG is  -hdf_type hdf -yamlconf /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/device-tree.yaml
| APP_ARG is  -app "device-tree"
| Using xsct from: /home/tbw/petalinux_2019.2/tools/xsct/bin/xsct
| cmd is: xsct -sdx -nodisp /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/dtgen.tcl -ws /home/tbw/tmp/test2/build/../components/plnx_workspace/device-tree -pname device-tree -rp /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/git -processor psu_cortexa53_0 -hdf /home/tbw/tmp/test2/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 64  -app "device-tree"  -hdf_type hdf -yamlconf /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/device-tree.yaml
| INFO: [Hsi 55-2053] elapsed time for repository (/home/tbw/petalinux_2019.2/tools/xsct/data/embeddedsw) loading 0 seconds
| hsi::open_hw_design: Time (s): cpu = 00:00:45 ; elapsed = 00:00:46 . Memory (MB): peak = 813.422 ; gain = 141.684 ; free physical = 4440 ; free virtual = 28283
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| WARNING: quotes to be removed or use 2018.1 version for &sata params param0..param7
| Failed to find amba_pl node !!!
| ERROR: [Hsi 55-1545] Problem running tcl command ::sw_device_tree::generate : Failed to find amba_pl node !!!
|     while executing
| "error "Failed to find $lu_node node !!!""
|     (procedure "get_node_object" line 31)
|     invoked from within
| "get_node_object amba_pl pl.dtsi"
|     invoked from within
| "create_dt_node  -name M_AXI -label M_AXI -unit_addr a0000000 -objects [get_node_object amba_pl pl.dtsi]"
|     ("eval" body line 1)
|     invoked from within
| "eval "create_dt_node ${cmd}""
|     (procedure "add_or_get_dt_node" line 183)
|     invoked from within
| "add_or_get_dt_node -n $drv_handle -l $drv_handle -u $base -d $default_dts -p $bus_node"
|     ("foreach" body line 36)
|     invoked from within
| "foreach drv_handle $ext_axi_intf {
| 			set base [string tolower [get_property BASE_VALUE $drv_handle]]
| 			set high [string tolower [get_property HIGH_V..."
|     (procedure "gen_ext_axi_interface" line 12)
|     invoked from within
| "gen_ext_axi_interface"
|     (procedure "::sw_device_tree::generate" line 21)
|     invoked from within
| "::sw_device_tree::generate device_tree"
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
| hsi::generate_target: Time (s): cpu = 00:00:17 ; elapsed = 00:00:19 . Memory (MB): peak = 822.938 ; gain = 9.516 ; free physical = 3019 ; free virtual = 27745
| generate_target failed
|     while executing
| "error "generate_target failed""
|     invoked from within
| "if {[catch {hsi generate_target -dir $project} res]} {
| 	error "generate_target failed"
| }"
|     (file "/home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/dtgen.tcl" line 38)
| WARNING: /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/temp/run.do_configure.27820:1 exit 1 from 'eval xsct -sdx -nodisp /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/dtgen.tcl -ws /home/tbw/tmp/test2/build/../components/plnx_workspace/device-tree -pname device-tree -rp /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/git -processor psu_cortexa53_0 -hdf /home/tbw/tmp/test2/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 64 ${APP_ARG} ${MISC_ARG}'
| ERROR: Function failed: do_configure (log file is located at /home/tbw/tmp/test2/build/tmp/work/zcu102_zynqmp-xilinx-linux/device-tree/xilinx-v2019.2+gitAUTOINC+a8b39cf536-r0/temp/log.do_configure.27820)
ERROR: Task (/home/tbw/petalinux_2019.2/components/yocto/source/aarch64/layers/meta-xilinx/meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3254 tasks of which 3029 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/tbw/petalinux_2019.2/components/yocto/source/aarch64/layers/meta-xilinx/meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
ERROR: Failed to build project

According the log, the root cause maybe my system-user.dsti file. Its content is:

/include/ "system-conf.dtsi"
/{
	chosen {
		bootargs = "earlycon clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait rootfstype=ext4 uio_pdrv_genirq.of_id=generic-uio";
		stdout-path = "serial0:115200n8";
	};

        htif_0: htif@a0000000 {
        #address-cells = <1>;
        #size-cells = <1>;
        compatible = "generic-uio", "uio", "uio_pdrv";
        reg = <0x0 0xa0000000 0x0 0x1000>;
        };
gpio-keys {
 sw19 {
 compatible = "gpio-keys";
 label = "sw19";
 status = "disabled";
 };
 };
 leds {
 compatible = "gpio-leds";
 heartbeat_led {
 label = "heartbeat";
 linux,default-trigger = "heartbeat";
 status = "disabled";
};
 };
};

&i2c1 {

	/* FIXME PL i2c via PCA9306 - u45 */
	/* FIXME MSP430 - u41 - not detected */
	i2c-mux@74 { /* u34 */
		i2c@0 { /* i2c mw 74 0 1 */
			/*
			 * IIC_EEPROM 1kB memory which uses 256B blocks
			 * where every block has different address.
			 *    0 - 256B address 0x54
			 * 256B - 512B address 0x55
			 * 512B - 768B address 0x56
			 * 768B - 1024B address 0x57
			 */
			eeprom: eeprom@54 { /* u23 */
				compatible = "atmel,24c08";
				reg = <0x54>;
			};
		};
	};
};

This is my first time to write .dst. I didn't understand its meaning, just copyed from original file and merged it into the default file. I know the riscv-fesvr is related to the dst file. So I want to know its meaning. Do you have some advise?

[li3tuo4]

@bwtang
This .dtsi file basically adds the device node htif and a few bootargs, to the device tree. Petalinux does not allow users to directly modify the main device tree (dst). This .dtsi file will be used by petalinux during build to merge with the main dst.

Which .hdf file did you use for your petalinux project? The hdf file should be from the vivado project (by export hardware).
In your new .dtsi file, where is the i2c device node from?

[FTGStudio]

Were you able to successfully boot on rev1.1?

[FTGStudio]

I have Petalinux 2019 installed on my system, and I am using the 2019 BSP file which is placed in my soft_config folder. when I issue make kernel_image I am receiving the following.

michael@michael-builldmachine:~/git/rc-fpga-zcu/zcu102$ make kernel_image
bash /home/michael/git/rc-fpga-zcu/zcu102/soft_config/petalinux_bd.sh petalinux_proj
INFO: Create project: petalinux_proj
INFO: New project successfully created in /home/michael/git/rc-fpga-zcu/zcu102/petalinux_proj
'/home/michael/git/rc-fpga-zcu/zcu102/soft_config/config' -> '/home/michael/git/rc-fpga-zcu/zcu102/petalinux_proj/project-spec/configs/config'
INFO: Getting hardware description...
INFO: Rename rocketchip_wrapper.hdf to system.hdf
[INFO] generating Kconfig for project
[INFO] silentconfig project
ERROR: Failed to silentconfig project component 
ERROR: Failed to config project.
ERROR: Get hw description Failed!.

Is there something that I need to refactor in order to get BOOT.bin and image.ub to build for rev1.1?

[li3tuo4]

@FTGStudio Yes, my board is also a rev1.1 and it works perfectly. However, the scripts are made and tested for 2017.1 Vivado and petalinux. Hence, you need to do some necessary changes in the scripts for newer Vivado and petalinux.

ERROR: Get hw description Failed!.

This error seems to say that the hardware definition file .hdf is not correct.
You might need to recreate your .hdf file from vivado project by using export hardware command, after the vivado project is implemented successfully. Make sure the correct .hdf file is put into the place, which is used by petalinux_bd.sh.

Cheers,
Tuo

[FTGStudio]

I was able to export an updated version of the hardware description file via 2019 vivado. I also built the project with 2019 Petalinux. When I generate my BOOT.bin and image.ub file and load it onto an SD card I see the following serial output from the zcu102 rev1.1 board

Xilinx Zynq MP First Stage Boot Loader
Release 2019.2   Jan 13 2020  -  18:18:43

It seems to be hanging out the FSBL. Any advice from this point on?

[li3tuo4]

@FTGStudio
According to this post:

On further digging, we stumble upon following thread on Xilinx forum
https://forums.xilinx.com/t5/Embedded-Boot-and-Configuration/Booting-ZCU-102-from-SD-Card/td-p/926649

According to it for ZCU102 rev 1.1, newer boards have a new SODIMM that requires 2018.3 FSBL in order to properly work. 2018.3 FSBL is also back compatible for older boards. Newer ZCU102 board MUST use the 2018.3 FSBL, i.e. 2018.2 or earlier FSBL won't boot.

The official Xilinx answer sheet for this issue is in here.

Cheers

[FTGStudio]

I'm attempting to build the fesvr-zynq right now, and it cannot seem to link "fesvr". I am following the instructions from the README. Any advice?

/opt/Xilinx/SDK/2019.1/gnu/aarch64/lin/aarch64-linux/bin/../lib/gcc/aarch64-linux-gnu/8.2.0/../../../../aarch64-linux-gnu/bin/ld: cannot find -lfesvr

[botaichang]

Hi @bwtang , have you resolved this problem, I met the same problem as you met.

[botaichang]

I substitute the fsbl.elf and pmufw.elf with the newer one and generate the BOOT.bin and image.ub, but when i boot with sd card, it will halt on starting kernel and cannot enter into the file system.

[botaichang]

Hi @FTGStudio , have you boot the arm linux successfully ?

[li3tuo4]

@FTGStudio
Did you build riscv-fesvr successfully? Is the $(fesvr-lib) built correctly? This tutorial might be helpful.

[botaichang]

I'm attempting to build the fesvr-zynq right now, and it cannot seem to link "fesvr". I am following the instructions from the README. Any advice?

/opt/Xilinx/SDK/2019.1/gnu/aarch64/lin/aarch64-linux/bin/../lib/gcc/aarch64-linux-gnu/8.2.0/../../../../aarch64-linux-gnu/bin/ld: cannot find -lfesvr

This is because when you compile the fesvr you didn't use aarch64 gcc to compile, you can check your fesvr-zynq Makefile to make sure the gcc host is aarch64 while not x86-64 gcc.