public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Major A <andras.g.major@gmail.com>
To: u-boot@lists.denx.de
Subject: ZynqMP boot: no messages from SPL other than "Debug uart enabled"
Date: Tue, 28 Apr 2020 11:29:48 +0200	[thread overview]
Message-ID: <584d3902-f6d2-d332-d3de-b7eb949993e2@gmail.com> (raw)
In-Reply-To: <9d0dff6b-7905-4bdd-2f3c-6c91a33c59d7@xilinx.com>

Hi Michal,

>> Thanks for your script, I tried it, it can extract the PMU config object
>> from the FSBL generated by Vitis, but the SD card I prepare this way
>> still doesn't boot.
>>
>> It does one thing differently than before, though: the line
>>
>>  ?? ### ERROR ### Please RESET the board ###
> 
> Can you please try xilinx u-boot master branch instead?

Sadly, the result is exactly the same as before.  BTW, the Rev1.1 
changes are not in master yet, I had to enter them manually.

> Tap delay programming can be one of the reason.
> But the best would be to load it via jtag and look at backtrace where
> the problem is.

How do I debug it via JTAG?  Any instructions on that somewhere?

Cheers,

   Andr?s

  reply	other threads:[~2020-04-28  9:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 11:28 ZynqMP boot: no messages from SPL other than "Debug uart enabled" Major A
2020-03-12  8:15 ` Michal Simek
2020-03-12  9:12   ` Major A
2020-03-12 10:32     ` Michal Simek
2020-03-12 11:38       ` Major A
2020-03-12 11:44         ` Michal Simek
2020-03-12 12:01           ` Major A
2020-03-12 12:06             ` Michal Simek
2020-03-12 13:24               ` Major A
2020-03-12 13:31                 ` Michal Simek
2020-03-12 14:19                   ` Major A
2020-03-12 15:22                     ` Michal Simek
2020-04-23  9:02                       ` Major A
2020-04-24 12:14                         ` Michal Simek
2020-04-27 22:00                           ` Major A
2020-04-28  6:42                             ` Michal Simek
2020-04-28  9:29                               ` Major A [this message]
2020-04-28  9:33                                 ` Michal Simek
2020-04-28 10:53                                   ` Major A
2020-04-28 11:16                                     ` Michal Simek
2020-04-28 11:25                                       ` Major A
2020-04-28 11:29                                         ` Michal Simek
2020-04-28 13:34                                           ` Major A
2020-04-28 13:55                                             ` Michal Simek
2020-04-28 14:21                                               ` Major A
     [not found]                                                 ` <3ab17480-431a-e0e3-c2af-e1639a2d07a6@xilinx.com>
     [not found]                                                   ` <6b4c296f-fb91-fd84-f5c8-7b4f542034e4@gmail.com>
2020-04-30 10:20                                                     ` Fwd: " Major A
     [not found]                                                     ` <4f8b4b6a-c97d-38b8-5a74-98bbc916cb3a@xilinx.com>
2020-04-30 11:01                                                       ` Major A
2020-04-30 11:03                                                         ` Michal Simek
2020-04-30 11:10                                                           ` Major A

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=584d3902-f6d2-d332-d3de-b7eb949993e2@gmail.com \
    --to=andras.g.major@gmail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox