We are using the ORIN 64GB module (part number: 900-13701-0050-000) on our custom carrier board and recently we experienced random crashes with messages appears on the ORIN serial port. I attached part of the error messages in this topic so you could see. We did reset and power cycle and the crash and error still appear at random time. We used this module before on the same custom carrier board with jetpack 5.1.1 and we did not have this problem before. Can you able to point to us what cause the crash based on the messages?
Yes we customized the kernel since we use the ORIN in our custom board with different pinouts compared to the Nvidia carrier board. We also modified the pinmux spreadsheet to match with our custom board. We recently received 21 ORIN 64GB modules and we found multiple of ORINs experienced similar behavior.
Also, more importantly, while testing we found that the failure mostly happened during the first cold boot after the system powered off overnight, and after multiple reboot issued by ORIN the error messages stops then ORIN maintains operation. The ORIN rebooted itself and fixed itself.
After that, I rebooted the ORIN and it booted up correctly with no errors. Since the jetpack code is locked for this shipment so we cannot able to upgrade the jetpack to more recent version to test yet. I also attached the latest failure log in this post so you could see the error messages.
We received and shipped out 20+ ORIN 64GB last year with the same custom carrier boards and never saw the similar problems that we are having now. Based on the attached boot messages can you narrow down the failures, if it is based on driver(s) problem or external problem from carrier board like power sequence, signal failure , or any changes on recent ORIN module, etc.. ? (we also checked the recent PCN and checked the failed ORINs are 699-13701-0005-500 and they are not affected by PCN210100 and PCN211462)
Thanks for the reply. I will have my firmware engineer to check to make sure to use the correct DTS. Then we will try update the jetpack and change the DTS to see if we see the problem again.