cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
3,250 Views
Registered: ‎10-12-2016

ZCU102 Ultrascale+ ATF hangs in SDCard boot using FSBL

Hi,

 

I'm having a very hard time trying to get an OS on the Ultrascale+ board. I've managed to do this successfully with the Zynq-7000 series, but it seems like there's a lot of extra things I seem to be missing.

 

I've used Yocto+Meta-Xilinx to bitbake all the necessary files, except for the BOOT.bin, FSBL.elf, and ATF.elf files. If I generate a BOOT.bin with:

 

- FSBL.elf

- top.bit

- u-boot.elf

 

I get the following with a kernel panic: https://gist.github.com/kratsg/ec4fe00cf9beb2bb3f1cb19f2e80dda0. So then I inquired around and it seems like I need ATF. So I ran 

bitbake arm-trusted-firmware

which I then included in my BIF

 

- FSBL.elf

- top.bit

- ATF.elf

- u-boot.elf

 

and trying to boot the board again from SD card, I see the following https://gist.github.com/kratsg/ec117ace83d1da8e30c34fb7c36e0555 where I'm not seeing a hand-off from ATF to the u-boot. It's not clear if I have ATF correct or what. Links to documentation describing the FSBL for Ultrascale+ step-by-step would be somewhat helpful as I can't find a concrete guide or working example to compare against.

 

Thanks!

 

Giordon

0 Kudos
2 Replies
Highlighted
Moderator
Moderator
3,199 Views
Registered: ‎04-17-2011

Re: ZCU102 Ultrascale+ ATF hangs in SDCard boot using FSBL

Can you copy over your .bif file here?
Regards,
Debraj
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
Highlighted
Visitor
Visitor
3,184 Views
Registered: ‎10-12-2016

Re: ZCU102 Ultrascale+ ATF hangs in SDCard boot using FSBL

the_ROM_image:
{
	[fsbl_config] a5x_x64
	[pmufw_image]pmufw.elf
	[bootloader]fsbl.elf	
	[destination_device=pl]top.bit
	[destination_cpu=a5x-0]arm-trusted-firmware.elf
	[destination_cpu=a5x-0]u-boot.elf
}

I'm using 2016.4 and the Xilinx SDK GUI to produce this. Is this related to 

https://forums.xilinx.com/t5/Embedded-Linux/2016-3-ZynqMP-zcu102-Wrong-exception-level-in-ATF-BL31-after/td-p/730428 because I don't have exception levels set? I was under the assumption that it was fixed in 2016.4...?

0 Kudos