Please provide the following info (tick the boxes after creating this topic): Software Version
[*] DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
[*] Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
[*] other
SDK Manager Version
[*] 1.9.10816
other
Host Machine Version
[*] native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
Hi sir,
when I upgrade to 6.0.5 with the SDK manager, the tool report flash failed
Dear @sunjiandong,
I see βecho Failed to flash device: detected no board connected to host with USB cableβ in above attached image. Make sure you have connected board to host.
Firstly please check below things.
Check if lsusb outputs Nvidia device after connecting host and target. You can verify lsusb output before and after the connection. Share the lsusb outputs.
Check if tegra can be set into recovery mode. You can connect to aurix console with minicom using sudo minicom -D /dev/ttyACM1 and run tegrarecovery x1 on and tegrareset x1. Now verify if you see an additional Nvidia device in lsusb output on host. After that put the target back in normal mode by running tegrarecovery x1 offandtegrareset x1` on aurix console.
If flashing fails, attach the complete sdkm logs for investigation.
Hi sir
Thanks for your reply. After set into the recovery mode, I can see the there have a APX port.Is it right? And I use the cable which is from the Nvidia. nvsdkm.tar.gz (170.4 KB)
After checking your logs, we think it can be solved with the workaround mentioned at DRIVE AGX Orin Flashing issue - #5 by VickNV.
Please also see how the developer solved their problems in the topic.
Hi sir
From the case you list, I can see it can see it failed after the ADB port is enumerate but I failed after the Orin enter into recovery mode.
And I also change the type-c cable and use the usb2.0. It still failed.
Thanks!
Dear @sunjiandong,
Thank you for sharing logs. I will share the logs for internal investigation.
Mean while, I would like to check manual flashing method instead of using sdkmanager.
Please try below and confirm
Put the target in recovery mode
sudo minicom -D /dev/ttyACM1 # on host
tegrarecovery x1 on #on Aurix console
tegrareset x1 #on Aurix console
bind and flash
cd drive-foundation
make -f make/Makefile.bind BOARD=p3710-10-s05 PCT=linux clean
make -f make/Makefile.bind BOARD=p3710-10-s05 PCT=linux
tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi
Put the target in normal mode
sudo minicom -D /dev/ttyACM1 # on host
tegrarecovery x1 off #on Aurix console
tegrareset x1 #on Aurix console
Please share the logs on host and aurix for these commands.
Hi sir
It refers as below when rung the command βmake β¦β
aic@caic-HP-ZBook-Power-G7-Mobile-Workstation:~/nvidia/nvidia_sdk/DRIVE_OS_6.0.5_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation$ make -f make/Makefile.bind BOARD=p3710-10-s05 PCT=linux clean
Direct call of makefile depreciated
Do not use makefile directly. Please use bind_partitions script
Hi sir
Yes, It can access successfully.
Does the bootburn have flash all images? Is there any other partitions need to flash? whether this command is the same with sdkmanager?
Thanks!
Dear @sunjiandong,
Yes. The above command flashes DRIVE OS onto target.
sdkmanager detects the board automatically using find_board_name and uses required configuration to flash board. I notice find_board_name seems to be failing as per sdkm logs
[2022-12-15 20:38:26,985 root DEBUG utilities.py 327 4622] Executing board_find_cmd python3 /home/caic/nvidia/nvidia_sdk/DRIVE_OS_6.0.5_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/bootburn.py --find_board_name -x /dev/ttyACM1
[2022-12-15 20:38:30,419 root DEBUG pdk_bind.py 213 4622] Bind partitions failed !
Traceback (most recent call last):
File "/dvs/git/dirty/git-master_foundation/out/embedded-foundation-generic-release-none/packaging/stage_driveinstaller/driveinstaller/module/pdk_bind.py", line 157, in pdk_bind
File "/dvs/git/dirty/git-master_foundation/out/embedded-foundation-generic-release-none/packaging/stage_driveinstaller/driveinstaller/utils/utilities.py", line 333, in find_board_name
File "/dvs/p4/build/sw/tools/linux/mods/python-3.6.3-glibc-2.5/lib/python3.6/subprocess.py", line 291, in check_call
subprocess.CalledProcessError: Command 'python3 /home/caic/nvidia/nvidia_sdk/DRIVE_OS_6.0.5_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/bootburn.py --find_board_name -x /dev/ttyACM1' returned non-zero exit status 43.
[2022-12-15 20:38:30,421 root ERROR pdk_bind.py 214 4622] Binding of partitions failed ! Check log for more details.
Could you check running the the same command and confirm if notice the same error.
Hi sir
Yes, it notice the same error when running this command manually. But it is ok when I add sudo before bootburn.py --find_board_name -x /dev/ttyACM1.
The ok log:
[bootburn]: [validateTargetBoardName(748)] : boardName p3710-10-s05 matches with the connected board
[bootburnTegra-A]: [StartNewSession_t23x(785)] : Target
[bootburnTegra-A]: [StartNewSession_t23x(786)] : Target ECID: 0x
[bootburnTegra-A]: [GetTargetECID(796)] : Target BR_CID: 0x80012344705DD2E30400000002030240
[bootburnTegra-A]: [CheckFuseForAuthentication(814)] : Target Authentication State : SHA-2
[bootburnTegra-A]: [GenAdbSerialNum(575)] : ADB serial number is 8S2TQBHG8000001060I0
the failed:
[bootburn]: [setTargetConfigt23xInfoRomInfo(725)] : ****** s_InforomProdInfo 940-63710-0010
[bootburn]: [validateTargetBoardName(748)] : boardName p3710-10-s05 matches with the connected board
[bootburnTegra-A]: [executeShellCommand(164)] : shell command β /home/caic/nvidia/nvidia_sdk/DRIVE_OS_6.0.5_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/001/017 --new_session --chip 0x23 failed
[bootburnTegra-A]: [executeShellCommand(166)] : Output: bβFile rcm_state open failed\nERROR: failed to update RCM_STATE to 0\nβ
[bootburnTegra-A]: [executeShellCommand(168)] : Return code: 16
[bootburnTegra-A]: [executeShellCommand(170)] : stdout: bβFile rcm_state open failed\nERROR: failed to update RCM_STATE to 0\nβ
[bootburnTegra-A]: [executeShellCommand(172)] : stderr: None
[bootburnTegra-A]: [sendRcmCommand(776)] : Unable to execute tegrarcm command β /home/caic/nvidia/nvidia_sdk/DRIVE_OS_6.0.5_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/001/017 --new_session --chip 0x23
command line used was:
[βtools/flashtools/bootburn/bootburn.pyβ, ββfind_board_nameβ, β-xβ, β/dev/ttyACM1β]
TEGRARCM β Unable to execute command
Exception 43 raised in bootburn_active
Traceback (most recent call last):
Dear @sunjiandong,
Thanks for update. It seems when you use sudo, you donβt see any issue. Do you see display on target after flashing with bootburn command?
Is there any permission issues for the user account? Could you check if launching sdkmanager with sudo helps to bypass this issue?
It looks something to do with your host environment.
Please try another host system or use the docker container way to install (follow Installation Methods).
