Posts: 4
Joined: Tue Jul 10, 2018 12:17 am

RP4 - Cannot get bootmessages to UART

Wed Sep 25, 2019 5:55 pm

My goal is to route all kernel boot messages to the UART4. I already have ttyAMA1 configured.

I whittled down my /boot/cmdline.txt to only the following:

Code: Select all

dwc_otg.lpm_enable=0 console=/dev/ttyAMA1,115200 root=PARTUUID=aaaaaaaa-02 rootfstype=ext4 elevator=deadline rootwait
My /boot/config.txt contains:

Code: Select all

# Enable UART4 debug console
With the above, on the connected HDMI display there is no output, but there is also NO output on the UART either! Once the system boots, I have (after reconfiguring the getty to use ttyAMA1) a login prompt on the UART. But there are no boot messages.

Posts: 764
Joined: Tue Aug 13, 2013 6:55 pm
Location: Dublin, Ireland

Re: RP4 - Cannot get bootmessages to UART

Thu Sep 26, 2019 10:21 pm

The 'dtoverlay=pi3-disable-bt" has now been changed to:

Code: Select all

The 'pi3-disable-bt' remains as an alias, but I don't know if it works on a Pi4.
When using 'dtoverlay=disable-bt', it is also necessary to issue the command

Code: Select all

sudo systemctl disable hciuart
once and reboot, otherwise '/dev/ttyAMA0' is still tied to Bluetooth.
Details in '/boot/overlays/README'

As you are trying to get boot messages on '/dev/ttyAMA1', and Bluetooth normally uses '/dev/ttyAMA0', I'm not sure the above will solve your problem, but worth trying.
As a troubleshooting step, I would try putting the phrase 'console=serial0,115200' back into '/boot/cmdline.txt' and see if you get boot messages on GPIO pins 14 and 15.


Return to “Troubleshooting”