bootFromExternalStorage: [BUG]: flashing and booting issues

Describe the issue

Followed the steps from this video: https://www.jetsonhacks.com/2021/08/25/native-boot-for-jetson-xaviers/
When I ran flash_jetson_external_storage.sh it failed with the following stacktrace:

[   0.5738 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   0.5775 ] /usr/bin/env: Traceback (most recent call last):
  File "./tegraflash.py", line 1296, in <module>
    tegraflash_run_commands()
  File "./tegraflash.py", line 1155, in tegraflash_run_commands
    interpreter.onecmd(command)
  File "/usr/lib/python3.8/cmd.py", line 217, in onecmd
    return func(arg)
  File "./tegraflash.py", line 667, in do_sign
    tegraflash_sign(exports)
  File "/home/skorol/Projects/bootFromExternalStorage/R32.6.1/Linux_for_Tegra/bootloader/tegraflash_internal.py", line 1078, in tegraflash_sign
    tegraflash_generate_bct()
  File "/home/skorol/Projects/bootFromExternalStorage/R32.6.1/Linux_for_Tegra/bootloader/tegraflash_internal.py", line 4004, in tegraflash_generate_bct
    tegraflash_generate_br_bct(True)
  File "/home/skorol/Projects/bootFromExternalStorage/R32.6.1/Linux_for_Tegra/bootloader/tegraflash_internal.py", line 3510, in tegraflash_generate_br_bct
    run_command(command)
  File "/home/skorol/Projects/bootFromExternalStorage/R32.6.1/Linux_for_Tegra/bootloader/tegraflash_internal.py", line 202, in run_command
    log = print_process(process, enable_print)
  File "/home/skorol/Projects/bootFromExternalStorage/R32.6.1/Linux_for_Tegra/bootloader/tegraflash_internal.py", line 164, in print_process
    outputchar = output.decode('ascii')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)
Error: /home/skorol/Projects/bootFromExternalStorage/R32.6.1/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/skorol/Projects/bootFromExternalStorage/R32.6.1/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up...

Which version of Ubuntu on the Host machine Ubuntu version: 20.04.2 LTS

Which Jetson Jetson: Xavier NX

To Reproduce Steps to reproduce the behavior: just run flash_jetson_external_storage.sh following the video guide

Expected behavior Flashing should be completed.

About this issue

Original URL
State: open
Created 3 years ago
Comments: 25 (5 by maintainers)

Most upvoted comments

Most of these script issues have been addressed now.

jetsonhacks on Sep 3, 2021

You also need to resize the file system itself in addition to resizing the partition.

sudo resize2fs /dev/nvme0n1p… ( the APP parition)

anhmiuhv on Sep 16, 2021

I’m have an Xavier NX, with a SK Hynix 512 MB Gen 3x4 drive, no sd card. It asks for the username/password from screen too, I just have to sudo screen to get to that part. I’m trying to set this up headless, so maybe that is the problem. After the flashing script exits, do I turn off the jetson? I may be making a silly mistake between the end of the script and trying to screen or putty into it. I’ll try hooking it up to a monitor and keyboard this time, I’ve ran that script maybe 20 times.

Thanks for your awesome videos, I enjoy the style of them greatly!

Thank you for the kind words. Some people have reported issues with oem-config not coming up correctly. anhmiuhv is one of the NVIDIA engineers who works on this, this is reported in another issue:

Flash from external storage should already flash to emmc in the process.

Oem-config is expected to run fine when booting from NVMe; but in case when flashing to NVMe and oem-config fails to start, you can run

sudo ./tools/l4t_create_default_user.sh -u ubuntu -p ubuntu # this command create username ubuntu and password ubuntu

to skip oem-config

You’ll need to be in the Linux_for_Tegra directory when executing the above command. Note that you may have to expand your APP partition to fill up the rest of your disk. That’s part of the config walk through process. I don’t know yet if this is due to a change that they’re making for adding this feature to the GUI SDK Manager, or some other issue.

I know that people of AGX Xavier are experiencing this issue.

jetsonhacks on Sep 15, 2021