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: Wed, 11 Mar 2020 12:28:01 +0100 [thread overview]
Message-ID: <f5d7cb93-4917-75f8-e736-d11ac8e284da@gmail.com> (raw)
Hi everyone,
Please forgive me if this issue has already been discussed somewhere, I
haven't been able to find the solution after searching and playing
around for the past week.
I have a ZynqMP board (Xilinx ZCU102 V1.1) and would like to install my
own Linux on it, based on the U-Boot SPL. After playing around with the
Xilinx version of U-Boot and various sources for ATF as well as PMUFW,
I've now settled on mainstream U-Boot (from git, master branch) as the
code I'd like to use. There's an issue there already: if I run
make DEVICE_TREE="zynqmp-zcu102-rev1.0" xilinx_zynqmp_virt_defconfig
then the default device tree in .config ends up being
"zynqmp-zcu100-revC", there's no sign of my DEVICE_TREE parameter making
it into .config . In any case, I fixed this manually, then I also
enabled early UART output and UART debugging.
After each build, I copy spl/boot.bin to the SD card and try to boot the
ZCU102.
The real issue is that, whatever I do, whichever version or
configuration of U-Boot I compile, I get a message "Debug uart enabled"
from the early UART code, but then nothing. Everyone else on the
internet seems to see at least a few more lines of output, usually
starting with "U-Boot SPL 2020.04-rc3-00108-gdb41d985f6" or similar
(this string was taken from the boot.bin I copied to the SD card, so
it's there!), whereas I see nothing at all.
If I turn early UART off, then I don't even get the "Debug uart enabled"
message. Simply nothing. Also no complaints about bl31 or PMUFW in
case I deliberately built without them.
The board works fine with Petalinux, and it passes all hardware tests,
so it should be OK. I'm monitoring all four UARTs exposed through the
USB device interface, just in case something is routed to the wrong
UART. But again, nothing.
I'm stuck, I'd appreciate any help.
Cheers,
Andr?s
next reply other threads:[~2020-03-11 11:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 11:28 Major A [this message]
2020-03-12 8:15 ` ZynqMP boot: no messages from SPL other than "Debug uart enabled" 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
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=f5d7cb93-4917-75f8-e736-d11ac8e284da@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.