Failed to Flash DRIVE Software 10.0 (rev.2)

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
25

I have responded to the private message you sent.
I would appreciate it if you could take a moment to review it.

27

Dear @jaeikb38 ,
You can flash DRIVE SW 10.0 only on Xavier A using bootburn command(If you don’t see selecting flashing Tegra A option using sdkmanager in step 3).
Please see DRIVE_SW_10.0_References/DRIVE_Software/index.html#page/DRIVE_OS_Linux_SDK_Development_Guide/Flashing%20Customization/flashing_bootburn.html

Like below commands

#Keep the tegra A in recoverymode using tegrarecovery x1 on && tegrareset x1  on aurix console
cd <top>/drive-t186ref-foundation
make -f Makefile.bind PCT=linux BOARD=<platform>
To flash all images for Linux:
cd <top>/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x
./bootburn.sh -b <platform> -B qspi

#Keep the tegra A in normal mode after flashing using tegrarecovery x1 off && tegrareset x1 on aurix console
28

I followed the commands you suggested, but an error occurred during the process.

When running the following command:

./bootburn.sh -b <platform> -B qspi

I received the error:

Multiple tegra instances found. Use -I <Bus_No> <Device_No>

so I checked other tegra instances by lsusb.

glad@glad:~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x$ lsusb
Bus 002 Device 004: ID 0424:5807 Standard Microsystems Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 2232:1083 Silicon Motion 
Bus 001 Device 005: ID 8087:0aaa Intel Corp. 
Bus 001 Device 026: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 025: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 024: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 023: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 055: ID 0955:7019 NVidia Corp. 
Bus 001 Device 056: ID 0955:7019 NVidia Corp. 
Bus 001 Device 022: ID 0424:2807 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I used the <Bus_No> <Device_No> for NVIDIA Corp., but another error occurred

glad@glad:~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x$ ./bootburn.sh -b e3550b03-t194a -B qspi -I 001 055

I tried both Bus 001 Device 055 and Bus 001 Device 056, but the same error occurred.

Error Code ffffffff
nvimagegen usage:

nvimagegen --bct <BCT_FILE> --mb1bct <MB1_BCT_FILE> --cfg <CFG_FILE>
  --bct <file>
	Optional, bct file(file), which will be updated with ODM-Data,
	PT StartInfo if provided.
	This update happens in unsign/unencrypted section of BCT
  --mb1bct <file>
	Optional, mb1_bct file(file), which will be updated with Firmware info.
	This update happens in unsign/unencrypted section of MB1_BCT
  --membct <file1> <file2> <file3> <file4>
	Optional, mem_bct file(file)
  --chip <Chip ID>
	Mandatory, Specifies chip id. The chip id of t18x is 0x18.
  --chipver <Chip version>
	Mandatory, Specifies chip version.
  --cfg <file>
	Optional, input cfg file containing partition layout used while flashing
  --pkc <file>
	Optional, pkc key used for signing the binary
  --showpt
	Optional, display the Partition Table on the screen.
  --rcm
	Optional, create images need for RCM Boot.
  --skipfs
	Optional, Skip filesystem partitions.
  --part <partition name>
	Optional, input partition names and only the binary of the partitions
	will be generated.
  --dtodmdata <odm-data parameter>
	Optional, Specifies the dt odm-data parameter
  --signbin <file> <magic id>
	Optional, Specifies a binary for signing.
  --parentcfg <file>
	Optional, parent cfg file location
  --prefix <name>
	Optional, Name to be prepended to the images generated.
  --guestcfg
	Optional, Flag to indicate that this is guest configuration along with guest id.
  --setvmax <Board Vmax>
	Optional, Specifies the board max micro voltage.
  --ecid
	Optional, ECID of target to be used in conjunction with --signbin.
:[E]: QbFindAndCreateImages              : 1162: Error (null) (0xff00)
:[E]: Failed to exectute nvimagegen
:[E]: QbCreatePartition                  : 1497: Error (null) (0xff00)
:[E]: failed to find and create images
Failed to create partitions
:[E]: main                               :  784: Error (null) (0xff00)
:[E]: Creating Partition images failed
finish nvimagegen
Error Code ff00
nvimagegen usage:

nvimagegen --bct <BCT_FILE> --mb1bct <MB1_BCT_FILE> --cfg <CFG_FILE>
  --bct <file>
	Optional, bct file(file), which will be updated with ODM-Data,
	PT StartInfo if provided.
	This update happens in unsign/unencrypted section of BCT
  --mb1bct <file>
	Optional, mb1_bct file(file), which will be updated with Firmware info.
	This update happens in unsign/unencrypted section of MB1_BCT
  --membct <file1> <file2> <file3> <file4>
	Optional, mem_bct file(file)
  --chip <Chip ID>
	Mandatory, Specifies chip id. The chip id of t18x is 0x18.
  --chipver <Chip version>
	Mandatory, Specifies chip version.
  --cfg <file>
	Optional, input cfg file containing partition layout used while flashing
  --pkc <file>
	Optional, pkc key used for signing the binary
  --showpt
	Optional, display the Partition Table on the screen.
  --rcm
	Optional, create images need for RCM Boot.
  --skipfs
	Optional, Skip filesystem partitions.
  --part <partition name>
	Optional, input partition names and only the binary of the partitions
	will be generated.
  --dtodmdata <odm-data parameter>
	Optional, Specifies the dt odm-data parameter
  --signbin <file> <magic id>
	Optional, Specifies a binary for signing.
  --parentcfg <file>
	Optional, parent cfg file location
  --prefix <name>
	Optional, Name to be prepended to the images generated.
  --guestcfg
	Optional, Flag to indicate that this is guest configuration along with guest id.
  --setvmax <Board Vmax>
	Optional, Specifies the board max micro voltage.
  --ecid
	Optional, ECID of target to be used in conjunction with --signbin.
