From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Date: Thu, 12 Mar 2020 14:31:09 +0100 Subject: ZynqMP boot: no messages from SPL other than "Debug uart enabled" In-Reply-To: <9bdb2ede-8788-a7ea-cb05-fff3188815d3@gmail.com> References: <0f9a6b47-110c-c2f8-ec40-72106ed3272d@xilinx.com> <77460fd1-f86d-fd53-66af-28d16fe395a1@gmail.com> <4fcae7a6-1156-d868-3463-424368cf7b7f@xilinx.com> <69846a06-7085-70dd-bde1-95abf870cd73@gmail.com> <87728a7f-42b5-8e3b-d5a1-5fced9d7601a@xilinx.com> <9bdb2ede-8788-a7ea-cb05-fff3188815d3@gmail.com> Message-ID: <43908655-808a-f646-a361-f7979c783409@xilinx.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, On 12. 03. 20 14:24, Major A wrote: > Hi Michal, > > Just to confirm and to eliminate any doubt: > > When I build u-boot SPL for the ZCU102, u-boot actually forces me to > supply a bl31.bin file, so that's what I did.? Apart from that, I expect > the SPL to print its welcome message (which I have yet to see) on the > UART and complain about other components (such as PMUFW, u-boot proper, > etc.) missing.? Is that correct? PMUFW needs to be loaded and can be built from SDK/VITIS or taken from petalinux. bl31 is ATF - also you can build it or take it externally. > > If it is, then there are only two components that can be wrong: u-boot > SPL and ATF (bl31.bin), am I right? > > Also, I assume that bl31.bin is incorporated into spl/boot.bin, so I > don't need to supply it externally, is that so? ATF is not the part of boot.bin. PMUFW is the part of boot.bin. > > Don't get me wrong, I already tested loads of configurations with > various incarnations of PMUFW and configuration object, etc., and never > ever have I seen the "U-Boot SPL" welcome message on the UART.? I guess > it just doesn't want to greet me for some reason or another. If you blame spl just use fsbl instead. ATF/PMUFW can be taken from petalinux to find out which component is failing for you. M