Fwd: Re: ZynqMP boot: no messages from SPL other than "Debug uart enabled"

[Major A <andras.g.major@gmail.com>]

Hi Michal,

The link I sent discusses boards that are externally identical but still 
different, even though they are all labeled Rev1.1.  My understanding is 
that there are differences between boards other than the SODIMM issue 
(from Rev1.0 to Rev1.1).  Don't you have a reasonably new board (I guess 
anything with a 2019 build date should do to test the file that you sent 
me?  I'm pretty sure you only tested it on older boards (still Rev1.1, 
but older).

Cheers,

   Andr?s


On 05/05/2020 09:58, Michal Simek wrote:
> Hi,
> 
> yes there are new sodimms for sure that's why there is separate folder
> for this board revision.
> You can try to generate psu_init for 1.1 from vivado and then ddr
> configuration should be right.
> You can also use psu_init and run memory test on the top to see if ddr
> is configured properly.
> 
> Thanks,
> Michal
> 
> On 05. 05. 20 9:43, Major A wrote:
>> Hi Michal,
>>
>> I appreciate that, thanks for your help.? I mentioned this earlier but
>> never got a reply: can this have something to do with
>>
>>
>> https://forums.xilinx.com/t5/ACAP-and-SoC-Boot-and/Booting-ZCU-102-from-SD-Card/td-p/926649
>>
>>
>> by any chance?
>>
>> Cheers,
>>
>>  ? Andr?s
>>
>>
>> On 05/05/2020 08:14, Michal Simek wrote:
>>> On 04. 05. 20 16:41, Major A wrote:
>>>> Dear Michal,
>>>>
>>>> There's no output on the console whatsoever.? I tried booting off SD
>>>> directly, and also via JTAG and your script.
>>>
>>> I am out of ideas what can be wrong. It is just working on our revision
>>> 1.1. I can only recommend you to debug it step by step and see where you
>>> end and what can be wrong.
>>> I can imagine that your zcu102 can have older memory module but it is
>>> unlikely if it is new. Or something else is broken there.
>>>
>>> Just keep in your mind that SPL is not supported official recommend boot
>>> flow and it is community driven first stage bootloader.
>>> I can help with brainstorming but you need to debug it self to find out
>>> where the problem is.
>>>
>>> Thanks,
>>> Michal
>>>
>