The connected Jetson device is not ready for flash

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

I am trying to reflash Jetpack 6.2.1 on the Jetson Orin Nano device. But, when I flash it using sdk manager to NVMe, “The connected Jetson device is not ready for flash” error is occuring . So I have followed the below forum to understand that issue.

Based on Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation , I am using the below command to flash the image.

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” \
–showlogs --network usb0 jetson-orin-nano-devkit internal

But I am getting following error:
*
Retrieving EEPROM data
[ 10.4012 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/user/Downloads/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 10.4059 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 10.4070 ] Dumping customer Info
[ 10.4090 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct
[ 10.4111 ] tegrabct_v2 --brbct tmp.bct --chip 0x23 0 --custinfo /home/user/Downloads/Linux_for_Tegra/bootloader/custinfo_out.bin
[ 10.4120 ] File tmp.bct open failed
[ 10.4122 ] Error: try getting custinfo fail. Moving on
[ 10.4122 ] Rebooting to recovery mode
[ 10.4131 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 10.4141 ] Rebooting to recovery mode
[ 10.4149 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
Parsing board information failed.
Error: failed to generate images
Cleaning up…*

How can I solve this?

2

Moving to Jetson Orin Nano forum to get resolution.

4

Hi @ajin.a,

Hope you’re doing well!

Just to confirm a couple of things to help narrow down the issue:

  • Are you using the Jetson Orin Nano devkit?
  • Can you confirm the board is in recovery mode? Run on your host PC the following command: lsusb

Nico
Best regards
Embedded Software Engineer at ProventusNova

5

FYI, I am using Jetson Orin Nano devkit and set the board to Recovery mode by shorting the REC and GND pins.

I am able to flash the device from sdk manager now. But still I am not able to flash it using l4t_initrd_flash.sh . I am getting the same error I showed before.

_info.bin
[ 10.4868 ] Retrieving EEPROM data
[ 10.4868 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/user/Downloads/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 10.4906 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 10.4918 ] Dumping customer Info
[ 10.4928 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct

[ 10.4948 ] tegrabct_v2 --brbct tmp.bct --chip 0x23 0 --custinfo /home/user/Downloads/Linux_for_Tegra/bootloader/custinfo_out.bin
[ 10.4958 ] File tmp.bct open failed
[ 10.4960 ] Error: try getting custinfo fail. Moving on
[ 10.4960 ] Rebooting to recovery mode
[ 10.4970 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 10.4979 ] Rebooting to recovery mode
[ 10.4989 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
Parsing board information failed.
Error: failed to generate images
Cleaning up…*

My actual goal is to do kernel customisation. So I am following Kernel Customization — Jetson Linux<br/>Developer Guide 34.1 documentation manual and Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation.

Please see the steps:

  • Downloaded Jetson_Linux_R36.4.4_aarch64.tbz2, aarch64–glibc–stable-2022.08-1.tar.tbz2

  • Sync the kernel sources by using the command
    ./source_sync.sh

  • Modified usb_wwan.c, option.c and usb-serial.c for integrating a communication module

  • Changed the .config file using menuconfig as per I need.

  • Built the kernel
    ./nvbuild.sh -o $PWD/kernel_out

  • Replaced Linux_for_Tegra/kernel/Image with a copy of this file:

    kernel_out/arch/arm64/boot/Image

  • Set up for flash

    cd Linux_for_Tegra/
    sudo ./tools/l4t_flash_prerequisites.sh
    sudo ./apply_binaries.sh

  • Set the board in recovery mode

  • Flashed the Image using l4t_initrd_flash.sh

    sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \ -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” \ --showlogs --network usb0 jetson-orin-nano-devkit internal

    I have attached the log for reference.

    log.txt (13.5 KB)

But even without kernel customisartion, I am getting the same error. On that I have worked out with Tegra_Linux_Sample-Root-FileSystem_R36.4.4_aarch64 file.

6

Hi

Please try to use lsusb to check whether the device in recovery mode.

Thanks

7

Hi David,

Please see this:
Bus 003 Device 010: ID 0955:7523 NVIDIA Corp. APX

8

Hi !

I can flash it now. I think that is a power related issue. After that, evenif I modified kernel source for usb and wwan drivers, that is not updated in the orin nano.

For kernel customisation I followed Kernel Customization — Jetson Linux<br/>Developer Guide 34.1 documentation procedure.
I just copied kernel_out/kernel/kernel-jammy-src/arch/arm64/boot/Image to /Linux_for_Tegra/kernel/ ,after building the image using “./nvbuild.sh -o $PWD/kernel_out”.

So my doubt is whether /boot/Image contains kernel source? I modified .config, usb , wwan drivers only.

Also is that okay to keep .config file in the kernel_out/kernel/kernel-jammy-src/ directory?

Thanks
Ajin A..

9

Hi,

Please refer to the doc instead

And complete below sections to setup custom kernel, dtb and oot modules

  • Building the Jetson Linux Kernel
  • Building the NVIDIA Out-of-Tree Modules
  • Building the DTBs

Thanks

10

I followed the same steps in Jetson Linux kernel. But my defconfig is not updated after flashing.

I created .config from menuconfig and used the command “make savedefconfig”. The resultant file renamed as my_defconfig and kept in arch/arm64/ configs folder.

Then, I put that Image file in L4T/kernel folder after built

11

I solved it by following orinNano Kernel added other driver, and need to modify the device tree, how do I need to operate - #19 by nagesh_accord

Thanks

13

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