For the past few days I have been attempting to use the ttyS0 port for regular UART commnication. The issue is the fact that unlike ttyTHS2, this port is reserved for serial debugging console.
Before doing anything, when i was connecting the RX and TX pins to each other and sending a “hello world” message over this network, i was getting garbage messages alongside what I had initially sent. Also, the RX and TX pins being connected to each other during system startup was causing the system to hang with black screen instead of booting normally. “cat /proc/cmdline” was also containing a message that was stating that ttyS0 is serial debugging port.
Here are some of the fixes I have attempted:
- Disabling getty and nvgetty, this has not helped with anything.
- I messed with some configuration files and changed the “console=ttyS0,115200n8 console=tty0” lines I found with with “console=tty0” in my Linux_for_Tegra folder. Afterwards, I flashed with “sudo ./flash -r -k kernel-dtb jetson-tx2i mmcblk0p1”. Initially I thought this had fixed the issue. I am no longer seeing garbage messages with the “hello world” messages I am sending through this network, which is when Linux is up and running. Additionally “cat /proc/cmdline” is no longer containing traces of ttyS0. However, when the RX and TX pins are connected to each other, the system still hangs at startup with black screen… Since I intend to use it for a headless system that is meant to operate without human intervention, it is out of question for me to make the connections after the boot process.
- I’ve had a look at the 3rd last message here: UART1 acts as default debug port on TX2, R28.1 - #12 by JerryChang . However, I could not understand well how to carry out the changes outlined. What software would I need for them? Is it something other than the regular flashing procedure? Would they be useful on newer L4T?
I think I have alse read up about something regarding re-compiling the device tree. What relevant guide can I follow to de-activate serial debugging console this way? Might it have something to do with 3rd party BSP (I assume this to be unlikely).
Platform: Jetson TX2i
L4T Version: 32.2.3
Carrier Board: Connect Tech Orbitty Carrier
Thank you in advance.