We are using Jetson Nano production modules on our custom carrier boards. The issue stated here: https://forums.developer.nvidia.com/t/jetson-nano-production-module-does-not-boot-on-custom-carrier-board-but-does-so-on-auvideas/110823/16 still exists. Sorry for the delay in following up.
We are using Jetpack 4.2.1 as some of our drivers are according to that version, and we cannot upgrade anytime soon. Also, at the moment we are only able to bring out the UART2 port (because of the PCB design), i.e., connect only that port to the TTL-to-USB converter. And we do not have an HDMI port, so we cannot view logs on the monitor, so only via host system.
So basically normally our custom carrier boards would not have a serial communication capability, this cable is soldered just to investigate the issue mentioned in the link above.
We are able to see the console, after boot, over UART, on the host PC, where a tegra-ubuntu login is prompted, but no serial logs before/during booting. Enabling/disabling the nvgetty service does not help with obtaining the logs.
What we tried: modifying the p3448-0000.conf.common file, by changing the line:
CMDLINE_ADD="console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0";
CMDLINE_ADD="console=ttyTHS1,115200n8 console=tty0 fbcon=map:0 net.ifnames=0";
but it did not help. We are particularly interested in fetching the preboot logs, which we cannot find under dmesg.
To summarize: We think that UART logs are available over UART0 for our current configuration. But we want them over UART2. Is it possible?
We referred to the documentation: https://developer.download.nvidia.com/assets/embedded/secure/jetson/Nano/docs/Jetson_Nano_Product_Design_Guide_DG-09502-001_v2.2.pdf?k7Pua3qrMSihDNcjXV_YziXPdubYjJn6GoVMg_5ASyfsmgPcYgcvm484x5F5UeSTTkQyjExEmyry0fZ0Hial5dL08EMUAuaJLUqpCpVFxwG3dTFZSrz_UJHKtsO4phRc1AhLmGm5c1hKiiusbHM3yPCQQILTA9Yg94neiF6uu129yOk4FifLp4hFmKD_JnhgF4RBtV957q8-qeOtlw, but couldn’t figure it out.