Hi,
Thor module + custom board SDK version r38.2.
If the UART3 debug cable is connected from power-on, the serial output becomes garbled immediately after the UEFI stage. If I leave the cable disconnected before this time and plug it in ~5 seconds later (during kernel init), the kernel logs are clean and readable.
garbled.log (158.1 KB)
normal.log (170.5 KB)
Hi @lzyu1110 , I hope you are doing well!
You could try using a different serial terminal program such as Minicom or Picocom to rule out any issues with the current terminal.
Also, make sure to check the baud rate used by both the board and your terminal. If the UEFI or kernel is configured for a different baud rate than your terminal (for example, 115200 vs 1500000), the output will appear garbled right after boot.
Please let me know if this helps, and if you have any questions, don’t hesitate to ask!
Best Regards,
Oscar Mendez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com
I tried minicom and it works well now. thanks.
Hi lzyu1110,
We would suggest using nv_tcu_demuxer to prevent the garbled messages during boot.
Please refer to Tegra Combined UART — Jetson Thor for details.