No, it can’t boot up. The screen goes blank after the NVIDIA logo shown in the attached picture.
Hi,
You cannot use a monitor to tell whether a board is really booting up or not. You need to use serial console log to tell.
1 Like
I’ll try this and get back ASAP.
Is there any way I can still do a fresh install with the SDKManager without following this article?
Can you figure out any workaround from the log files I shared?
Try this method:
1 Like
Thanks! I’ll check and get back.
I’ve tried the following command. Here’s the output,
asif@ubuntu-asif:~/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash$ sudo BOARDID=3767 BOARDSKU=0003 FAB=300 ./l4t_initrd_flash.sh
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh: line 48: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash.func: line 216: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
************************************
* *
* Step 1: Generate flash packages *
* *
************************************
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 369: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 561: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY="" /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/flash.sh --no-flash --sign /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash
Error: Invalid target board - /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.
Usage: sudo ./flash.sh [options] <target_board> <rootdev>
Where,
target board: Valid target board name.
rootdev: Proper root device.
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 119537664 if this option is not set.
-U <int num sectors> ---The number of the sectors of the internal storage device.
The default value is 119537664 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.
--generic-passphrase -- Use generic passphrase for disk encryption.
--disable-random-iv --- Disable generation of random IV; IV will be 0.
Error: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...
You should read the document for how to run flash command first if this is your first time doing flash. We really didn’t ask you to just copy and paste…
2 Likes
I understand this fact and I read through this, Flashing Support — Jetson Linux<br/>Developer Guide 34.1 documentation
I tried through various commands but ended up getting the same error
Error: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...
I appreciate your support and looking forward to getting your expert opinion on whether I’m getting something wrong.
Always attach the full log.
Here’s the full log, FYI, I’ve also tried BOARDSKU=0005
asif@ubuntu-asif:~/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash$ sudo BOARDID=3767 BOARDSKU=0003 FAB=300 ./l4t_initrd_flash.sh
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh: line 48: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash.func: line 216: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
************************************
* *
* Step 1: Generate flash packages *
* *
************************************
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 369: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
/home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_create_images_for_kernel_flash.sh: line 561: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra//home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.conf: No such file or directory
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY="" /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/flash.sh --no-flash --sign /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash
Error: Invalid target board - /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh.
Usage: sudo ./flash.sh [options] <target_board> <rootdev>
Where,
target board: Valid target board name.
rootdev: Proper root device.
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 119537664 if this option is not set.
-U <int num sectors> ---The number of the sectors of the internal storage device.
The default value is 119537664 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.
--generic-passphrase -- Use generic passphrase for disk encryption.
--disable-random-iv --- Disable generation of random IV; IV will be 0.
Error: /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/asif/Downloads/Jetson_Linux_R36.2.0_aarch64/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...
I don’t feel like you have read the document:
https://docs.nvidia.com/jetson/archives/r36.2/DeveloperGuide/IN/QuickStart.html
1 Like
Thanks for sharing the link. I’ll go through it again and check if I miss anything important.
So, I followed the instruction here, Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
As I want to flash on a SD card I used the the command,
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device mmcblk0p1 \
-c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
--showlogs --network usb0 jetson-orin-nano-devkit internal
Unfortunately, I’m still getting some errors. Here’s the full log,
asif@ubuntu-asif:~/Downloads/Linux_for_Tegra$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device mmcblk0p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal
/home/asif/Downloads/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device mmcblk0p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/generic/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/asif/Downloads/Linux_for_Tegra/flash.sh --no-flash --sign -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
###############################################################################
# L4T BSP Information:
# R36 , REVISION: 2.0
# User release: 0.0
###############################################################################
ECID is 0x80012344705DD3081400000010028100
copying emc_fuse_dev_params(/home/asif/Downloads/Linux_for_Tegra/bootloader/generic/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying device_config(/home/asif/Downloads/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-device-p3767-0000.dts)... done.
copying misc_config(/home/asif/Downloads/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)... done.
./tegraflash.py --chip "0x23" --applet "/home/asif/Downloads/Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3767-0000.dts --misc_config tegra234-mb1-bct-misc-p3767-0000.dts --bins "mb2_applet applet_t234.bin" --cmd "dump eeprom cvm cvm.bin; dump try_custinfo custinfo_out.bin; reboot recovery"
Traceback (most recent call last):
File "./tegraflash.py", line 27, in <module>
import tegraflash_internal
File "/home/asif/Downloads/Linux_for_Tegra/bootloader/tegraflash_internal.py", line 28, in <module>
from tegrasign_v3 import (compute_sha, do_key_derivation,
File "/home/asif/Downloads/Linux_for_Tegra/bootloader/tegrasign_v3.py", line 13, in <module>
from tegrasign_v3_internal import *
File "/home/asif/Downloads/Linux_for_Tegra/bootloader/tegrasign_v3_internal.py", line 13, in <module>
from tegrasign_v3_util import *
File "/home/asif/Downloads/Linux_for_Tegra/bootloader/tegrasign_v3_util.py", line 23, in <module>
import yaml
ModuleNotFoundError: No module named 'yaml'
Reading board information failed.
Error: /home/asif/Downloads/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/asif/Downloads/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...
You should have done some basic Googling before asking for every error you bump into.
sudo ./tools/l4t_flash_prerequisites.sh
Will install all packages this flashing script requires for you.
1 Like
I agree with you and I assure you that before posting each reply I google it more than once and then I post it.
The command you posted here is the fifth command from step 2 of the quick start guide. I have followed till step 6 and got the error at step 6.
I ran the command sudo ./tools/l4t_flash_prerequisites.sh before I got the error.
Some scripts in BSP is still using Python 2 instead of Python 3, so maybe l4t_flash_prerequisites.sh installs packages for Python 2 for you, but other scripts still run in Python 3, and the requirement is hence not met.
Check the Python version on your host PC.
asif@ubuntu-asif:~$ python3 -V
Python 3.7.9
I am saying that python should be linked against python2 instead of python3.
What you get with python3 doesn’t really matter.
For example, this is a snippet from l4t_flash_prerequisites.sh:
# Some of our tools (notably, boardctl) still require python2. In the past,
# we've installed python2 by installing the "python" package, but as of
# ubuntu 22.04, this package has been obsoleted and is no longer available.
# Instead, we have to install the "python2" package.
if [ "${SYSTEM_VER}" -lt 2204 ]; then
sudo apt-get install -y python python-yaml
else
sudo apt-get install -y python2
fi
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.