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, 12 Mar 2020 12:38:01 +0100 [thread overview]
Message-ID: <69846a06-7085-70dd-bde1-95abf870cd73@gmail.com> (raw)
In-Reply-To: <4fcae7a6-1156-d868-3463-424368cf7b7f@xilinx.com>
Hi Michal,
> First of all I sent v2 because of dt changes to see 1.1 revision and I
> have also tested it on real HW.
Just tried your patch v2 against mainline master branch, it still
doesn't work on my board. I also checked your mainline-v20200312
branch, it's exactly the same: no output from any UART other than "Debug
uart enabled" on UART0 if I enable it in menuconfig as "early UART".
>> For some reason, that's no enough: I have to manually set
>> CONFIG_DEVICE_TREE because xilinx_zynqmp_virt_defconfig sets it wrong.
>> In any case, behaviour is exactly the same as before.
>
> With latest my queue it should be enough.
> https://github.com/michalsimek/u-boot/tree/mainline-v20200312
It's the same. CONFIG_DEFAULT_DEVICE_TREE becomes "zynqmp-zcu100-revC"
whatever I do, there is no trace of the value specified in the
DEVICE_TREE environment variable.
> But I think that latest mainline should setup default in ITS properly.
> You can check it by looking at u-boot.its when build is done and find
> default configuration option which should point to 1.1 dt.
From the build using your mainline-v20200312 branch:
default = "config_1";
where config_1 is
description = "avnet-ultra96-rev1";
> Here are jtag steps I have run.
I haven't set up JTAG yet.
Cheers,
Andr?s
next prev parent reply other threads:[~2020-03-12 11:38 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 [this message]
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=69846a06-7085-70dd-bde1-95abf870cd73@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.