[Jetson Linux 35.5.0 GA] Failed to flash image to jetson device due to Error: missing readinfofile

Hi Nvidia Team,

I try to use jetson linux r35.5 release to flash image to jetson orin kit, but faced an Error: missing readinfofile (Linux_for_Tegra/bootloader/readinfo_t234_min_dev.xml).

The steps as follows:

https://docs.nvidia.com/jetson/archives/r35.5.0/DeveloperGuide/IN/QuickStart.html#to-flash-the-jetson-developer-kit-operating-software

Step-6 try to build and flash got problem.

Logs:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal 
/home/hengyongchao/NVIDIA/test_jetson_linux_r35.5.0/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_qspi.xml --showlogs --network usb0 jetson-orin-nano-devkit internal
************************************
*                                  *
*  Step 1: Generate flash packages *
*                                  *
************************************
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY=""  /home/hengyongchao/NVIDIA/test_jetson_linux_r35.5.0/Linux_for_Tegra/flash.sh --no-flash --sign  -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

###############################################################################
# L4T BSP Information:
# R35 , REVISION: 5.0
# User release: 0.0
###############################################################################
ECID is 0x00000
Error: missing readinfofile (/home/hengyongchao/NVIDIA/test_jetson_linux_r35.5.0/Linux_for_Tegra/bootloader/readinfo_t234_min_dev.xml).

Usage: sudo ./flash.sh [options] t186ref internal
    options:
        -c <cfgfile> ---------- Flash partition table config file.
        -d <dtbfile> ---------- device tree file.
        -f <flashapp> --------- Path to flash application (tegraflash.py)
        -h -------------------- print this message.
        -i <enc rfs key file>-- key for disk encryption support.
        -k <partition id> ----- partition name or number specified in flash.cfg.
        -m <mts preboot> ------ MTS preboot such as mts_preboot_si.
        -n <nfs args> --------- Static nfs network assignments
                                <Client IP>:<Server IP>:<Gateway IP>:<Netmask>
        -o <odmdata> ---------- ODM data.
        -r -------------------- skip building and reuse existing system.img.
        -t <tegraboot> -------- tegraboot binary such as nvtboot.bin
        -u <PKC key file>------ PKC key used for odm fused board.
        -v <SBK key file>------ Secure Boot Key (SBK) key used for ODM fused board.
        -w <wb0boot> ---------- warm boot binary such as nvtbootwb0.bin
        -x <tegraid> ---------- Tegra CHIPID.
        -B <boardid> ---------- BoardId.
        -C <cmdline> ---------- Kernel commandline arguments.
                                WARNING:
                                Each option in this kernel commandline gets
                                higher preference over the values set by
                                flash.sh. In case of NFS booting, this script
                                adds NFS booting related arguments, if -i option
                                is omitted.
        -F <flasher> ---------- Flash server such as cboot.bin.
        -G <file name> -------- Read partition and save image to file.
        -I <initrd> ----------- initrd file. Null initrd is default.
        -K <kernel> ----------- Kernel image file such as zImage or Image.
        -L <bootloader> ------- Bootloader such as cboot.bin or u-boot-dtb.bin.
        -M <mts boot> --------- MTS boot file such as mts_si.
        -N <nfsroot> ---------- i.e. <my IP addr>:/my/exported/nfs/rootfs.
        -R <rootfs dir> ------- Sample rootfs directory.
        -S <size> ------------- Rootfs size in bytes. Valid only for internal
                                rootdev. KiB, MiB, GiB short hands are allowed,
                                for example, 1GiB means 1024 * 1024 * 1024 bytes.
        -T <ext num sectors> ---The number of the sectors of the external storage device.
                                The default value is 122159104 if this option is not set.
        -Z -------------------- Print configurations and then exit.
        --no-flash ------------ perform all steps except physically flashing the board.
                                This will create a system.img.
        --external-device------ Generate flash images for external devices
        --sparseupdate--------- only flash partitions that have changed. Currently only support SPI flash memory
        --no-systemimg -------- Do not create or re-create system.img.
        --bup ----------------- Generate bootloader update payload(BUP).
        --single-image-bup <part name> Generate specified single image BUP, this must work with --bup.
        --bup-type <type> ----- Generate specific type bootloader update payload(BUP), such as bl or kernel.
        --multi-spec----------- Enable support for building multi-spec BUP.
        --clean-up------------- Clean up BUP buffer when multi-spec is enabled.
        --usb-instance <id> --- Specify the USB instance to connect to;
                                <id> = USB port path (e.g. 3-14).
        --no-root-check ------- Typical usage of this script require root permissions.
                                Pass this option to allow running the script as a
                                regular user, in which case only specific combinations
                                of command-line options will be functional.
        --uefi-keys <keys_conf> Specify UEFI keys configuration file.
        --rcm-boot ------------ Do RCM boot instead of physically flashing the board.
        --sign ---------------- Sign images and store them under "bootloader/signed"
                                directory. The board will not be physically flashed.
        --image --------------- Specify the image to be written into board.
        --boot-chain-flash <c>  Flash only a specific boot chain (ex. "A, "B", "all").
                                Defaults to "all", inputs are case insensitive.
                                Not suitable for production.
        --boot-chain-select <c> Specify booting chain (ex. "A" or "B") after the board is flashed.
                                Defaults to "A", inputs are case insensitive.
        --pv-crt -------------- The certificate for the key that is used to sign cpu_bootloader
        --with-systemimg ------ Generate system images also when using -k option
        --pv-enc <enc_key>----- The encryption key that is used to encrypt cpu_bootloader.
        --uefi-enc <uefi_enc_key> Key file (0x19: 16-byte; 0x23: 32-byte) to encrypt UEFI payloads
        --uda-dir-------------- Directory to store user data that will be encrypted in UDA partition.
        --separate-rcmboot-binary ------ Enable use of different binaries for rcmboot and coldboot.
        --generic-passphrase -- Use generic passphrase for disk encryption.
        --disable-random-iv --- Disable generation of random IV, SALT1, SALT2 and DERSTR.
        --read-info ----------- Read and display board related info, fuse info (based on fuse_t234.xml),
                                and EEPROM content.
        --reuse-uuid ---------  Reuse uuid which is already generated first time.

Error: /home/hengyongchao/NVIDIA/test_jetson_linux_r35.5.0/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/hengyongchao/NVIDIA/test_jetson_linux_r35.5.0/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...

Search a topic, but does not works for me!! Image fails to build on missing readinfofile (xxx/readinfo_t234_min_dev.xml)

Maybe delete the BSP folder and try again.
Or use SDK Manager.

I download the files form Jetson Linux | NVIDIA Developer

and Installation instructions here, Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation)

I belive that the document is right.

Either there is some typo in the command you used, or something is missing in the BSP.

I got the answer, I make a mistake, I confused xavier and orin development boards. Hope it helps others.

Yeah, i created that post originally, in the mean time i got the same error several time and the solution doesn’t always work.

The only solution is to delete the BSP folder and restart from scratch :( unfortunately.

The only pattern that i might have identified is that is often follows some other failure. Once a generation of a rootfs failed in some particular stage the BSP doesn’t seem to be recoverable anymore, even when the cause of the original failure has been fixed. Probably there is a way by knowing exactly which files to delete but i never figured it out.

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