Dear NVIDIA team,
we are currently using Xavier NX modules and dev kits for an embedded aerospace project. So far the XavierNX modules have been working great. But we recently came across an larger issue. After shutting down the Jetson it was unable to reboot again and we got this error message in an endless repeat cycle:
0000000000011111111110111000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ÿâ [0000.025] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses. [0000.034] I> MB1 (prd-version: 18.104.22.168-t194-41334769-1740dd39) [0000.039] I> Boot-mode: Coldboot [0000.042] I> Chip revision : A02P [0000.045] I> Bootrom patch version : 15 (correctly patched) [0000.050] I> ATE fuse revision : 0x200 [0000.054] I> Ram repair fuse : 0x0 [0000.057] I> Ram Code : 0x0 [0000.059] I> rst_source : 0xb [0000.062] I> rst_level : 0x1 [0000.065] I> Boot-device: QSPI [0000.068] I> Qspi flash params source = brbct [0000.072] I> Qspi using bpmp-dma [0000.075] I> Qspi clock source : pllp [0000.079] I> QSPI Flash Size = 32 MB [0000.082] I> Qspi initialized successfully [0000.086] E> LOADER: Failed to verify SMD. [0000.090] I> Primary SMD copy is invalid, try with secondary copy.. [0000.096] E> LOADER: Failed to verify SMD. [0000.100] E> LOADER: Failed to verify SMD & SMD_b. [0000.104] E> Error: SMD: Load failed [0000.107] E> Load SMD failed [0000.110] E> LOADER: Failed to get slot for boot chain from SMD. [0000.116] E> LOADER: Failed to get storage info for binary 0 from loader. [0000.122] E> LOADER: Failed to get info for binary 0 from loader. [0000.128] C> LOADER: Could not read binary 0. [0000.132] C> Fail to load mb1-bct bin [0000.135] E> Task 24 failed (err: 0x1d1d1318) [0000.139] E> Top caller module: LOADER, error module: LOADER, reason: 0x18, aux_info: 0x13 [0000.147] I> MB1(22.214.171.124-t194-41334769-1740dd39) BIT boot status dump : 0000000000011111111110111000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
The shutdown probably occurred during the boot process and this corrcuped both SMD copies. We are planing to deploy the Jetson in an inaccessible environment and won’t be able to flash the bootloader again after deployment. We are using the older Jetpack 4.5.1 because of some camera dependencies.
I saw this problem already in multiple other forum posts and the solution seems to be to completely re flash the whole board:
The source seems to be that “there’s a background service running for SMD update and abruptly shutdown may crash the service and cause such scenario”. Can you confirm that this issue is fixed in more recent Jetpack releases? Do you have an specific Jetpack version after which this error was fixed?
If there is an confirmation that this is fixed, then we would try to modify our application for this, as this poses a huge risk, because unplanned power offs could occur at any time.
Thank you for your help!