Flashing_log_doubt

DRIVE OS Version: Provide DRIVE OS version. Example: 7.2.5

Issue Description: I am flashing thor HW and get the message update is successful but there is [bootburnTegra-A]: [executeShellCommand(171)] : shell command – timeout 5 /drive/drive-foundation/tools/flashtools/flash/adb -s 2U218620G00000503020 wait-for-device failed

i want to understand whether flashing has happened correctly or not

root@7.2.5.0-0004-linux-nsr:/drive/drive-foundation/tools/flashtools/bootburn# ./bootburn.py -b p3960-10-sw03 -x /dev/ttyACM2 --init_persistent_partitions

********* Starting bootburn/bootburn.py *********
Command Line Arguments :: [‘./bootburn.py’, ‘-b’, ‘p3960-10-sw03’, ‘-x’, ‘/dev/ttyACM2’, ‘–init_persistent_partitions’]
2026-08-27 13:23:40,774 - INFO - Initializing SOC group selector
2026-08-27 13:23:40,775 - INFO - Found SOC group for board p3960-10-sw03
********* Starting t264 bootburn py ********
Bootburn Starting with arguments [‘./bootburn.py’, ‘-b’, ‘p3960-10-sw03’, ‘-x’, ‘/dev/ttyACM2’, ‘–init_persistent_partitions’]
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t264_py/nv-customer-data-schema.json

cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
Check finished successfully
Done parsing command line

[bootburn]: [executeShellCommand(156)] : command = whoami
cwd = /drive/drive-foundation/tools/flashtools/bootburn_t264_py
[bootburn]: [executeShellCommand(163)] : root

[bootburn]: [GetInfoRom(599)] : Read skuinfo from InfoRom…
[bootburn]: Execute command on Aurix serial port
[bootburn]: [ParseInfoRom_Print(673)] : Product Part Number: 670-63960-0010-000
[bootburn]: [getListTargetsInRecovery(3849)] : Bus 001 Device 019: ID 0955:7026 NVIDIA Corp. APX
[bootburn]: [getListTargetsInRecovery(3849)] : Bus 001 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[bootburn]: [GetTegrasAssocWithAurix(514)] : Setting Tegra-A in recovery…
[bootburn]: [GetTegrasAssocWithAurix(518)] : Done
[bootburn]: [getListTargetsInRecovery(3849)] : Bus 001 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[bootburn]: [GetTegrasAssocWithAurix(532)] : retrying board recovery check…
[bootburn]: [getListTargetsInRecovery(3849)] : Bus 001 Device 020: ID 0955:7026 NVIDIA Corp. APX
[bootburn]: [getListTargetsInRecovery(3849)] : Bus 001 Device 014: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
p3960-10-sw03
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t264_py/nv-customer-data-schema.json

cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py
Check finished successfully
Done parsing command line

[bootburnTegra-A]: [executeShellCommand(156)] : command = whoami
cwd = /drive/drive-foundation/tools/flashtools/bootburn_t264_py
[bootburnTegra-A]: [executeShellCommand(163)] : root

[bootburnTegra-A]: [GetTargetECID(838)] : Target BR_CID: 0x8001264178414184080000000A018040

[bootburnTegra-A]: [GetTargetECID(839)] : Target ECID: 0x178414184080000000A018040

[bootburnTegra-A]: [GenAdbSerialNum(605)] : ADB serial number is 2U218620G00000503020
[bootburnTegra-A]: [CheckForDeviceType(941)] : Detected ES production device type

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
n_FlashUfsFirmware is not listed in the Boardconfig

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
n_FlashUfsFirmware is not listed in the Boardconfig
[bootburnTegra-A]: creating and flashing coldboot images
[bootburnTegra-A]: [Boot_Create_Flash_Coldboot(1628)] : Creating & Flashing images
[bootburnTegra-A]: Creating rcm-flash images
[bootburnTegra-A]: [Boot_Create_Flash_Coldboot(1631)] : flashingCFG :: /drive/drive-foundation/tools/flashtools/flashing_kernel/flashing_configs/t264/quickboot_flashing.cfgself.targetConfig.p_OutDirPath :: /drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/Tegra-A-c9052de79f8
[bootburnTegra-A]: [GenerateImage(2047)] : Generating Flashing-RCM Images
[bootburnTegra-A]: [Boot_Create_Flash_Coldboot(1635)] : Generating cold boot flash-images
[bootburnTegra-A]: [initializeChainList(2209)] : selected chains in initializeChainList: [‘A’, ‘B’, ‘C’]
[bootburnTegra-A]: [GenerateImage(2073)] : Generating Flash Images for chain A, this may take a few minutes
[bootburnTegra-A]: [GenerateImage(2073)] : Generating Flash Images for chain B, this may take a few minutes
[bootburnTegra-A]: [GenerateImage(2073)] : Generating Flash Images for chain C, this may take a few minutes
[bootburnTegra-A]: [UpdatePVITinCreateImages(3323)] : Full create, calling UpdatePVITfileNamenMD5 for chain A in UpdatePVITinCreateImages
[bootburnTegra-A]: [UpdatePVITinCreateImages(3323)] : Full create, calling UpdatePVITfileNamenMD5 for chain B in UpdatePVITinCreateImages
[bootburnTegra-A]: [UpdatePVITinCreateImages(3323)] : Full create, calling UpdatePVITfileNamenMD5 for chain C in UpdatePVITinCreateImages
[bootburnTegra-A]: [Boot_Create_Flash_Coldboot(1639)] : Booting Flashing Kernel
[bootburnTegra-A]: [runPlatformDetection(1486)] : runPlatformDetection - rcm-flash
[bootburnTegra-A]: [CheckOptFuses(1320)] : Sku 0xa0