:[E]: QbFindAndCreateImages              : 1162: Error (null) (0xff00)
:[E]: Failed to exectute nvimagegen
:[E]: QbCreatePartition                  : 1497: Error (null) (0xff00)
:[E]: failed to find and create images
Failed to create partitions
:[E]: main                               :  784: Error (null) (0xff00)
:[E]: Creating Partition images failed
finish nvimagegen
Error Code ff00
nvimagegen usage:

nvimagegen --bct <BCT_FILE> --mb1bct <MB1_BCT_FILE> --cfg <CFG_FILE>
  --bct <file>
	Optional, bct file(file), which will be updated with ODM-Data,
	PT StartInfo if provided.
	This update happens in unsign/unencrypted section of BCT
  --mb1bct <file>
	Optional, mb1_bct file(file), which will be updated with Firmware info.
	This update happens in unsign/unencrypted section of MB1_BCT
  --membct <file1> <file2> <file3> <file4>
	Optional, mem_bct file(file)
  --chip <Chip ID>
	Mandatory, Specifies chip id. The chip id of t18x is 0x18.
  --chipver <Chip version>
	Mandatory, Specifies chip version.
  --cfg <file>
	Optional, input cfg file containing partition layout used while flashing
  --pkc <file>
	Optional, pkc key used for signing the binary
  --showpt
	Optional, display the Partition Table on the screen.
  --rcm
	Optional, create images need for RCM Boot.
  --skipfs
	Optional, Skip filesystem partitions.
  --part <partition name>
	Optional, input partition names and only the binary of the partitions
	will be generated.
  --dtodmdata <odm-data parameter>
	Optional, Specifies the dt odm-data parameter
  --signbin <file> <magic id>
	Optional, Specifies a binary for signing.
  --parentcfg <file>
	Optional, parent cfg file location
  --prefix <name>
	Optional, Name to be prepended to the images generated.
  --guestcfg
	Optional, Flag to indicate that this is guest configuration along with guest id.
  --setvmax <Board Vmax>
	Optional, Specifies the board max micro voltage.
  --ecid
	Optional, ECID of target to be used in conjunction with --signbin.
error-tool-nvimagegen

Could you please review them and advise on the possible cause of the issue?

29

I was wondering if there might be any additional solutions you’ve found regarding this issue?

30

Can you check removing other connected board to host.

31

Ok, I checked there is only one board connected to host.

Bus 001 Device 024: ID 0955:7019 NVidia Corp.

and I got this error.

glad@glad:~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x$ ./bootburn.sh -b e3550b03-t194a -B qspi -I 001 024
Successfully acquired lock over /var/lock/LCK..bootburn
tmp_list_misc_subcfg located at /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_3V60MugdxM/tmp_list_subcfg
file /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/../../../..//out/e3550b03-t194a/platform_config.json does not exist

command options used = -b e3550b03-t194a -B qspi -I 001 024

 ------------ Stack Trace ------------
stack frame 0 - 317 AbnormalTermination /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
stack frame 1 - 3480 HelperVerifyFileExists /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
stack frame 2 - 3638 ValidatePlatCfg /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
stack frame 3 - 3647 ProcessPlatCfg /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
stack frame 4 - 374 source /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_active.sh
stack frame 5 - 1143 main ./bootburn.sh
-------------------------------------

Tool OutPut:
Tool OutPut to stderr:
error-invalid-params
32

We recently had a visit from Hancom MDS, the local NVIDIA reseller, who helped us identify an issue during the update process using the SDK Manager.

  1. Drive OS Update: This works as expected because we can manually select only Tegra A during the installation process.
  2. Software Update: This step fails, and we believe it’s due to the SDK Manager automatically selecting both Tegra A and Tegra B simultaneously. However, our Xavier model only includes Tegra A, and does not have Tegra B, which likely causes the update to fail.

We would like to ask:
Is there a way to disable or modify this automatic selection behavior in SDK Manager so that only Tegra A is selected for software updates?

Any guidance or workaround would be greatly appreciated. Thank you!

33

Dear @jaeikb38 ,
If you are using sdkmanager GUI, don’t you see flash screen like in Install DRIVE with SDK Manager :: DRIVE Platform Installation Guide with NVIDIA SDK Manager where we can select Flash A+B/Flash A/ Flash B in drop down menu? By default it selects Flash A+B option. We need to manually change in UI to proceed further.

34

As you suggested, I looked for a dropdown menu to change the Flash option from “Flash A+B” to “Flash A only” in the SDK Manager GUI. However, in the current interface (see attached screenshot), I do not see any dropdown menu or clickable option to change this setting — it appears fixed as “Flash Xavier A+B in parallel.”

Could you please clarify:

  • Is there any way to manually change the Flash option to “Flash A only” in this version of SDK Manager?
  • Or is there a workaround (possibly using CLI or editing config files) to avoid flashing Tegra B?
    Nvidia sdk manager
    Nvidia sdk manager1496×1496 181 KB
35

Dear @jaeikb38 ,
Is your board not a Xavier devkit?

Does the bootburn flash commands provided at Failed to Flash DRIVE Software 10.0 (rev.2) - #27 by SivaRamaKrishnaNV not worked for you. Make sure only one board is connected to host.

Note: before flashing you need to manually keep the board in recovery mode from aurix console. After flashing finishes, keep the board in normal mode from aurix console to access tegra console.