From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: RPi3: serial console
Date: Wed, 04 Nov 2020 15:05:18 +0100 [thread overview]
Message-ID: <0f3f9865757edddffef7d598e234b86e@agner.ch> (raw)
In-Reply-To: <CAHYQr0pBQB-c_sKO-7N49==0zAJ7_roQ1VCZ6JubTCqKk-1Rqw@mail.gmail.com>
On 2020-10-16 03:28, Ricardo Salveti wrote:
> On Tue, Oct 13, 2020 at 11:04 AM Peter Robinson <pbrobinson@gmail.com> wrote:
>>
>> > >> Hello Matthias,
>> > >>
>> > >> I have upgraded the Raspberry 3 firmware from raspi3-firmware
>> > >> (1.20190215-1+deb10u4) to raspi-firmware (1.20200601-3)
>> > >> [https://packages.debian.org/bullseye/raspi-firmware].
>> > >>
>> > >> After the upgrade the output of U-Boot on the serial console is complete
>> > >> gibberish as if the baudrate were incorrect. The output from the Linux
>> > >> kernel is fine at 115200 baud.
>> > >
>> > > I've seen similar on all firmware since around mid April up until
>> > > recently, it seems to be fixed with releases in Oct (I'm using one
>> > > from Oct 8th), I'm not sure if it can be fixed in U-Boot but it seems
>> > > to be due to a change in the firmware.
>> >
>> > Thanks for confirming the problem.
>>
>> For reference I have found a number of other problems with recent
>> firmwares and 2020.10 release:
>> * U-Boot crashes on a RPi4 8Gb model if you don't have a display connected [1]
>> * It doesn't boot, not sure if it's a crash or something else, you
>> just get the rainbow screen, if you don't have the uart enabled in
>> config.txt (ie just using a display for output).
>
> Noticed the same as well here (boots fine only with enable_uart=1).
> While playing over with the files I noticed it works fine with the
> latest firmware when using an older bcm2710-rpi-3-b-plus.dtb
> (placed together with the firmware). If I use the latest
> bcm2710-rpi-3-b-plus.dtb from the 5.4 downstream kernel, it doesn't
> work (only tested on rpi3-b-plus).
>
> This is with CONFIG_OF_BOARD=y, if I use CONFIG_OF_EMBED instead it
> works just fine (which gives me the impression that u-boot might not
> be happy with the dtb generated by the firmware when enable_uart is
> not set).
What we noticed is adding brcm,bcm2835-pl011 compatible to the UARTs
makes U-Boot 2020.10 boot even *without* enable_uart=1. dm shows that
with this change CONFIG_BCM283X_PL011_SERIAL is in use...
From what I understand, this driver checks if the UART is muxed, and if
not bails out. So I guess without that compatible string, when the
regular PL011 driver is used, it seems that U-Boot tries to initialize
UART and fails?
--
Stefan
next prev parent reply other threads:[~2020-11-04 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:56 RPi3: serial console Heinrich Schuchardt
2020-10-12 16:50 ` Peter Robinson
2020-10-12 18:39 ` Heinrich Schuchardt
2020-10-12 23:21 ` Otavio Salvador
2020-10-13 14:04 ` Peter Robinson
2020-10-16 1:28 ` Ricardo Salveti
2020-11-04 14:05 ` Stefan Agner [this message]
2020-11-10 16:21 ` Stefan Agner
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=0f3f9865757edddffef7d598e234b86e@agner.ch \
--to=stefan@agner.ch \
--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