I’m running into issues where my Orin modules (happened on Orin NX 16GB, Orin nano 8GB and Orin nano 4GB) get stuck in boot after a seemingly random amount (in one case it was roughly 45) of power-ups and power-downs. The Debug UART of the malfunctioning Jetson writes:
However, this is happening on Jetpack 6.1 (as well on Jetpack 6.0, reflashing them to the newest Jetpack was the first thing I tried), which is listed as a solution in those topics.
To get the Jetson out of the malfunctioning state I had to reflash the modules with
I haven’t been able to put it through a properly long reboot test,onlya shorter one where it went 60 rebootwithout a hitch. Will report back on that one a week from now.
As for the original issues, We were testing our new batch of custom carrier boards. Each board went through three reboots where we tested various configurations, on one documented case the jetson malfunctioned after 15 boards (45 reboots). Is it possible the modules store some variables about each unique pci-e device, or something like that?
I didn’t encounter anything at a reboot stress test at over 220 reboots. Could it somehow be related to the amount of unique devices? Or some pci-e related thing?