AGX-Xavier, flash.sh was blocked in 'tegrarcm_v2 --isapplet'

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
,
1

Software Version
Jetpack4.6.1

Target Operating System
Linux

Hardware Platform
AGX Xavier- customized board

SDK Manager Version
L4T-32.7.1

Host Machine Version
Ubuntu 18.04

The board can boot up nomally, it just can’t be flash.
when I run flsah.sh, the program was blocked in ‘tegrarcm_v2 --isapplet’.
I found a similar topic, and follwing the solution, I checked Strapping Pins as OEM Develop Guide, but found nothing wrong.
Is there any problem ignored？

The flash log prints following below:

[   0.1475 ] Signing RCM messages
[   0.1501 ] tegrasign_v3.py --getmontgomeryvalues montgomery.bin --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.1503 ] Assuming zero filled SBK key
[   0.1636 ] Copying signature to RCM mesages
[   0.1663 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[   0.1684 ] 
[   0.1685 ] Boot Rom communication
[   0.1711 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml --skipuid
[   0.1723 ] RCM version 0X190001
[   0.1981 ] Boot Rom communication completed
[   1.2143 ] 
[   2.2195 ] tegrarcm_v2 --isapplet
[   2.2217 ] Applet version 01.00.0000
[   2.2963 ] 
[   2.3002 ] tegrarcm_v2 --ismb2
[   2.3923 ] 
[   2.3963 ] tegrahost_v2 --chip 0x19 --align nvtboot_applet_t194.bin
[   2.3987 ] 
[   2.4025 ] tegrahost_v2 --chip 0x19 0 --magicid PLDT --appendsigheader nvtboot_applet_t194.bin zerosbk
[   2.4046 ] adding BCH for nvtboot_applet_t194.bin
[   2.4094 ] 
[   2.4122 ] tegrasign_v3.py --key None --list nvtboot_applet_t194_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   2.4124 ] Assuming zero filled SBK key
[   2.4224 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_sigheader.bin.encrypt nvtboot_applet_t194_sigheader.bin.hash zerosbk
[   2.4281 ] 
[   2.4314 ] tegrarcm_v2 --download mb2 nvtboot_applet_t194_sigheader.bin.encrypt
[   2.4331 ] Applet version 01.00.0000
[   2.5079 ] Sending mb2
[   2.5081 ] [................................................] 100%
[   2.5238 ] 
[   2.5276 ] tegrarcm_v2 --boot recovery
[   2.5297 ] Applet version 01.00.0000
[   2.6078 ] 
[   3.6130 ] tegrarcm_v2 --isapplet

Additionally，when flash.sh runs, the uart log prints as follow:

[0023.133] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0023.141] I> MB1 (prd-version: 1.5.1.9-t194-41334769-73a9b7ef)
[0023.147] I> Boot-mode: Platform RCM
[0023.150] I> Chip revision : A02P
[0023.153] I> Bootrom patch version : 15 (correctly patched)
[0023.158] I> ATE fuse revision : 0x200
[0023.162] I> Ram repair fuse : 0x0
[0023.165] I> Ram Code : 0x2
[0023.167] I> rst_source : 0x0
[0023.170] I> rst_level : 0x0
[0023.174] I> USB configuration success
[0025.443] I> mb2 image downloaded
[0025.527] I> Recovery boot mode 0
[0025.530] E> Unsupported boot-device strap-reg: 0x00000004
[0025.535] E> Get boot dev failed
[0025.538] E> UPHY lane_config get failed
[0025.542] E> Task 44 failed (err: 0x1e1e0001)
[0025.546] E> Top caller module: SOCMISC, error module: SOCMISC, reason: 0x01, aux_info: 0x00
[0025.554] I> MB1(1.5.1.9-t194-41334769-73a9b7ef) BIT boot status dump :
0000000000011111111111100000000000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000000011001000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0025.584] I> Reset to recovery mode
2

Dear @shantian.huang,
Could you please confirm if it is DRIVE platform or Jetson?

3

Your topic was posted in the wrong category. I am moving this to the Jetson AGX Xavier category for visibility.

5

Hi shantian.huang,

Does your board have EEPROM?
Which board config are you using to flash your customized board?

6

No, the board has no EEPROM. The config file is jetson-agx-xavier-devkit.conf.
Running command like this:
./flash.sh jetson-agx-xavier-devkit mmcblk0p1

I had flashed it successfully before. It can’t be flash again.

7

Do you have NV devkit to test the flash function?

8

Yes，i do. It can be flash. So does another customized board.

9

Then this looks like a hardware problem.

That error “Unsupported boot-device strap-reg:” may not be software issue. It could be strap pin got something wrong. Please refer to the design guide document for strap pin.

10

I have checked the strap pin, but it seems nothing wrong.

11

Is your “this module can work fine on devkit” also using the same BSP to flash as your custom board?

12

Yes, this module is work fine.

13

不是 我的意思是你燒 devkit跟燒custom board的時候用的是同一份BSP嗎?

No, I am asking if you are using same BSP to flash your devkit and custom board.

14

Yes, the same BSP.

15

There is only one same issue reported by another user 3 years ago. Thus, I still believe this is hardware design issue.

16

I read the topic before. which pin do you think is the the most possibility that cause the problem？ I will check it again tomorrow.