Hello,
I wanted to flash (OS update) the TEGRA A system on my PX2 DRIVE, using the SDK manager on a unix host.
Everything was setup correctly:
- TEGRA A up and running
- TEGRA A connected to the internet.
- USB connection with the Host
- no minicom session opened
In the menu where it is possible to select the drive to be flashed I wanted to select the drive A, but by mistake (the two buttons are basically attached), I clicked the “flash” button with TEGRA B still selected.
As a result of the process TEGRA B is still working (it was turned off at the time of the flash), but TEGRA A won’t boot.
How can I fix this ?
the SDK-Mnager log is the attached file (I couldn’t get it properly visualized here)
logA.txt (279 KB)
Dear dario.turchi,
As I understand, you have tried to flash Drive 5.0.13 on Tegra B. After that you are not able to boot into Tegra A.
But, from the log, I could see, flashing of Tegra B is failed. Confirm if you are able to connect to Tegra A using minicom?(For setting minicom refer https://docs.nvidia.com/drive/active/5.0.10.3L/nvvib_docs/index.html#page/NVIDIA%2520DRIVE%2520Linux%2520SDK%2520Development%2520Guide%2FUtilities%2Fminicom.html).
You can use below command for connecting to Tegra A
sudo minicom -D /dev/ttyUSB2
Hello,
Flashing Tegra B has failed because the tegra B was turned off. I wanted to select Tegra A for flashing but by mistake instead of the drop down menu I’ve pressed the “flash” button when A+B or B were selected for flashing (can’t remember).
Anyway it seems like I can’t connect to Tegra A. If i connect to tegra B un ttyUSB6 i can see the booting debug messages and login, nothing on ttyUSB2 for Tegra A
Dear dario.turchi,
Can you connect to aurix and check running following commands and let us know
lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1770:ff00
[b]Bus 001 Device 006: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 005: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC[/b]
Bus 001 Device 004: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sudo minicom -D /dev/ttyUSB1
Welcome to minicom 2.7
OPTIONS: I18n
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB1, 11:53:53
Press CTRL-A Z for help on special keys
shell> enablesafetylogs
Info: Executing cmd: enablesafetylogs, argc: 0, args:
Note: enablesafetylogs should only be used
when Tegra is flashed with safety profile
When -enablesafetylogs is set, the logs for safety demos
and if any safety error logs will start appearing on the console
To get the all the demo logs use -showsafetylogs d
To display the safety error logs use -showsafetylogs e
It will show error logs that appear after the demos are finished
shell> gettegrahealth a
Info: Executing cmd: gettegrahealth, argc: 1, args: a
<Get Tegra Health Successful>
04
shell> gethbpkt a
Info: Executing cmd: gethbpkt, argc: 1, args: a
<Get Tegra Heartbeat Data Successful>
00 00 00 00 84 08 F8 FF
hello:
lsusb:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 17ef:1010 Lenovo
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 050: ID 17ef:100f Lenovo
Bus 003 Device 049: ID 17ef:1010 Lenovo
Bus 003 Device 002: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
Bus 003 Device 056: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 003 Device 055: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 003 Device 054: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 003 Device 053: ID 17ef:600e Lenovo
Bus 003 Device 052: ID 04b3:301b IBM Corp. SK-8815 Keyboard
Bus 003 Device 051: ID 04b3:301a IBM Corp. 2-port low-power hub
Bus 003 Device 006: ID 04ca:7035 Lite-On Technology Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
in minicom, enablesafetylogs
shell> enablesafetylogs
Info: Executing cmd: enablesafetylogs, argc: 0, args:
Note: enablesafetylogs should only be used
when Tegra is flashed with safety profile
When -enablesafetylogs is set, the logs for safety demos
and if any safety error logs will start appearing on the console
To get the all the demo logs use -showsafetylogs d
To display the safety error logs use -showsafetylogs e
It will show error logs that appear after the demos are finished
shell>
gettegrahealth
shell> gettegrahealth a
Info: Executing cmd: gettegrahealth, argc: 1, args: a
<Get Tegra Health Successful>
00
shell>
gethbpkt
shell> gethbpkt a
Info: Executing cmd: gethbpkt, argc: 1, args: a
<Get Tegra Heartbeat Data Successful>
00 00 00 00 00 00 00 00
shell>
Dear dario.turchi,
Could you please file a bug for this topic?
Please share bug ID, we will look into this issue.
Please login to https://developer.nvidia.com/drive with your credentials. Please check MyAccount->MyBugs->Submit a new bug to file bug. Thanks.