[bootburnTegra-A]: [PreserveTargetSkuInfo(1541)] : Preserving SkuInfo from Target
[bootburnTegra-A]: [waitOnFlashSyncPoint(131)] : Flash sync point not initialized, skipping synchronization
[bootburnTegra-A]: [BootRCM(1404)] : BootRCM - rcm-flash

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
n_FlashUfsFirmware is not listed in the Boardconfig
[bootburnTegra-A]: [getmembctName(1207)] : RAMCODE 4
[bootburnTegra-A]: [getmembctName(1228)] : Selected membct_2 for memcfg
[bootburnTegra-A]: [Boot_Create_Flash_Coldboot(1643)] : Flashing cold boot Images
[bootburnTegra-A]: [FlashImages(3348)] :

[bootburnTegra-A]: [FlashImages(3349)] : Flashing-Images starting

[bootburnTegra-A]: [executeShellCommand(171)] : shell command – timeout 5 /drive/drive-foundation/tools/flashtools/flash/adb -s 2U218620G00000503020 wait-for-device failed
[bootburnTegra-A]: [executeShellCommand(175)] : Output:
[bootburnTegra-A]: [executeShellCommand(177)] : Return code: 124
[bootburnTegra-A]: [getBrBctEntriesFromFileToFlash(3127)] : Found BCT entries in FileToFlash.txt: {‘A_bct’: <bootburn_adb.partitionInformation object at 0x779c38998e60>, ‘B_bct’: <bootburn_adb.partitionInformation object at 0x779c38762840>, ‘C_bct’: <bootburn_adb.partitionInformation object at 0x779c387a93d0>}
[bootburnTegra-A]: [getBrBctEntriesFromFileToFlash(3127)] : Found BCT entries in FileToFlash.txt: {‘A_bct’: <bootburn_adb.partitionInformation object at 0x779c38998e60>, ‘B_bct’: <bootburn_adb.partitionInformation object at 0x779c38762840>, ‘C_bct’: <bootburn_adb.partitionInformation object at 0x779c387a93d0>}

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
n_FlashUfsFirmware is not listed in the Boardconfig
[bootburnTegra-A]: [getBrBctEntriesFromFileToFlash(3127)] : Found BCT entries in FileToFlash.txt: {‘A_bct’: <bootburn_adb.partitionInformation object at 0x779c38998e60>, ‘B_bct’: <bootburn_adb.partitionInformation object at 0x779c38762840>, ‘C_bct’: <bootburn_adb.partitionInformation object at 0x779c387a93d0>}

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
n_FlashUfsFirmware is not listed in the Boardconfig
[bootburnTegra-A]: [getBrBctEntriesFromFileToFlash(3127)] : Found BCT entries in FileToFlash.txt: {‘A_bct’: <bootburn_adb.partitionInformation object at 0x779c38998e60>, ‘B_bct’: <bootburn_adb.partitionInformation object at 0x779c38762840>, ‘C_bct’: <bootburn_adb.partitionInformation object at 0x779c387a93d0>}

In BoardSetFilePathsAndDefaultValues in targetConfig

n_FlashFirmware is set to True
n_FlashUfsFirmware is not listed in the Boardconfig
[bootburnTegra-A]: [FlashImages(3400)] : flashExcept return code - None
[bootburnTegra-A]: [flashFirmware(453)] : in flashFirmware
[bootburnTegra-A]: [flashFirmware(472)] : n_FlashFirmware is set True in board configuration
[bootburnTegra-A]: [flashFirmware(496)] : n_FlashUfsFirmware is False – Skipping Ufs Flashing
[bootburnTegra-A]: [flashFirmware(504)] : Flashing MCU Firmware
Flashing MCU Firmware
mapdictionary :: {‘MT256GAVAT4U31AA’: ‘firmware/micron_fw/ProdSigned_0103_A2001Z_PXA4P418E0H2001Z_Nov11_ec95dee4aa_AUTO_PRN_MT256GAVAT4U31AA_FWVER_67.bin’, ‘G1J38E’: ‘firmware/micron_fw/FFU_EME2LG0364QR071Q_2024JUN21_56e21265d4_PRN_G1J38E_FWVER_5131373052513436.bin’, ‘MT256GBCAV4U31AA’: ‘firmware/micron_fw/DAB0T01CC5QW00GK_2024Jun27_ead4d6a022f_MICRON_PRN_MT256GBCAV4U31AA_FWVER_102.bin’, ‘BGUF4R’: ‘firmware/samsung_fw/fw/SAMSUNG_eMMC_5_1_VINCENT_FETB_MLC_32GB_P63_PRN_BGUF4R_FWVER_000000063.bin’, ‘KLUDG4UHYB-B0EP’: ‘firmware/samsung_fw/fw/SAMSUNG_UFS_3_1_SELENA_V5_TLC_128GB_P53_PRN_KLUDG4UHYB-B0EP_FWVER_14B4.bin’, ‘MCU_FW’: {‘FWupdateScript’: ‘MCU_Flashing.py’, ‘MCUFW’: ‘DRIVE-V7.2.5-P3960-AFW-RH850-U2A16-3.05.03.hex’, ‘tegraUsbPortName’: ‘/dev/ttyACM0’, ‘forceUpdate’: ‘No’}}
3 5 3 0
[bootburnTegra-A]: [vlog(66)] :
***** Fw version in the target MCU FW :: 3.5.3.0****

[bootburnTegra-A]: [vlog(66)] :
starting MCU FW flashing

[bootburnTegra-A]: [vlog(66)] : In UpdateMCUfw
[bootburnTegra-A]: [vlog(66)] : updateMCUfw completed successfully
[bootburnTegra-A]: [vlog(66)] : MCU FIRMWARE UPDATE SUCCESS!!
[bootburn]: Resetting Aurix
[bootburn]: [AurixTegraReset(564)] : Re-setting x1
[bootburn]: [AurixTegraReset(567)] : Done
[bootburn]:
Bootburn completed successfully!

[bootburn]: Bootburn Time 848.4670996665955 seconds

[bootburn]: Dumping file-size files created during flashing
[bootburn]: ===== /drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/Tegra-A-c9052de79f8/flash-images/FileSize_810c5b0000.spi =====
[bootburn]: A_bct 8192
[bootburn]: pt 10752
[bootburn]: bad-page 12288
[bootburn]: A_pt 13824
[bootburn]: A_mb1-bootloader 404896
[bootburn]: A_psc-bl 201952
[bootburn]: A_mb1-bct 47104
[bootburn]: A_mem-bct 311296
[bootburn]: A_mem-dtb 51712
[bootburn]: A_mb2-bootloader 692736
[bootburn]: A_sc7-fw 223744
[bootburn]: A_mb2-rf 279840
[bootburn]: A_psc-fw 456160
[bootburn]: A_sb-package 660064
[bootburn]: A_hpse-package 1069040
[bootburn]: A_bpmp-fw 1413760
[bootburn]: A_bpmp-fw-dtb 20416
[bootburn]: A_bpmp-ist 372992
[bootburn]: A_ist-config 60784
[bootburn]: A_igpu-boot-fw 447744
[bootburn]: B_bct 8192
[bootburn]: B_pt 13824
[bootburn]: B_mb1-bootloader 404896
[bootburn]: B_psc-bl 201952
[bootburn]: B_mb1-bct 47104
[bootburn]: B_mem-bct 311296
[bootburn]: B_mem-dtb 51712
[bootburn]: B_mb2-bootloader 692736
[bootburn]: B_sc7-fw 223744
[bootburn]: B_mb2-rf 279840
[bootburn]: B_psc-fw 456160
[bootburn]: B_sb-package 660064
[bootburn]: B_hpse-package 1069040
[bootburn]: B_bpmp-fw 1413760
[bootburn]: B_bpmp-fw-dtb 20416
[bootburn]: B_bpmp-ist 372992
[bootburn]: B_ist-config 60784
[bootburn]: B_igpu-boot-fw 447744
[bootburn]: C_bct 8192
[bootburn]: C_pt 10752
[bootburn]: C_mb1-bootloader 404896
[bootburn]: C_psc-bl 201952
[bootburn]: C_mb1-bct 47104
[bootburn]: C_mem-bct 311296
[bootburn]: C_mem-dtb 51712
[bootburn]: C_mb2-bootloader 692736
[bootburn]: C_psc-fw 456160
[bootburn]: C_sb-package 660064
[bootburn]: C_hpse-package 1069040
[bootburn]: C_bpmp-fw 1413760
[bootburn]: C_bpmp-fw-dtb 20480
[bootburn]: C_pvit 12944
[bootburn]: C_atf 201264
[bootburn]: C_secure-hv 780064
[bootburn]: C_fsi-fw 579888
[bootburn]: C_kernel 1546048
[bootburn]: C_1_pt 9216
[bootburn]: C_1_kernel-dtb 198480
[bootburn]: C_1_kernel 7511136
[bootburn]: C_1_ramdisk 8804000
[bootburn]: ===== end /drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/Tegra-A-c9052de79f8/flash-images/FileSize_810c5b0000.spi =====
[bootburn]: ===== /drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/Tegra-A-c9052de79f8/flash-images/FileSize_a80b8d0000.ufshci =====
[bootburn]: A_aon-fw 90432
[bootburn]: A_adsp0-fw 384624
[bootburn]: A_adsp1-fw 384608
[bootburn]: A_dce-fw 12682080
[bootburn]: A_pva-fw 2165136
[bootburn]: A_atf 201264
[bootburn]: A_secure-hv 2242112
[bootburn]: A_fsi-fw 6050656
[bootburn]: A_plat-misc-cfg 1056784
[bootburn]: A_rce-fw 631712
[bootburn]: A_rce-fw-dtb 8432
[bootburn]: A_pvit 14896
[bootburn]: A_kernel 5580288
[bootburn]: A_xusb-fw 186432
[bootburn]: A_ist-testimg 3270737920
[bootburn]: A_ist-runtimeinfo 59936
[bootburn]: A_gos0-fs 11697881088
[bootburn]: A_1_pt 9216
[bootburn]: A_1_kernel-dtb 218288
[bootburn]: A_1_kernel 52562432
[bootburn]: A_1_ramdisk 9937408
[bootburn]: A_gos0-rw-overlay 53687091
[bootburn]: A_1_custom_gp1 139264
[bootburn]: A_1_custom_gpt 135168
[bootburn]: gos0-shared-pers 36102144
[bootburn]: gos0-ufs 68182016
[bootburn]: gos0_nvlog 47185920
[bootburn]: pers-ota 268435456
[bootburn]: A_ist-resultdata 81264640
[bootburn]: gos0_nvlog_lun1 47185920
[bootburn]: B_aon-fw 90432
[bootburn]: B_adsp0-fw 384624
[bootburn]: B_adsp1-fw 384608
[bootburn]: B_dce-fw 12682080
[bootburn]: B_pva-fw 2165136
[bootburn]: B_atf 201264
[bootburn]: B_secure-hv 2242112
[bootburn]: B_fsi-fw 6050656
[bootburn]: B_plat-misc-cfg 1056784
[bootburn]: B_rce-fw 631712
[bootburn]: B_rce-fw-dtb 8432
[bootburn]: B_pvit 14896
[bootburn]: B_kernel 5580288
[bootburn]: B_xusb-fw 186432
[bootburn]: B_ist-testimg 3270737920
[bootburn]: B_ist-runtimeinfo 59936
[bootburn]: B_gos0-fs 11697881088
[bootburn]: B_1_pt 9216
[bootburn]: B_1_kernel-dtb 218288
[bootburn]: B_1_kernel 52562432
[bootburn]: B_1_ramdisk 9937408
[bootburn]: B_gos0-rw-overlay 53687091
[bootburn]: B_1_custom_gp1 139264
[bootburn]: B_1_custom_gpt 135168
[bootburn]: B_ist-resultdata 81264640
[bootburn]: ===== end /drive/drive-foundation/tools/flashtools/bootburn_t264_py/__temp_t264/Tegra-A-c9052de79f8/flash-images/FileSize_a80b8d0000.ufshci =====

Dear @nandhini.ravikumar1 ,
Flashing seems successful. Please connect display monitor to accept EULA and config user accounts. This is needed as you have used --init_persistent_partitions flag with bootburn to reset persistent partition. Please see Finalizing the Installation — NVIDIA DriveOS 7.2 Linux Early Access Installation Guide

Connect to tegra console using minicom to confirm the DOS version .

Thanks for your confirmation, I will follow the remaining steps and confirm ,

but I would like to understand whether the following line in log is intended?

timeout is mentioned below is it intended ?

[bootburnTegra-A]: [executeShellCommand(171)] : shell command – timeout 5 /drive/drive-foundation/tools/flashtools/flash/adb -s 2U218620G00000503020 wait-for-device failed

there is a skipping of ufs flash as below is it intended

[bootburnTegra-A]: [FlashImages(3400)] : flashExcept return code - None
[bootburnTegra-A]: [flashFirmware(453)] : in flashFirmware
[bootburnTegra-A]: [flashFirmware(472)] : n_FlashFirmware is set True in board configuration
[bootburnTegra-A]: [flashFirmware(496)] : n_FlashUfsFirmware is False – Skipping Ufs Flashing
[bootburnTegra-A]: [flashFirmware(504)] : Flashing MCU Firmware

Thanks @SivaRamaKrishnaNV :

can you confirm my above query whether it is intended in logs

@SivaRamaKrishnaNV when i try to read console is spawning with the mgbe0 local link fault detected messages . i could read the DOS version as 7.2.5.0-46229577 but how to stop this spawning

Welcome to minicom 2.9 OPTIONS: I18n Port /dev/ttyACM0, 11:54:01 Press CTRL-A Z for help on special keys mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected��sysctl -w kernel.printk=“1 4 1 7” kernel.printk = 1 4 1 7 root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected��sysctl -w kernel.printk=“1 4 1 7” kernel.printk = 1 4 1 7 root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected��echo “mgbe0_0” >��mgbe0: PCS �� ��b��/sy��lock lock SUCCESS 0x0 ��s/bus/platform/drivers/nvidia,mgbe/unbind 2>/dev/null || echo “0000:04:00.0” > /sys/bus/pci/driv��m��ers/��gbe0: Local Link fault detected��nvidia,mgbe/unbind 2>/dev/null -bash: /sys/bus/platform/drivers/nvidia,mgbe/unbind: No such file or directory -bash: /sys/bus/pci/drivers/nvidia,mgbe/unbind: No such file or directory root@tegra-ubuntu:~# root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 �� root@tegra-ubuntu:��m��~# ��gbe0: Local Link fault detected�� root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# root@tegra-ubuntu:~# root@tegra-ubuntu:~# root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.9 | VT102 | Offline | ttyACM0 emobinno@4CE603CSN6:~$ sudo minicom -D /dev/ttyACM0 Welcome to minicom 2.9 OPTIONS: I18n Port /dev/ttyACM0, 11:55:20 Press CTRL-A Z for help on special keys mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected��cat /etc/nvidia/version-ubuntu-rootfs.txt 7.2.5.0-46229577 root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected�� root@tegra-ubuntu:~# ��mgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS 0x0 mgbe0: Local Link fault detected

Yes. flashing is successful. You would see these messages on serial console. Please connect via ssh session to target.

@SivaRamaKrishnaNV :

Thanks for confirmation , I connected via ssh session to target. but i have couple of queries can you help me with it

  1. if i execute sudo minicom -D /dev/ttyACM0 i am getting below messages continously .. i cannot able to use that session itself , may i know how to stop it Welcome to minicom 2.9

    OPTIONS: I18n
    Port /dev/ttyACM0, 16:59:29

    Press CTRL-A Z for help on special keys

    mgbe0: PCS block lock SUCCESS
    0x0
    mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS

    0x0
    mgbe0: Local Link fault detectedmgbe0: PCS block lock SUCCESS
    0x0
    mgbe0: Local Link fault detected��
    tegra-ubuntu login: ��mgbe0: PCS block lock SUCCESS
    0x0

  2. i am using 1gb NIC card and connected via mgbe3_0 interface to take ssh , but interface mgbe2_0 and mgbe1_0 are up state , can i use that interface as well , or what is the difference

  3. external monitor display i connected to the NVDIA drive AGX thor is not powering on by default , is there any pre conditions let me know

@SivaRamaKrishnaNV : Can you please update to my query for my understanding

Dear @nandhini.ravikumar1 ,
Connect internet to mgbe0 interface to to avoid warning related to mgbe0 on serial console.
I would recommend to use ssh session to use target. You can use any mgbe interfaces for ssh connection. Refer to P3960 Network Topology — NVIDIA DriveOS 7.2.5 Linux SDK Early Access Developer Guide for details.
Does this monitor working earlier? Please file a topic for monitor issues. Check if the monitor is detected and share logs in new topic to avoid cluttering of issues in single topic. Thanks

@SivaRamaKrishnaNV : thanks for your clarification , i will post separate topic for monitor issues