ZynqMP boot: no messages from SPL other than "Debug uart enabled"
andras.g.major at gmail.com
Thu Apr 23 11:02:04 CEST 2020
I've had to take a break because, as it turned out, my ZCU102 was
defective. Now that I have a working one, I can go on with my
frustrating quest for a bootable image.
So now that the patches to u-boot for the ZCU102 Rev. 1.1 are in git
master, I started again from scratch, building ATF, PMUFW with patch and
config object, and u-boot.
Once the builds finish, I place the files
on the SD card and try to boot. Sadly, as before, the only result I get
on the first UART channel is a line
Debug uart enabled
sometimes followed by
### ERROR ### Please RESET the board ###
but nothing else.
My suspicion is that the PMUFW or its configuration object isn't right.
I use Luca's code from here to build both:
I also found an issue here:
It appears that there are at least two incompatible subrevisions of the
board, both labeled Rev. 1.1. Could it be that the current PMUFW (or
whatever) just won't work with the current revision?
How do I figure out what the h*** is going on?
On 12/03/2020 16:22, Michal Simek wrote:
> On 12. 03. 20 15:19, Major A wrote:
>> Hi Michal,
>>> ATF is not the part of boot.bin. PMUFW is the part of boot.bin.
>> I'm confused. U-boot requires bl31.bin while building but not PMUFW
>> (unless a non-default configuration option is set). Just to confirm
>> that I'm thinking straight: ATF must be supplied in the form of a file
>> bl31.bin in the SD card root directory in order for SPL to load it?
> SD boot flow boot.bin which contains u-boot SPL and PMUFW.
> SPL looks for u-boot.itb on fat partition which is U-Boot fit image
> which contains u-boot-nodtb, ATF(bl31.bin) and dtbs.
> It means flow is PMUFW on PMU, SPL -> ATF -> U-Boot proper.
> bl31.bin is only required for u-boot.itb generation. If you don't pass
> it it won't be included in u-boot.itb.
> I haven't tested SPL-> U-Boot in EL3 but it doesn't make too much sense
More information about the U-Boot