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: Thu, 30 Apr 2020 13:10:43 +0200	[thread overview]
Message-ID: <90804b25-0bd5-2124-7c80-e045d03576c5@gmail.com> (raw)
In-Reply-To: <47699640-e89a-585a-59b0-1d4f1d00ae8d@xilinx.com>

Hi Michal,

Yes, I did.  The Petalinux image from here:

 
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841937/Zynq+UltraScale+MPSoC+Ubuntu+part+2+-+Building+and+Running+the+Ubuntu+Desktop+From+Sources

works fine.

Cheers,

   Andr?s


On 30/04/2020 13:03, Michal Simek wrote:
> hi,
> 
> that's quite weird. Did you try any petalinux bsp and boot petalinux
> boot.bin on that board to make sure that board is fine?
> 
> M
> 
> On 30. 04. 20 13:01, Major A wrote:
>> Hi Michal,
>>
>> Sorry I misunderstood your message, and I didn't spot the attached
>> files.? Now I booted with those two files, there's no output on the
>> UARTs whatsoever.? Is there anything else I can try?
>>
>> Cheers,
>>
>>  ? Andr?s
>>
>>
>> On 30/04/2020 12:33, Michal Simek wrote:
>>> Hi,
>>>
>>> On 30. 04. 20 12:19, Major A wrote:
>>>> Hi Michal,
>>>>
>>>>> can you please try these files in SD boot mode?
>>>>
>>>> Done, here are two logs, both in SD boot mode.
>>>>
>>>> First, log.sd is with SD card inserted (with the image files that
>>>> apparently refuse to work other than the early UART message).
>>>>
>>>> The other file, log.no-sd, is with no card inserted.
>>>
>>> we don't understand each other. I sent you boot.bin and image.itb. Just
>>> copy them to SD card, switch board to sd boot mode and power it up.
>>>
>>> Thanks,
>>> Michal
>>>
> 

      reply	other threads:[~2020-04-30 11:10 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
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 [this message]

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=90804b25-0bd5-2124-7c80-e045d03576c5@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