Xavier NX Module Failures

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

We’ve recently hit a number of xavier nx module failures and were requested that we post some logs to the forum so here we go. While attempting to flash the problematic modules I connected a debug uart and collected the output during the attempt to flash. I’ve attached the logs here.
Summary:
Module 1:

[0016.808] C> Task 0x4d failed (err: 0x8c8c011c)
[0016.812] E> Top caller module: MB1_MSS, error module: MB1_MSS, reason: 0x1c, aux_info: 0x01
[0016.820] C> Error: 0x8c8c011c
[0016.823] C> MB1(2.6.0.0-t194-41334769-cab45716) BIT boot status dump :

Module 2

[0000.066] E> Failed to verify PMC high threshold fault occurrence. Fault reg: 0x0x2
[0000.073] C> Task 0x27 failed (err: 0x77770918)
[0000.077] E> Top caller module: FMON, error module: FMON, reason: 0x18, aux_info: 0x09
[0000.085] C> Error: 0x77770918
[0000.088] C> MB1(2.6.0.0-t194-41334769-cab45716) BIT boot status dump :
0000000000111111111001000000000001111010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0000.117] I> Reset to recovery mode

Module 3 - This one appears to be completely dead
Module 4

[0019.705] E> Error: 0 
[0019.707] C> Task 0x6b failed (err: 0x32320006)
[0019.711] E> Top caller module: CPUINIT, error module: CPUINIT, reason: 0x06, aux_info: 0x00
[0019.719] C> Error: 0x32320006
[0019.722] C> MB1(2.6.0.0-t194-41334769-cab45716) BIT boot status dump :
0000000000111111111001000000000001111011111111000011111111111111001110001111111100100001111101110001101111100000000000000000000010101111000001010111100000110101011110000010101111000000000110000000000011000000000000000000000000000000000000000000000000000000

logs.tar.gz (21.1 KB)

3

Are these module tested on NV devkit?

4

Yes, the logs i posted were collected while running on a NX devkit board.

5

I would suggest you could do more cross check on different carrier board and modules to see if this is related to carrier board defect.

If you are sure it is from module, then please do the RMA.

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.