Flashing Failed - Drive OS

Hello,

I am facing an error while flashing. Below are the details of the error.
Target HW: Drive AGX Orin
Host PC: Ubuntu 20.04.5 LTS
Drive OS 6.0.4
Error: ‘Failed to execute commands with GenericInstaller’



driveinstaller.log (348.1 KB)

Dear @JaxSpar,
Could you share complete flashing logs(~/.nvsdkm/) folder

Thanks for the quick response Siva.
Can’t find a folder which explicitly says flashing log. But do you mean the logs folder itself?

Dear @JaxSpar,
Yes. Please zip the ~/.nvsdkm/sdkm*.log and logs folder

Attaching log files:
logs.zip (613.2 KB)

If at all I am looking in the right direction >>/tmp/tmp_NV_DRIVE_FLASH_DRIVE_COMP.sh<< returns a message saying >>The user is already a member of ‘dialout’<<
yet it is unable to read files in driveinstaller directory

Hi @JaxSpar
May I know which SDK Manager version you’re using? Thanks.

Hi Vick,
Thanks for responding!
sdkmanager_1.8.1-10392_amd64

Thanks for the information. I’ll check it with our team and get back to you.

1 Like

In the meantime, please double check the System Requirements and make sure all are met. Thanks.

It looks you encountered below known issue mentioned in DRIVE OS 6.0.4 Linux Release Notes. Please try if reflashing helps (only the flashing step).

Thanks for getting back Nick. I have tried re-creating the flash image & flashing itself multiple times but did not work. Meanwhile I shall try looking the issue in different perspective on Monday.

Hey @VickNV & @SivaRamaKrishnaNV
the issue is fixed now, may be the host pc restart solved the issue.
Thanks for the support.

Good to hear you solved the issue. Thanks for letting us know.

Facing multiple flashing issues here too. I see three issues so far:

  1. Serial ports in use (even if you’ve exited minicom, might need to reset serial ports or reboot host computer)

  2. Retry flash: Image creation during a retry will wipe previously generated files and not create them again under ~/nvidia/ folder. This is remedied by uninstalling driveos and reinstalling each time a failure occures.

3. Unresolved: “Binding of partitions failed !”

This issue seems to be different. Seems it fails after putting the board in recovery mode due to “No valid Tegra-A … must have a primary SOC” but the prior step of putting “Tegra-A on hold” and “Tegra-A in recovery” was successful.

[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [GetInfoRom(616)] : Read skuinfo from InfoRom...
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: Execute command on Aurix serial port
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [CheckFirmwareisAFW(596)] : AFW firmware found
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [setTargetConfigt23xInfoRomInfo(716)] : 940-63710-0010-D00
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [setTargetConfigt23xInfoRomInfo(717)] : None
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [setTargetConfigt23xInfoRomInfo(724)] : ******  s_InforomSkuVersion   D00
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [setTargetConfigt23xInfoRomInfo(725)] : ******  s_InforomProdInfo   940-63710-0010
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [findTargetBaseBoardName(763)] : baseBoardName found :: p3710-10-s05
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [findBaseBoardName(3440)] : Detected baseboard with default ChipSku  :: p3710-10-s05
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [updateFindBoardData(353)] : Connected Board Name details ::  baseBoard name - p3710-10-s05
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold...
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [GetTegrasAssocWithAurix(509)] : Done
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [getListTargetsInRecovery(3508)] : Bus 003 Device 004: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [GetTegrasAssocWithAurix(534)] : Setting Tegra-A in recovery...
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [GetTegrasAssocWithAurix(538)] : Done
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [getListTargetsInRecovery(3508)] : Bus 003 Device 004: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [GetTegrasAssocWithAurix(548)] : No valid Tegra-A ... must have a primary SOC
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] command line used was:
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] ['/home/user/nvidia/nvidia_sdk/DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422]
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422]
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] ^[[01;31mCould not put Tegra-A in recovery^[[0m
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422]
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] [bootburn]: [__exit__(82)] : Exception in critical section :<class 'OSError'>
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422]
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] ^[[01;31mException caught in bootburn ^[[0m
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] returning to directory /home/user/nvidia/nvidia_sdk/DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/driveinstaller
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] Cleaning up ...
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] Cleaning temp dir
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] Traceback (most recent call last):
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] File "/home/user/nvidia/nvidia_sdk/DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 288, in bootburn
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] bootburnLib.CheckRecoveryTargets()
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] File "/home/user/nvidia/nvidia_sdk/DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3453, in CheckRecoveryTargets
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] self.aurix.GetTegrasAssocWithAurix(self.targetConfig.s_AurixPort)
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] File "/home/user/nvidia/nvidia_sdk/DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_aurix.py", line 549, in GetTegrasAssocWithAurix
[2022-09-07 12:28:10,705 root DEBUG utilities.py 294 89422] AbnormalTermination("Could not put {} in recovery".format(name), nverror.NvError_ResourceError)
[2022-09-07 12:28:10,706 root DEBUG utilities.py 294 89422] File "/home/user/nvidia/nvidia_sdk/DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 249, in AbnormalTermination
[2022-09-07 12:28:10,706 root DEBUG utilities.py 294 89422] raise OSError(errorCode)
[2022-09-07 12:28:10,706 root DEBUG utilities.py 294 89422] OSError: 15
[2022-09-07 12:28:10,706 root INFO runner.py 37 89422] Failed to bind partitions!

Hi @ibreakthings

Please help create a new topic. If you think it’s related, you can link it to this one. Thanks.

Created. Linking here: DriveOS 6.0.4 Flashing Failures

I met the same things. uninstall the download file. not use retry when flash fail. just close sdkmanager and reopen