Can not force recovery through TOPO_Utility program orin development board(p3710)

Please provide the following info (tick the boxes after creating this topic):
Software Version
[*] 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.8.3.10426
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

The orin development board cannot be started by flashing the mcu through common_if_testapp,nv provides TOPO_Utility program to force recovery on mcu, open Infineon Memtool cannot connect to flash program, Memtool Reference configuration doc:Flashing Basics
Error Messages:

Dear @Marin_ma,
What is the objective? If you want to flash the target, could you check using sdkamanager?

Now the mcu serial port and the orin serial port no log output, the usb-c flashing cannot communicate, cannot be flashed through sdkmanager

@Marin_ma did you mean /dev/ttyACMx is not available on your host system? may I know when it worked last time? what caused the problems? Please also create another topic for SDK Manager installation failure with its ~/.nvsdkm logs. Thanks.

Dear @VickNV

  1. /dev/ttyACMx is available on the host, but there is no log output when powered on
  2. Flashing the mcu firmware through the common_if_testapp program on orin causes the mcu to crash
  3. The way to flash the development board is to use the command tools/flashtools/bootburn/bootburn.py -b p3710-10-a01 -B qspi

Dear @Marin_ma,
/dev/ttyACMx is available on the host, but there is no log output when powered on

Are you able to connect to /dev/ttyACMx(both aurix, Tegra console) via minicom? That means, There is no boot log on Tegra A serial console when connected via minicom? Also, Could you share the lsusb output on host?

Dear @SivaRamaKrishnaNV
minicom connect ttyACM* no log output, lsusb output

Please try again after rebooting your host system and devkit system.

Also, I would suggest you follow DRIVE OS 6.0 Installation Guide for NVIDIA Developers and install DRIVE OS 6.0.4 Linux SDK with SDK Manager. It will take care of everything. Thanks.

Dear @VickNV
Rebooting the device doesn’t fix the problem
Do you understand the problem described, the system cannot be flashed and is looking for a way to enter recovery mode

Dear @Marin_ma,
We are wondering why serial console access is not available to Aurix and tegra. Could you disconnect and verify which of /dev/ttyACM* denotes Orin board.
Please share the output of sudo minicom -D /dev/ttyACM* of both Aurix and Tegra. Please press ENTER on the console after openining minicom connection.

@SivaRamaKrishnaNV
let me explain
The minicom is connected to the serial ports of Aurix and Tegra, the orin dev kit powered on no information is printed on the serial ports of Aurix and Tegra.
The reason for this phenomenon is that I used the command common_if_testapp by Tegra to flash Aurix, Aurix failed to flash, restart orin dev kit Aurix and Tegra serial port have no log output, so I am looking for a way to put Aurix into recovery state, and then reflash

No output from the serial ports seems abnormal. Had it ever gotten any output after you flashed DRIVE OS 6.0.4 Linux SDK?
Please reflash DRIVE OS 6.0.4 Linux SDK with SDK Manager. After that, it will take care of firmware updating (also with common_if_testapp) automatically during the first booting. You don’t need to worry about it.

@VickNV
Flashing Drive OS 6.0.4 serial port has output
The USB-C Flashing port cannot be recognized. Can the flashing succeed with sdkmanager?

Why is your devkit uncovered? If it’s Orin devkit, please try to flash DRIVE OS 6.0.4 Linux SDK with sdkmanager. It will be easier.

@Marin_ma did you mean it used to work and the no output from the serial ports issue was caused by flashing Aurix? Why did you try to flash it at the beginning?

@VickNV Because I want to flash mcu through orin

Please let us know why you want to flash the mcu from the very first. Had the devkit ever worked well on your side (before attemping any mcu flashing)?

Initially, devkit was working fine because I wanted to update the mcu software version with the command common_if_testapp, which has now been solved by opening devkit and going into recovery to update the software again