BootRom is not running when flashing to multiple Jetson devices

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

Hi,
I am trying to flash the BSP(Jetson Linux 35.5.0) to two identical Jetson Xavier NX 8 GB-DRAM devices(jetson-xavier-nx-devkit-emmc) at the same time by using the method in the developer guide:Flashing to Multiple Jetson Devices.
1.Run the following command:

sudo BOARDID=3668 FAB=100 BOARDSKU=100 BOARDSKU=0001 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --network usb0 -massflash 5 jetson-xavier-nx-devkit-emmc mmcblk0p1

2.Connect the two Jetson devices to the flashing hosts(Ubuntu18.04).
3.Ensure that the devices have the identical hardware revision.
4.Place all of the connected Jetson devices into RCM mode.
5.Run the following command:

sudo ionice -c 1-n 0 ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --flash-only --massflash 2

However, only one board was flashed successfully, the other board got stuck in an error:

Entering RCM boot

[   0.0000 ] rcm boot with presigned binaries
[   0.0000 ] Boot Rom communication
[   0.0019 ] tegrarcm_v2 --instance 1-10 --chip 0x19 0 --rcm rcm_1_encrypt.rcm --rcm rcm_2_encrypt.rcm
[   0.0025 ] BootRom is not running

How can I solve this problem? Thanks.

3

Hi qian.yuan,

Are you using the devkit or custom board for Xavier NX?

Could you share the result of the following command on your board?

$ cat /etc/nv_boot_control.conf

Could you share the full flash log for further check?
Or have you tried to using initrd flash script to flash this board independently?

4

Hi,

  1. I am using the devkit for Xavier NX 8 GB-DRAM.
  2. This is the result of the command cat /etc/nv_boot_control.conf on my board:
TNSPEC 3668-300-0001-B.0-1-2-jetson-xavier-nx-devkit-emmc-
COMPATIBLE_SPEC 3668-100---1--jetson-xavier-nx-devkit-emmc-
TEGRA_LEGACY_UPDATE false
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
  1. I want to share the full log but I am not able to upload or paste the full log because of the information security rules of my company. And I don’t have too much time to input the full log manually.
  2. Yes, I have tried to use initrd flash script to flash each board independently, and each flash was successful. This is the command:
sudo ionice -c 1-n 0 ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --flash-only --massflash 1
5

Why you have 2 BOARDSKU here?
In your case, please use the following parameters:

BOARDID=3668 
BOARDSKU=0001
FAB=300

It would be hard for us to check the issue in details. Please also review the full flash log and serial console log with the passed one to find if there’re other errors.

6

Hi,

1.I change the parameters and try to flash using the following command:

sudo BOARDID=3668 FAB=300 BOARDSKU=0001 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --network usb0 -massflash 5 jetson-xavier-nx-devkit-emmc mmcblk0p1

sudo ionice -c 1-n 0 ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --flash-only --massflash 2

But it seems that this solution doesn’t work, I encounter the same problem.
2.I have reviewed the full flash log with the passed one and there are no other errors.

7

Could you add set -x in tools/kernel_flash/images/l4t_flash_from_kernel.sh as following to enable more logs and compare them again?

# Usage: ./l4t_flash_from_kernel.sh
# This script flashes the target from the Network File Systems on the target or
# from the host using the images inside the flash package generated by
# l4t_create_flash_image_in_nfs

set -e
+set -x
9

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