Install DRIVE OS with SDK Manager ：Failed to bind partitions

[zhangpeixing]

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
[*] DRIVE OS 6.0.6
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-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
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.3.10904
[*] 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

[zhangpeixing]

When using the SDK to flash the Drive AGX Orin, we encountered the following problem. How should we handle it?

[zhangpeixing]

[zhangpeixing]

driveinstaller.log (306.2 KB)

[SivaRamaKrishnaNV]

Dear @zhangpeixing,
I see below error in logs.
Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.

Please double check the connections between target and host as mentioned in Getting started section(page 9) in DRIVE AGX Orin quick start guide.

Make sure the host meets the requirements at Requirements for Your Development Environment | NVIDIA Docs

Is it possible to flash latest release i.e DRIVE OS 6.0.8.1? Note that we recommend to use docker flashing method to avoid host system state related issues. Please see Install DRIVE OS Linux Docker Containers from NGC | NVIDIA Docs to flash DRIVE OS 6.0.8.1.

[zhangpeixing]

@SivaRamaKrishnaNV

target and host

I have connected the target and host as shown in the diagram according to the instructions. Do I need to connect any other cables

[zhangpeixing]

I encountered the same error following the document operation： Install DRIVE OS Linux Docker Containers from NGC | NVIDIA Docs

[zhangpeixing]

driveinstaller.log (168.7 KB)
May I ask how to solve this problem？

[SivaRamaKrishnaNV]

Dear @zhangpeixing,
Could you please check

1. aurix and tegra console accessible via minicom?
2. Do you see an additional NVIDIA device in lsusb output on host when target is set in recovery mode?

[zhangpeixing]

Orin board with Device ID – 0955:7045 found.
Orin board device path is /dev/bus/usb/001/006
Could not fetch board revision.
Orin board can be detected，but Could not fetch board revision.

root@6.0.8.1-0006-build-linux-sdk:/drive# lsusb
Bus 002 Device 003: ID 0bda:0328 Realtek Semiconductor Corp. USB3.0-CRW
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. 2-Port USB 3.1 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0955:7045 NVIDIA Corp. 
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. 2-Port USB 2.1 Hub
Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse
Bus 001 Device 004: ID 2bdf:028a SN0002 2K USB Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb only contains one NVIDIA device

[SivaRamaKrishnaNV]

@SivaRamaKrishnaNV

Dear @zhangpeixing,
Could you please check

1. aurix and tegra console accessible via minicom?
2. Do you see an additional NVIDIA device in lsusb output on host when target is set in recovery mode?

Dear @zhangpeixing,
The connections looks good.

command to access Aurix/tegra consoles

sudo minicom -D /dev/ttyACM1  #access aurix console
sudo minicom -D /dev/ttyACM0  #access tegra console

lsusb output on host should show just 0955:7045 NVIDIA device when target in normal mode.

Now, to put target in recovery mode, run below commands

#sudo minicom -D /dev/ttyACM1 #run on host to open aurix console
// Below commands should run on aurix console
#tegrarecovery x1 on  #puts in recovery mode
#tegrareset x1 #reset tegra

To, close the Aurix minicom connection, press CTRL+A+Z and then press q to quit the session

Now lsusb on host should show an additional NVIDIA device with ID 0955:7023

Before flashing the device with sdkmanager or docker script, you need to put the board back to normal mode and close all minicom sessions.

Use below commands to put the board in normal mode

#sudo minicom -D /dev/ttyACM1 #run on host to open aurix console
// Below command should run on aurix console
#tegrarecovery x1 off  #puts in recovery mode
#tegrareset x1 #reset tegra

Please confirm if you followed the same and share the logs of each command to debug further.

[zhangpeixing]

Hello, Mr. SivaRamaKrishnaNV.
I did what you told me to do.

sudo minicom -D /dev/ttyACM1  #access aurix console
sudo minicom -D /dev/ttyACM0  #access tegra console

But the terminal shows this and you can’t enter any commands.

So I switched to a different way of doing serial commands via cutecom.
As shown in the figure below.

Closing the cutecom interface, I ran lsusb again and still no NVIDIA device with ID 0955:7023 appeared.At this point, the drive AGX Orin is powered up.The host and AGX Orin did not perform a reboot after the command was issued.

After doing this, it still reports errors on the Flash part.

Sir, what am I supposed to do?

[SivaRamaKrishnaNV]

Dear @zhangpeixing,
May I know if the board is in working condition before you trying to flash? Is tegra accessible?
When trying to connect via minicom, please press ENTER once minicom connection is opened to get access to serial console.

Also, Could you check changing host connection ports and wires and see if lsusb shows an additional NVIDIA device after putting the target in recovery mode.

[zhangpeixing]

Hello,I did the command entry as you said, but it didn’t have any effect.
We checked and the 7023 only works with the Jetson AGX Orin.

My product is DRIVE AGX Orin.

It’s still not compiling past the flashing step.

Is the wiring harness for type-c, etc. to communicate with the host special provided?

[SivaRamaKrishnaNV]

Dear @zhangpeixing,
Can you please confirm if the board is in working condition? Are you able to get access tegra console?
If so, we generally see this issue when host to target connections wires are not good. Did you try changing wires/host ports?

Also, what is the aurix FW version on target?
Please help to clarify above for further debugging.

Note: I am assuming USB Type-A to Micro-USB Cable and USB Type-A to USB Type-C Cable are connected between host and target before flashing.

[zhangpeixing]

We connected minicom and successfully solved the problem, thank you very much for your support and help. Have a nice work.

[SivaRamaKrishnaNV]

Dear @zhangpeixing,
Could you share how the issue is resolved to help others in community

[zhangpeixing]

No problem, sir.

initial step

sudo minicom -D /dev/ttyACM1  #Enter minicom

Press enter on your keyboard to enter the minicom command line and enter the command.

second step

#sudo minicom -D /dev/ttyACM1 #run on host to open aurix console
// Below commands should run on aurix console
#tegrarecovery x1 on  #puts in recovery mode
#tegrareset x1 #reset tegra

Close the terminal after typing the command

The lsusb command confirms that it shows 0955:7045 NVIDIA Corp. If it shows its own device number, the harness is fine.

Third step
Open a new terminal，Enter the following command
The command for this step is to turn off hardware flow control via minicom.

#sudo minicom -D /dev/ttyACM1 #run on host to open aurix console
// Below command should run on aurix console
#tegrarecovery x1 off  #puts in recovery mode
#tegrareset x1 #reset tegra

Finally, install via NVIDIA’s SDK Manger and Flashing will pass.

Thanks again, the official engineers for their help and guidance.