Hi
Our Orin Drvkit unable to start normally when we turn the switch on the back of the machine. The fan not work and the led on the front panel not on,also the debug port no output message. We’ve change the power cable and retried many times，still no response.
Please provide the following info (tick the boxes after creating this topic): Software Version
[v] 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
[v] Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
[v] DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
[v] 1.9.2.10884
other
Host Machine Version
[v] 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
Dear @yilin.shen,
May I know if the board was working earlier befoe noticing this issue? If so, when did you notice this issue and what caused this issue? Is the board used in car or office premises?
we used this devkit in office. and we have been using this device until this problem occurs. It is worth noting that we update the firmwere from 6.0.5 to 6.0.6 and system rebooting is OK. When the system prompts to register a username and password. Device crashed suddenly！ after that device cannot reopened anymore
Dear @yilin.shen,
So the DRIVE OS 6.0.6 flashing was successful and when login into DRIVE OS 6.0.6 first time, you notice crash. Please share the ~/.nvsdkm/logs for to confirm flashing the status
Could you check lsusb on host when target is connected to host via debug cable to confirm if detected?
Could you share power connection pictures and power button for confirmation?
Dear @yilin.shen,
Could you share lsusb on host after connecting target. If aurix console is reachable and Tegra is not reachable, please check running tegrareset x1 command on aurix console.
yes，we can see this usbdevice. but aurix console can not input the command, it look like this com port can not receive my keyboard input and can not echo this command to the console.
also, we tried to use “echo “tegrareset x1” > /dev/ttyACMO” cmd ,still no response.
Dear @yilin.shen,
You seems to be opening Tegra console(/dev/ttyACM0)
Could you open serial connection to aurix console via minicom(/dev/ttyACM1) and run tegrareset x1 command on aurix to see if fix the access issue to Tegra A via serial console.
How did you upgrade from 6.0.5 to 6.0.6? With SDK Manager? Could you share the complete logs under ~/.nvsdkm/ as @SivaRamaKrishnaNV requested?
Where did you see the prompts for username/password? Was it on ssh? What did you mean ‘Device crashed suddenly’? Can you elaborate more?
Have you previously been able to access Tegra and Aurix with minicom through /dev/ttyACM0 and /dev/ttyACM1 respectively? What is the current status? Are there no outputs from either device? We would need more information to assist with the issue.
How did you upgrade from 6.0.5 to 6.0.6? With SDK Manager? Could you share the complete logs under ~/.nvsdkm/ as @SivaRamaKrishnaNV requested?
【answer】we did not use sdk manager to upgrade. we used dos command
“./make/bind_partitions -b p3710-10-a03 linux
tools/flashtools/bootburn/bootburn.py -b p3710-10-a03 -B qspi”
to upgrade.
the device
s/n: is 1411522000369
p/n: is 940-63710-0010-c00
we’ve checked our upgrade script relatived directory and can not find the log file.
Where did you see the prompts for username/password?
[answer] After finishing upagrade, we used windows com port communication tool MobaXterm to connect to Orin’s debug port to input the username/password. And after this step，system no response.
We switch off the orin and switch on again , at this time we can not use MobaXerm to connect to orin debug port any more.
Although we did not use the minicom to access, The above operating step is very similar to that.
Have you previously been able to access Tegra and Aurix with minicom through /dev/ttyACM0 and /dev/ttyACM1 respectively? What is the current status? Are there no outputs from either device? We would need more information to assist with the issue.
[answer] Do you mean BEFORE the upgrade action？or AFTER upgrade？ We‘ve replied that we can not access the /dev/ttyACM0 and /dev/ttyACM1. but we can see these ports by using lsusb command.
Please share the history of this devkit before encoutnering this issue, e.g. Where and how has the System been used?What changed between the System working and not working? Does the System have any physical damage?
Please flash with SDK Manager and share the complete logs under ~/.nvsdkm/ for our investigation.
nvsdkm-log2.tar.gz (2.1 MB)
Hi，
I‘ve upload the log which we use sdkmanager to upgrade the system.
we used this device just for isp tuning. office use. Before crash， the debug port always usable. No physical damage has occurred.
The message was found in your driveinstaller.log. Please try again right after power cycling both your host and target systems.
[2023-05-17 15:33:31,952 root ERROR pdk_bind.py 121 102780] Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
nvsdkm-log03.tar.gz (2.2 MB)
Yes, We have closed all serial ports and tried many times. It always reports the same error. It seems that this machine is not powered on. when we press the power button, the fan and indicator light are unresponsive.
I still found the same message in your latest logs.
Some of the following questions I probably already asked you previously but please provide the information again. I’ll discuss your issue with our team based on this information. Thanks.
Part Number?
Serial Number?
Sales Order Number?
What software is running on the System?
Where and how has the System been used?
What changed between the system working and not working?
Does the System have any physical damage? Can you hear noise when moving the unit, any loose component inside?
4.What software is running on the System?
Ubuntu Linux 20.04 with DRIVE OS 6.0.5
5.Where and how has the System been used?
We use this system to debug nvsipl camera drivers and tunning
6.What changed between the system working and not working?
we update the firmwere from 6.0.5 to 6.0.6, and system rebooting is OK. When the system prompts to register a username and password. Device crashed suddenly！ After that device cannot reopened anymore.
7.Does the System have any physical damage? Can you hear noise when moving the unit, any loose component inside?
There is no physical damage to the machine. And No abnormal noise was heard when shaking the machine.
This image looks the LEFT USB Type-C port on the Developer System isn’t connected to your host system.
May I know if it’s connected when you tried to flash DRIVE OS?
We confirmed that LEFT USB type C port is connected to PC when we flashing.
This picture is just we want to show that when we switch on the devkit
and connected the debug port to PC,but PC can not connect to this debug COM port by console. At that time，we just do the POWER ON test.
We would like to make sure this isn’t a software issue.
Please make sure you have experience in using minicom to access Tegra and Aurix (through /dev/ttyACM0 and /dev/ttyACM1) and provide the commands and their outputs on the problematic unit.
