mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Robert Carnecky (Neopsis)" <robert@neopsis.com>,
	barebox@lists.infradead.org
Subject: Re: Mini UART on RaspberryPi CM3/CM3+
Date: Fri, 9 Oct 2020 16:18:33 +0200	[thread overview]
Message-ID: <0fae6213-91b3-a3ae-e1b8-2c7752866b2a@pengutronix.de> (raw)
In-Reply-To: <CABMENH4s2fWgZmJG-hMtKmHJAmC0N6PtL41LA2vJ4iuA1tPA9g@mail.gmail.com>

Hello Robert,

On 10/9/20 2:30 PM, Robert Carnecky (Neopsis) wrote:
>> Try adding to arch/arm/dts/bcm2837-rpi-cm3.dts:
>>
>> &uart1 {
>>         pinctrl-names = "default";
>>         pinctrl-0 = <&uart1_gpio14>;
>>         status = "okay";
>> };
> 
> I extended arch/arm/dts/bcm2837-rpi-cm3.dts as advised +
> additionally I set UART0 to pins 32/33.
> 
> &uart0 {
>      pinctrl-names = "default";
>      pinctrl-0 = <&uart0_gpio32>;
>      status = "okay";
> };
> 
> I still cannot see Barebox console on boot, however, the Barebox loader
> starts in 3 seconds my kernel and I get the Linux console output on
> UART1/ttyS0.

Strange that this made the kernel boot now. Maybe somewhere an unclocked
peripheral was being accessed before?

> Now my Linux boots as expected, unfortunately without
> visible Barebox console. I tried all Barebox console setting
> (NONE/ALL/FIRST), same result, no Barebox console output on UART0
> or UART1.

Huh, you did listen at the UART0 _before_ the RS-485 transceiver?
UART0 should work, at least it apparently did when the CM3 support
was added.

>> If that doesn't help, use CONSOLE_ACTIVATE_ALL and listen
>> on UART0 before the RS-485 transceiver and paste the
>> dmesg and devinfo input you get.
> 
> # dmesg | grep tty
> [    0.000000] Kernel command line: console=ttyS0,115200
> coherent_pool=1M snd_bcm2835.enable_compat_alsa=0
>  snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1
> 8250.nr_uarts=1 bcm2708_fb.fbwidth=656
>  bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1
> smsc95xx.macaddr=B8:27:EB:C5:7D:E3 vc_mem.mem_base=0x3ec00000
>  vc_mem.mem_size=0x40000000  root=/dev/mmcblk0p2 console=ttyS0,115200
> rootfstype=ext4 elevator=deadline rootwait
> [    1.289058] printk: console [ttyS0] disabled
> [    1.289175] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 53, base_baud
> = 50000000) is a 16550
> [    1.945483] printk: console [ttyS0] enabled
> [    2.432604] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81,
> base_baud = 0) is a PL011 rev2
> 
> # stty -F /dev/ttyAMA0 115200
> # cat /etc/inittab  > /dev/ttyAMA0   <- OK

I meant dmesg under barebox, if UART1 fails to output, but UART0 can be
read before the transceiver.

On 10/6/20 1:32 AM, Robert Carnecky (Neopsis) wrote:
> I played a bit more with the config.txt settings and when I activated the flag
> 
>     uart_2ndstage=1
> 
> I got the barebox console! Here a snippet from the 2stage while
> logging the UART lading.

Oh. That would indicate that there is some sort of initialization missing.
uart_2ndstage=1 initializes the UART for VideoCore use apparently and from
there on, it works.

> What I do not understand: how the loaded  /mfs/sd/bcm2710-rpi-cm3.dtb
> and the overlays
> cooperate with the Barebox device tree? Does it mean we have two sets
> of device tree
> files?

Yes. The VideoCore device tree is available in barebox as /vc.dtb,
see e390c8799d91 ("ARM: rpi: save fdt that was passed from VideoCore")


Hope this helps,
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-10-09 14:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 10:07 Robert Carnecky (Neopsis)
2020-10-05 11:16 ` Ahmad Fatoum
2020-10-09 12:30   ` Robert Carnecky (Neopsis)
2020-10-09 14:18     ` Ahmad Fatoum [this message]
2020-10-17 11:31       ` Robert Carnecky (Neopsis)
2020-10-17 21:29         ` Ahmad Fatoum
2020-10-17 23:17           ` Robert Carnecky (Neopsis)
2020-10-19  9:28             ` Ahmad Fatoum
2020-10-19 22:29               ` Robert Carnecky (Neopsis)
2020-10-20  3:59                 ` Rouven Czerwinski
2020-10-20  4:04                   ` Rouven Czerwinski
2020-10-20 12:22                     ` Robert Carnecky (Neopsis)
2020-10-20 12:45                       ` Rouven Czerwinski
2020-10-20 17:04                         ` Robert Carnecky (Neopsis)
2020-10-21  8:21                           ` Robert Carnecky (Neopsis)

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=0fae6213-91b3-a3ae-e1b8-2c7752866b2a@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=robert@neopsis.com \
    /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