My Jetson was running on my desk just doing a few evolutionary trainings when I started noticing that random standard linux commands created segmentation faults. I tried to reboot but the xavier never came back to live (no USB, no Video Output and wasn’t showing up on the network.
What was still working was the serial debug interface and it looks like the I2C broke and the jetson is stuck in a boot loop now?
Unfortunately the xavier is not detected by the SDK Manager anymore. My understanding is that the Xavier AGX can just be flashed through the SDK Manager and not by SD-Card?
Is there a way to reflash the boot loader through the JTAG interface on the carrier board?
After many reboots the debug log looks slightly different:
[0000.352] I> Active Boot chain : 0
[0000.397] I> Relocating BR-BCT
[0000.398] > DEVICE_PROD: device prod is not initialized.
[0000.423] E> I2C: slave not found in slaves.
[0000.424] E> I2C: Could not write 0 bytes to slave: 0x00ae with repeat start true.
[0000.425] E> I2C_DEV: Failed to send register address 0x00000000.
[0000.426] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via instance 0.
[0000.427] E> eeprom: Failed to read I2C slave device
[0000.430] I> Failed to read CVB eeprom data @ AE
[0000.434] I> Retrying CVB eeprom read @ AC ...
[0000.463] E> cpubl: digest on binary did not match!!
[0000.463] I> �域�����域�����域�����域����: execution failed
[0000.463] I> �域�����域�����域�����域����: execution failed
[0000.464] E> Top caller module: LOADER, error module: LOADER, reason: 0x18, aux_info: 0x00
[0000.465] I> AB warm reset
Do you have other AGX Xavier board that can cross check? For example plug out the module from the issued device and put it to another “fine” carrier board.