Tested with industrial module using jetpack 5.1.2
The temperature of the chamber is -35 degrees and 25 degrees, and the storage time is set to 1 hour.
Both the 0000 carrier board and the handmade board stopped booting
I tested it several times with two modules, but they all stopped at the same phrase
Attached is the serial console where the problem occurred
low temp error log :
[ Initialized dvs
Initialized clk_mach_config ]
If there is a solution to this problem, please reply
I think jatpack 5.1.2 may need a patch, just like the temperature problem of jatpack 5.1.1
The “storage time is set to 1 hour” mean the entire device is at off state, then do the hardboot not working?
The same test done at JP5.1.1 with Orin 32GB/64GB module?
Storage time means that the entire unit is turned off at low temperature, and hardware boot does not work.
The same test was performed on Orin 64GB JP 5.1.1 to confirm normal operation at -25 degrees after the low temperature patch.
I ran two Orin industrial modules in the same test and found that the boot stopped in the same serial log.
[?nitialized dvs
initialized clk_mach_config ]
I’ve tried it several times, but the boot stops with that data.
And now the boot didn’t work with the same result at -25 degrees, and the boot worked successfully at -20 degrees.
I attached the serial console data which is the test result.
Thanks for reporting this issue, I have forwarded it to internal team to do more investigation.
Can you help to test with Orin 64GB JP5.1.2 again? Just wnat to double confirm whether that’s the patch not integrated well, or it’s not cover Orin industrial. Thanks
Hello
All modules were installed in order by SDK manager.
The test was conducted with two Orin modules at the same time, one using a hand-made carrier board and the other using a P3701-0000 carrier board.
Most of the tests stopped booting from [initialized clk_mach_config]
I waited 10 minutes after the boot stopped, but it still didn’t work.
Just a basic concept. You always need to share the full log but not just “my board cannot boot”.
We use the log to tell things. But not only your comment.
So please share the full log from your modules. We need to know the exact location but not just “most of tests are balabala”. If the error does not happen in same location, then we need to know every case here.
Share the original text file where the cold test was conducted.
If you want, I will organize it by episode and share it again.
We tested it with two units, but we only saved one unit.
If you look at the text file, you can see that the boot stops at the same location, and at the end, the boot succeeds at -21 degrees.
We have fixed this internally. But releasing a binary out needs few days more. This solution is not open source things so releasing requires a internal review.