No-Flash Option Only Working in Recovery Mode

Hello,

We did a migration to Jetpack 5.1.3 / L4T 35.5.0 and updated the SDK Manager to 2.1.0.1 1660.

Following those updates, the --no-flash option stopped working if the Orin is not in Recovery Mode.

As this process requires physical access (enter / leave Recovery Mode), it poses a constraint to the team.

The problem is the following:

$ sudo ./flash.sh -r --no-flash jetson-agx-orin-devkit mmcblk0p1 # not in recovery mode

###############################################################################
# L4T BSP Information:
# R35 , REVISION: 5.0
# User release: 0.0
###############################################################################
ECID is 
Board ID() version() sku() revision()
Chip SKU(00:00:00:D0) ramcode() fuselevel(fuselevel_production) board_FAB()
Error: Unrecognized module SKU 

When in Recovery Mode:

$ sudo ./flash.sh -r --no-flash jetson-agx-orin-devkit mmcblk0p1 #  in recovery mode

no_flash_recov_mode_read_info.txt (15.4 KB)
no_flash_recov_mode.txt (26.3 KB)

Note that normal flashing works perfectly fine (but causes development constraints, since it resets the board):

$ sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1 #  in recovery mode

How should we proceed to make --no-flash work again without Recovery Mode?

Thank you.

I don’t really know what’s the purpose of putting -r and --no-flash together.

From JP 6 , jetson-agx-orin-devkit board configure require that BOARDSKU, FAB, BOARDID are provided through environment variable in the command line like this:

Your eeprom information
Board ID(3701) version(500) sku(0000) revision(M.0)
Chip SKU(00:00:00:D0) ramcode(00:00:00:00) fuselevel(fuselevel_production) board_FAB(500)

So your command would be like

sudo BOARDID=3701 BOARDSKU=0000 FAB=500 BOARDREV=500 CHIP_SKU=D0 RAMCODE=0 FUSELEVEL=fuselevel_production ./flash.sh --no-flash jetson-agx-orin-devkit mmcblk0p1

by the way it is possible to control the board remotely through the use of its micro USB port, Board Automation — Jetson Linux Developer Guide documentation

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