Ultra96 V2 kernel is hanging when loading root file system

Hi,

I am building the kernel from source based on the https://github.com/Xilinx/linux-xlnx kernel released by Xilinx.

I didn't find the defconfig for the ultra96 so I used the one "xilinx_zynqmp_defconfig" which is a basic configuration for the Ultrascale+.

I am wondering if there is a particular defconfig for the Ultra96 V2 that is I need to use.

It is hanging when loading root "waiting for root device /dev/mmcblk0p2". I used a uEnv.txt to load the bootargs and used root=/dev/mmcblk0p2

but I am not sure how to check what argument root should be.

from U-Boot, I was not sure if I needed to use the address "initrd" address with the initial RamDisk. I didn't know what to use for loading the RamDisk.

From what I read on a blog, root partition is temporally mounted on the initrd.

Any Ideas?

Top Replies

jafoste4 over 5 years ago in reply to nico_n04 +1

Yes that is correct. -Josh

nico_n04 over 5 years ago

update, it is hanging due to an argument I added to the bootargs "rootwait" . It is waiting for the root=/dev/mmcblk0p2.
I not sure what I need to set on the u-boot , it like it is not seen the partition where the root file is located.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
jafoste4 over 5 years ago in reply to nico_n04

Hi Nicolas,

Just to confirm, is the boot partition - Fat32 and the root partition formatted to EXT4?

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
nico_n04 over 5 years ago in reply to jafoste4

Yes, boot partition is Fat32 and the root file system is in a partition formatted as EXT4.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
nico_n04 over 5 years ago in reply to nico_n04

I built u-boot from source, I am wondering if it's missing a configuration that is not on the defconfig "avnet-Ultra96_rev1_deconfig".
where does the header "platform-top.h" AVNET is providing suppose to go? maybe my issue is in the u-boot
https://github.com/Avnet/petalinux/blob/master/configs/u-boot/platform-top.h.ultra96v2_sd_boot

I found a similar issue for other board but it didn't help. https://forums.xilinx.com/t5/Embedded-Development-Tools/Beginners-problems-with-Ultrazed-eg/td-p/800802
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
jafoste4 over 5 years ago in reply to nico_n04

Hi Nicolas,

Are you opposed to reviewing the Ultra96-V1 BSP and trying to mimic this targeting the Ultra96-V2 board?

If so, we will have an Ultra96-V2 BSP available in a couple weeks you could leverage to get past this problem.

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
nico_n04 over 5 years ago in reply to jafoste4

I have figured out the issue!!
I used the device tree configuration from Ultra96-V1 BSP. So basically I used the SDK to generate a base device tree for my PL blocks from Vivado 2018.3.
Then I built my dtb from the dts generated plus the avnet-ultra96-rev1.dtsi . This solved the issue.

I built the source u-boot with the defconfig for the ultra96 which I think it's for the version 1. I only had to modified the bootcmd parameter it was looking for from the default configuration.
I passed my boot cmd from the uEnv.txt file.

What is the differences between the Ultra96-V1 and Ultra96-V2? I have to clean up unused configuration.

thanks for your help Josh.

-Nicolas
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
jafoste4 over 5 years ago in reply to nico_n04

Hi Nicolas,

In regards to the boards BDF, the only difference will be the DDR configurations between the V1 and V2.

-Josh
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
nico_n04 over 5 years ago in reply to jafoste4

Are those DDR configurations of the BDF for the V2 provided in github https://github.com/Avnet/bdf ?
I used this configuration when I created my Vivado project, It contained the V2 BDF. I would assume they are the correct DDR configurations.

The FSBL and PMUFW was generated by Vivado based on .hdl file that was built.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
jafoste4 over 5 years ago in reply to nico_n04

Yes that is correct.

-Josh
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel