After Flshing no IP no Monitor

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
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
2.1.0
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

After i flashed the DriveKit now with 6.0.10 as recommended via the docker container successfully,
log see below.

  1. no Monitor
  2. no IP (Drivekit is direct in the network as other machines and light on Netport DriveKit blinks green)
  3. i read all the other topics, no i could not find in the NVIDIA DRIVE OS Linux SDK Developer Guide
    anything about how to accept the EULA, the links are only ending in landingpages
  4. i cannot access via putty even /dev/ttyACM* (1-3) are available
    ls /dev/ttyACM* = /dev/ttyACM0 /dev/ttyACM1 /dev/ttyACM2 /dev/ttyACM3
  5. lsusb shows the device
  6. when i start sudo minicom -D /dev/ttyACM1 and start the device see log below, for me it looks like
    if he still has 6.0.6 not 6.0.10

how can i fix it

thx

Install/flashlog

sudo docker run -it --privileged --net=host -v /dev/bus/usb:/dev/bus/usb -v /drive_flashing:/drive_flashing nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:latest

[sudo] password for machinexy:

root@6.0.10.0-0009-build-linux-sdk:/drive# ./flash.py /dev/ttyACM1 p3710

2025-04-29 12:29:45 INFO : Initiating pre-flash check
2025-04-29 12:29:45 INFO : Checking Serial Port Connection
2025-04-29 12:29:45 INFO : Serial Port found /dev/ttyACM1
2025-04-29 12:29:45 INFO : Running basic open/close tests on Serial Port Connection
2025-04-29 12:29:45 INFO : Serial Port is open
2025-04-29 12:29:45 INFO : Flushing input and output buffer, discard all content
2025-04-29 12:29:45 INFO : Serial Port is closed
2025-04-29 12:29:45 INFO : Checking available targets
2025-04-29 12:29:45 INFO : Checking Orin board connection
2025-04-29 12:29:45 INFO : Orin board with Device ID – 0955:7045 found.
2025-04-29 12:29:45 INFO : Orin board with Device ID – 0955:7023 found.
2025-04-29 12:29:45 INFO : Orin board device path is /dev/bus/usb/001/014
2025-04-29 12:29:45 INFO : Orin board device path is /dev/bus/usb/001/015
2025-04-29 12:29:45 INFO : Pre-flash check complete
2025-04-29 12:29:45 INFO : Flashing DRIVE OS Docker
2025-04-29 12:40:55 INFO : driveinstaller v2.0
2025-04-29 12:40:55 INFO :
2025-04-29 12:40:55 INFO : SDK/PDK Installer and Flasher
2025-04-29 12:40:55 INFO : Run ./driveinstaller --help for usage information.
2025-04-29 12:40:55 INFO :
2025-04-29 12:40:55 INFO : Initializing board and OS configuration to Autonomous Vehicle p3710 Linux Tegra A
2025-04-29 12:40:55 INFO : Manifest version 2.0
2025-04-29 12:40:55 INFO :
2025-04-29 12:40:55 INFO : BOARD SKU : 940-63710-0010-300
2025-04-29 12:40:55 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-300 sku
2025-04-29 12:40:55 INFO : Applying additional Bind opts
2025-04-29 12:40:55 INFO : Executing bind clean cmd make/bind_partitions -b p3710-10-s05 linux clean
2025-04-29 12:40:55 INFO : Executing bind cmd make/bind_partitions -b p3710-10-s05 linux
2025-04-29 12:40:55 INFO : Bind partitions done!
2025-04-29 12:40:55 INFO : Initializing SDK/PDK flasher for configuration
2025-04-29 12:40:55 INFO : Board: p3710
2025-04-29 12:40:55 INFO : Board type: ES
2025-04-29 12:40:55 INFO : Hypervisor config: linux
2025-04-29 12:40:55 INFO :
2025-04-29 12:40:55 INFO : bypassing inforrom for flashing cmd
2025-04-29 12:40:55 INFO : Pre flash script found! Calling scripts/linux_pre_flash.sh
2025-04-29 12:40:55 INFO : Running flash command: sudo -E /drive/drive-foundation//tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -x /dev/ttyACM1
2025-04-29 12:40:55 INFO : This may take a few minutes
2025-04-29 12:40:55 INFO : Flashing completed successfully
2025-04-29 12:40:55 INFO : See logs at /drive_flashing/log_ije0q4m9fbop17a6dzgyvs2u3hxcrw5n.txt and /drive/driveinstaller/driveinstaller.log
root@6.0.10.0-0009-build-linux-sdk:/drive#

minicom log

*************** NvShell Initialization Start******************
DRIVE-V6.0.6-P3710-AFW-Aurix-StepB-5.07.06
Compilation date: Jan 24 2023, 23:02:05
Enter ‘help’ to see the available commands.

*************** NvShell Initialized *************************
Press ‘Enter’ for NvShell prompt

INFO: SftyMon_IoHwAbs: SAFE_3V3 OutOfRange
MCU_FOH: E2E Initialized
MCU_FOH: Initialization done
INFO: MCU_PLTFPWRMGR: Power-on Triggered
Check for VRS10…
Check for VRS10…
Check for VRS11-1…
Check for VRS11-1…
Check for VRS11-1…
Check for VRS11-1…
Check for VRS11-2…
Check for VRS11-2…
Check for VRS11-2…
Check for VRS11-2…
Check for VRS10…
Check for VRS10…
Check for VRS10…
Check for VRS10…
INFO: NVMCU_ORINPWRCTRL: FUNC_NIRQ continuous monitoring Enabled!
INFO: NvMCU_OrinTMON: toggle check of local and remote sensor successfull
INFO: NvMCU_OrinTMON: Orin Temperature sensor initialized
INFO: MCU_PLTFPWRMGR: Orin TMON enabled …
INFO: BtChn_Cfg: No valid next bootchain loaded
INFO: NVMCU_ORINPWRCTRL: Tegra x1 Boot Chain: A
INFO: SftyMon_tmon: Board Temperature sensor initialized
INFO: MCU_PLTFPWRMGR: Board TMON enabled.
Check for VRS10…
Check for VRS10…
Check for VRS10…
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
INFO: MCU_PltfPwrMgr: Linkup status is not active
INFO: MCU_PltfPwrMgr: 88Q5072 OAK Link Active
INFO:Marvell switch: 0: NW_CFG_BASE
INFO:Marvell switch: Marvell Oak/Spruce configuration completed..
INFO: MCU_PltfPwrMgr: Switch Init
INFO: Marvell Phy: Phy init begin..
MCU_FOH: SOC error pin is asserted
MCU_FOH: Spi Transmit Started
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
INFO: Marvell Phy: Phy init completed..
INFO: MCU_PltfPwrMgr: PHYs Init
INFO: MCU_PltfPwrMgr: StbM Init
ERROR: MCU_ERRHANDLER: McuFoh E2E Frame Error
INFO: MCU_PLTFPWRMGR: Power-up sequence is complete !
INFO: MCU_PLTFPWRMGR: DL Ready drive to HIGH !
Power on the system
ERROR: NvMCU_OrinVMON: VMON XA Notification
INFO : MCU_ISTMGR: IST aborted failed due to wrong sequence Id
ERROR: MCU_ERRHANDLER: OrinVMON : ReportedID - 0x810B ErrorCode - 0xB
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started…
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation agam

2

Dear @alexander102
Tegra console : minicom -D /dev/ttyACM1
Aurix console : minicom -D /dev/ttyACM0

Access tegra console and check etc/nvidia/version-ubuntu-rootfs.txt

Also, please share ethernet connection pictures and ifconfig output

3

thx so much now i have a screen setup users and logged in.
The only open thing he want me to setup the network manager

4

Do you see IP now?

6

Yes i see the IP and i can connect the network, but when i go in the desktop
settings-network i do not see the network admin page only empty page
with info

Oops something has gone wrong. Please contact your software vendor.
NetworkManager needs to be running

cannot install it with sudo apt install network-manager
E: unable to correct problems you have hold broken packages

sudo apt-get install -f shows now broken packages

need to check more, if you have a solution please let me know

many thx

7

Dear @alexander102 ,
Network manager is not used in DRIVE OS. Please see if Network Configuration in NVIDIA Filesystems | NVIDIA Docs helps.

8

ok will check and let you know.

thx so much for your support

9

How can i check which version is installed

10

You can check cat etc/nvidia/version-ubuntu-rootfs.txt on terminal.

11

ok thx, now still we have the problem, that the network screen in settings do not come up, but network settings are important. yes is have internet and ip. only do not see the manual edit screen.

image0
image01920×1080 143 KB

12

This is expected UI for network tab. There is no issue with flashing/setup.
Please see Configuring Interfaces | NVIDIA Docs for configuring interfaces.

15

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.