Can not flash Jetson xavier NX

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

Hey everyone,

I tried flash my device Jetson Xavier NX [DevKit] with the latest release L4T R32.5.2. I was getting issue when flashing the device.

For your information, this topic is related to this one

  • Here is the logs (From serial uart)
[0011.415] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.                                      
[0011.423] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)                                                                         
[0011.429] I> Boot-mode: Platform RCM                                                                                                   
[0011.432] I> Chip revision : A02P                                                                                                      
[0011.435] I> Bootrom patch version : 15 (correctly patched)                                                                            
[0011.441] I> ATE fuse revision : 0x200                                                                                                 
[0011.444] I> Ram repair fuse : 0x0                                                                                                     
[0011.447] I> Ram Code : 0x0                                                                                                            
[0011.450] I> rst_source : 0x0                                                                                                          
[0011.452] I> rst_level : 0x0                                                                                                           
[0011.456] I> USB configuration success
[0013.492] I> mb2 image downloaded
[0013.506] I> Recovery boot mode 0
[0013.509] I> Boot-device: QSPI
[0013.514] I> UPHY full init done
[0013.518] I> MB1 done

[0013.523] W> Profiler not initialized
[0013.526] I> Welcome to MB2(TBoot-BPMP) Applet (version: 00.00.2018.32-mobile-f43153f5)
[0013.534] W> Profiler not initialized
[0013.538] I> DMA Heap @ [0x40020000 - 0x40065800]
[0013.542] I> Default Heap @ [0xd486400 - 0xd48a400]
[0013.547] W> Profiler not initialized
[0013.551] W> Profiler not initialized
[0013.554] E> DEVICE_PROD: Invalid value data = 0, size = 0.
[0013.560] W> device prod register failed
[0013.563] W> Profiler not initialized
[0013.568] E> Error in command_complete 18000 int_status
[0013.573] E> OCR failed, error = f0f0706
[0013.577] I> SDMMC is not present.
[0013.580] I> QSPI Flash Size = 32 MB
[0013.591] I> Qspi initialized successfully
[0013.643] E> Link startup dme_set failed
[0013.646] E> UFS initialization failed
[0013.650] I> UFS is not present
[0013.653] W> Profiler not initialized
[0013.658] I> Found 47 partitions in QSPI_FLASH (instance 0)
[0013.664] W> Profiler not initialized
[0013.667] W> Profiler not initialized
[0013.671] W> Profiler not initialized
[0013.674] I> Entering 3p server
[0013.678] I> USB configuration success
[0014.536] I> Populate chip info
[0014.547] I> Populate eeprom info
[0014.551] I> Populate eeprom info for module cvm
[0014.592] I> Rebooting : reboot-recovery


[001��
[0009.096] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0009.104] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)
[0009.110] I> Boot-mode: RCM
[0009.112] I> Chip revision : A02P
[0009.115] I> Bootrom patch version : 15 (correctly patched)
[0009.121] I> ATE fuse revision : 0x200
[0009.124] I> Ram repair fuse : 0x0
[0009.127] I> Ram Code : 0x0
[0009.130] I> rst_source : 0xb
[0009.133] I> rst_level : 0x1
[0009.136] I> USB configuration success
[0011.110] I> bct_bootrom image downloaded
[0011.119] C> LOADER: mb1bct binary ratchet level 0 is less than ratchet level 60 from HW fuses.
[0011.127] C> LOADER: Could not read mb1bct.
[0011.131] C> Fail to load mb1-bct bin
[0011.134] C> OEM authentication of MB1-BCT failed!!!
[0011.139] E> NV3P_SERVER: Failed to verify image bct_mb1.
  • Here is the logs (From Host machine)
...
[   2.9234 ] Boot Rom communication
[   2.9259 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml
[   2.9281 ] BR_CID: 0x88021911647147031000000013ff8140
[   2.9299 ] RCM version 0X190001
[   2.9302 ] Boot Rom communication completed
[   3.9470 ] 
[   4.9519 ] tegrarcm_v2 --isapplet
[   4.9551 ] Applet version 01.00.0000
[   4.9589 ] 
[   4.9590 ] Sending BCTs
[   4.9599 ] tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt --download bct_mem mem_rcm_sigheader.bct.encrypt
[   4.9607 ] Applet version 01.00.0000
[   4.9626 ] Sending bct_bootrom
[   4.9627 ] [................................................] 100%
[   4.9640 ] Sending bct_mb1
[   4.9691 ] [................................................] 100%
[   4.9727 ] 000000001d1d0b08: 1bctӣ@from
[   4.9989 ] 
Error: Return value 8
Command tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt --download bct_mem mem_rcm_sigheader.bct.encrypt

Any help would be appreciated.

Thanks,
Ilies

3

hello ilies.chergui,

may I have confirmation, is this a fused Jetson Xavier NX ?

4

Hello @JerryChang

I tried to burn the Tegra fuses but It doesn’t happen for some reason please see this topic

Attached file contains the logs when trying to read tegra fuses.

odm_fuse_read_jetson_nx.log (31.2 KB)

Please take a look

5

hello ilies.chergui,

SecureBoot feature it only supported with production modules. (i.e. eMMC version)
FYI, in the next coming release (i.e. JetPack-4.6), it’ll include soft preventing mechanism to prevent fusing on non-eMMC version boards.
thanks

6

Hey @JerryChang

In the previous topic you said that we can define mb1bct version, this works only with Jetson Xavier AGX.

Are you planing to make this possibility with Jetson Xavier NX ? if so, could you please provide the binary or the patch for testing.

Thanks a lot for your help

7

hello ilies.chergui,

I’ve checked again, it’s only Jetson AGX Xavier to supports this workaround.
as I mentioned in comment #5, there’ll be soft preventing mechanism to prevent fusing on non-eMMC version boards in further release.
thanks

1 Like
9

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