Hello,
I have asked this question in another post that may be more confusing than is necessary, so I will try to be more clear and simpler.
I upgraded an Xavier AGX 32G module from Jetpack 4.x to Jetpack 5.0.2 and am now having boot failures.
The failures appears to come from one of the boot loaders , MB1 or maybe MB2 (TBoot), being interrupted by some raw serial traffic that is on the 2 UARTs my Connect Tech Rogue carrier card has. I do have serial devices, GPS, IMU etc, on the UARTs and they had no issues for over a year under Jetpack 4.x that I believe runs CBoot.
I have read over the NVIDIA documentation and find the Boot loader section well written, but I am not able to find out if there any monitoring of the UARTs that can cause the boot process to halt. For example, in the older TX2 usage of UBoot, if a serial device was powered on during boot then there was a strong chance the UBoot would be halted by the raw traffic assuming that the user requested to halt the boot. CBoot did not appear to have that issue, while it looks like MB1/2/TBoot may.
Can someone possibly advise me on the follow
- Does MB1 check any UART during boot for console input? If so can I disable this feature/checking through a configuration file?
- Does MB2/TBoot check any UART during boot for console input? If so can I disable this feature/checking through a configuration file?
- I have read comments on forums and also in the documentation about a combined UART, but I have not found any explanation on what exactly this combined UART actually means. Is there more detail on this beyond the configuration file to enable/disable it?
- I have seen some other posts on this subject but they seem older, maybe from the Jetpack 4.x days. Has anyone else observed issues in Jetpack 5.x?
- Sometimes the raw serial traffic causes the AGX to enter setup menus I have never seen before, for example language setup etc. So it seems clear that somehow this traffic from devices on the UARTs are causing a part of the boot loading to take actions.
- If I power cycle enough times I can usually get it to boot, maybe one inf 50 times success.
- If I remove the serial devices from the UARTs, power cycle the AGX, it boots with no issues. I can then reconnect the serial devices and everything operates as it should. Clearly that is not an operation solution, but I mention it as a data point that indeed the system and devices are all functional as expected.