Can not power on,after flash successfully

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: DRIVE AGX Orin Developer Kit (940-63710-0010-200)

SDK Manager Version
1.9.1.10844
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


When I finish my flash successfully, I found that the divece can’t automatically restart.
After that, it can no longer be turned on, and even the fan does not turn after power on. There is no device number after the “lsusb” command. How should I detect if the hardware is damaged? Thank you very much!
driveinstaller.log (1.0 MB)
The attachment is my flashing log, which shows that the flashing has been successful…

Dear @guoju.wang,
Could you attach ~/.nvsdkm/sdkm*.log and ~/.nvsdkm/logs folder?
What is the output of lsusb on host? Could you try check accessing /dev/ttyACM0 and /dev/ttyACM1 ports via minicom?

when I connected type c to my host pc, used entering recovery mode operation,and

lsusb

only can see the serial port device name,like this:

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 13d3:5411 IMC Networks Integrated Camera
Bus 003 Device 003: ID 06cb:00fc Synaptics, Inc. 
Bus 003 Device 002: ID 2c7c:0127 Quectel Wireless Solutions Co., Ltd. Quectel EM05-CE
Bus 003 Device 005: ID 8087:0026 Intel Corp. 
Bus 003 Device 006: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I can find /dev/ttyACM* in /dev,but I cannot access /dev/ttyACM0 and /dev/ttyACM1 ports via minicom, it’s no response.

sdkm.zip (1.6 MB)
logs.zip (853.8 KB)

Dear @guoju.wang,
When you flash board using sdkmanager, please put the board in normal mode.

Before checking lsusb, Did you run tegrarecovery x1 off and tegrareset x1 on aurix console? If so, another NVIDIA device should come in lsusb output.

When try to access Tegra console(/dev/ttyACM0), please keep the board in normal mode(not recovery mode)

Per flashing logs, flashing seems to be successful on 02/08

But it can not power on, that is what I want to know why…

If the flashing seems to be successful on 02/08 ,Why turn on the power switch, but no any response?

Are you still having the issue? Could you provide the logs from the Orin and Aurix consoles after power cycling the system?

Dear @guoju.wang,
I am assuming only one board is connected to your host. Press ENTER to connect to Tegra/aurix console using minicom with sudo minicom -D /dev/ttyACM0 & sudo minicom -D /dev/ttyACM1

Sorry,minicom didn’t work. Press ENTER could not connect any device.

Dear @guoju.wang,
Could you check if the issue is similar to Can't open /dev/ttyACM1 and suggested solution in topic thread works for you?

DRIVE OS has successfully flashed to the system with SDK Manager, so you should be able to access Orin/Aurix. Have you accessed the console on any other system before? If not, please refer to the documentation.

I doubt that whether the hardware is now broken down after I flashed, because when I press the power button, the fan is not work, and there is even no light on on the Drive AGX Orin machine. Now I need to find out that whether my hardware of Drive AGX Orin is already broken down first. The machin have no indication that the machine is success power on after I press the power button.

Thanks for your reply. I have read the documentation you given, and I have use Jetson series before. This is my first time use Drive AGX Orin. But now I can’t even access Orin/Aurix with serial port, the usb to serial port is shown in the device list, but the port can’t be access. I doubt that whether the hardware is now broken down after I flashed, because when I press the power button, the fan is not work, and there is even no light on on the Drive AGX Orin machine. Now I need to find out that whether my hardware of Drive AGX Orin is already broken down first. The machin have no indication that the machine is success power on after I press the power button.

Dear @guoju.wang,

I doubt that whether the hardware is now broken down after I flashed

Flashing should not damage HW. I see flashing is succesful on 02/08 and issue is filed on 02/13. Could you confirm if the issue occured immediately after flashing or occured after few days? Please double check if power supply is correct

How can I confirm hardware is Good ?

Dear @guoju.wang,
Please confirm if you have used the target after flash on 02/08? If so, what did you try on target before this issue occurred.
We will check internally if it is symptom of HW failure and provide guidance accordingly.

Also, could you try check flashing again and see if it works?

Please share below pictures

  1. Target from all directions after poweron
  2. Pictures of host and target connection

That is my all directions picture and connction status.





Dear @guoju.wang,
I hope you have used the rocker switch on the back (near the power cord) to power on/off the board.
Did you try disconnect/reconnect type C cable?
Also, please share dmesg -T log on host after successful flashing.

nvsdkm_20230310.tar (2.6 MB)
SDKM_logs_DRIVE_OS_6.0.5_SDK_Linux_for_DRIVE_AGX_Orin_DevKits_2023-03-10_10-38-27.zip (183.8 KB)





Dear Siva,
Please help to look at this issue. There is no response after I pressed “enter” in ttyACM0 or ttyACM1。
I tried to flash this device with sdkmanager but failed. Please see the logs in attachment.
Thanks!

I noticed some suspicious messages in your logs (appended at the end of this post).

Could you try reproducing the issue on another devkit and confirm if the issue is specific to the current devkit?

In sdkm-2023-03-10-10-36-58.log:

10:56:52.547 - info: exec_command: lsof /dev/ttyACM1 2>/dev/null
10:56:52.898 - info:
10:56:52.898 - error: command error code: 1

In driveinstaller.log:

[2023-03-10 10:56:53,548 root DEBUG inforom_data_handler.py 131 1823614] Opening serial port …
[2023-03-10 10:56:53,549 root DEBUG inforom_data_handler.py 134 1823614] Aurix port /dev/ttyACM1 is open
[2023-03-10 10:56:56,653 root DEBUG inforom_data_handler.py 117 1823614] response on /dev/ttyACM1 =
[2023-03-10 10:56:56,655 root DEBUG inforom_data_handler.py 185 1823614] Inforom data length:
[2023-03-10 10:56:56,655 root DEBUG inforom_data_handler.py 186 1823614] In get_Target_uniqueId()
[2023-03-10 10:56:56,655 root DEBUG inforom_data_handler.py 187 1823614] Inforom data length: 0
[2023-03-10 10:56:56,655 root DEBUG inforom_data_handler.py 99 1823614] sku- {‘p3710’: {}} :
[2023-03-10 10:56:56,655 root DEBUG inforom_data_handler.py 106 1823614] PCB revision : :
[2023-03-10 10:56:56,655 root ERROR pdk_bind.py 121 1823614] Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
[2023-03-10 10:56:56,655 root INFO runner.py 37 1823614] Failed to bind partitions!
[2023-03-10 10:56:56,655 root DEBUG runner.py 39 1823614] Error on line 910
[2023-03-10 10:56:56,655 root DEBUG runner.py 40 1823614] Exception info: Exception Type <class ‘module.errors.FailedToBindPartitionsError’>, Traceback <traceback object at 0x7f721f8ccdc8>
[2023-03-10 10:56:56,656 root INFO runner.py 45 1823614] driveinstaller cannot continue! Check the log file for details: /home/leadtek/.nvsdkm/driveinstaller.log
[2023-03-10 10:56:56,656 root DEBUG runner.py 62 1823614] Cleaning up…
[2023-03-10 10:56:56,656 root DEBUG utilities.py 137 1823614] Deleting temporary directories…
[2023-03-10 10:56:56,656 root DEBUG runner.py 64 1823614] Closing the log file.

Hi Vick, unforunately I don’t have other dev kit at this moment, is there any other method?