Closed nerbivol closed 2 months ago
Does the LED still blink? If so your system is booted. UART2_M0 is used as debug console (console=ttyFIQ0,1500000n8
) by default, so if you enabled it as a normal UART, then the console will be closed as the port is now a ttyS*
.
The LED doesn't blink at all; it just stays on. The port works as ttyS2
, but Radxa doesn't boot when a device is connected to UART2_M0
. I can start Radxa and then connect the device to UART2_M0
. My question is, do I need to change anything in /etc/kernel/cmdline
?
This is the reason we do not recommend using UART2_M0: the default U-Boot console is connected to this port, and it will interrupt the boot process when there is input over the serial.
You will need to do a system update and then boot loader update from rsetup
. Then edit /etc/default/u-boot
to uncomment prompt & timeout to be 0. Run sudo u-boot-update
to rebuild boot profile, and you should now be able to boot.
Your UART device might malfunction with the boot log outputting on this port though.
After running sudo apt upgrade
on my Radxa device, I can no longer connect to Wi-Fi. The device doesn't detect any available Wi-Fi networks.
It is not supported, which is why I told you to use rsetup
.
Edit: I can see I was not quite clear on this. Use rsetup
.
Oh, you're right! Thank you. I'll update through rsetup
. I was struggling with this before!
I need to configure
UART2_M0
as a normal serial port. I followed the instructions provided in the Radxa documentation. Inrsetup
, I set theEnable UART2-M0
option to*
. When Radxa is already running, everything works fine. However, after a reboot, the Radxa device fails to boot.It seems like I need to modify the Linux boot parameters. My current
/etc/kernel/cmdline
looks like this:Question:
console=ttyFIQ0,1500000n8
, or is there something else I need to consider?