Making massflash blob on AGX Orin

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
1

Hi,

Platform : AGX Orin
Jetpack : 5.0.2
board : custom carrier board

I can make the massflash blob, but it can’t flash successfully

I use the commands in tools/kernel_flash/README_initrd_flash.txt

To make the massflash blob :

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 10 jetson-agx-orin-devkit mmcblk0p1

Then use the masflash blob to flash 2 device simultaneously :

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 10 --showlogs

The logs show timeout in “Step 3: Start the flashing process”

Here’s logs
flash_1-1_1_20230213-100220.log (45.6 KB)
flash_1-3_0_20230213-100220.log (45.6 KB)

The trying on devkit:

I use the pure image and use the same process on devkit

Making massflash blob is successful and the masflash also success

The weird thing is one of two logs is failed and show “Error flashing qspi”

But the image is flashing in succeed because I can see the OEM config when I boot the device

Here’s logs
flash_1-2_1_20230209-135117.log (63.4 KB)
flash_1-3_0_20230209-135117.log (125.1 KB)

3

Hi zax0220jecht,

Are you refer to the Workflow 6: Initrd Massflash of README_initrd_flash.txt?
If yes, please try the following command for BOARD related parameters to generate massflash package.

$ sudo BOARDID=3701 FAB=TS4 BOARDSKU=0004 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 10 jetson-agx-orin-devkit mmcblk0p1

and do you have the specific board config for your custom board?
(you might use your board config instead of the jetson-agx-orin-devkit for the devkit)

It seems your custom board has boot-up issue which causes host PC could not access the board with ssh and the flash process stopped.
Does your custom board could boot up normally with single flash command?

Please use above command for BOARD related parameters and flash again.

4

Does your custom board have EEPROM?
If not, do you follow the instruction for EEPROM setting?
Jetson AGX Orin Platform Adaptation and Bring-Up — Modifying the EEPROM

5

Hi KevinFFF,

I’ve tried the command and it still not work on our carrier board

sudo BOARDID=3701 FAB=TS4 BOARDSKU=0004 BOARDREV=A.0 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 10 jetson-agx-orin-devkit mmcblk0p1

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 10 --showlogs

The answers for questions :

  1. do you have the specific board config for your custom board?

No, we use the config for devkit and modified the specific dtb/dts to make our I/O work

  1. Does your custom board could boot up normally with single flash command?

No, it can’t boot by the Workflow1 command
sudo ./tools/kernel_flash/l4t_initrd_flash.sh jetson-agx-orin-devkit mmcblk0p1

  1. Does your custom board have EEPROM?

Yes, we have.
But it didn’t really do something work
Should we make anything modification for EEPORM?
Or just follow the instruction in document?

6

Please refer to the adaptation guide for your custom board.

and make sure your custom board could boot up normally before trying with workflow of massflash.

For boot up issue, you may file another topic and provide serial console log for further check.
This topic would be discussing about massflash.

9

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