Fail to flash tegra A and B when using sdkmanager

Hi,

I am working with Drive PX2 autochauffer. And I am trying to flash tegra A and B by newest SDKM.

I followed the steps from 1 to 4. In the last step 4, the SDKM says that flashing failed. And I have no idea what happened.

Details of terminal tab:

10:55:21 INFO : null
10:55:24 INFO : GNU Toolchains : download ‘GNU Toolchains’ success
10:55:24 INFO : DRIVE Foundation Packages : download ‘DRIVE Foundation Packages’ success
10:55:24 INFO : DRIVE Foundation OSS Packages : download ‘DRIVE Foundation OSS Packages’ success
10:55:24 INFO : OSS and NV packages : download ‘OSS and NV packages’ success
10:55:24 INFO : DPX Packages : download ‘DPX Packages’ success
10:55:24 INFO : Aurix Updater : download ‘Aurix Updater’ success
10:55:24 INFO : CUDA on Target : download ‘CUDA on Target’ success
10:55:24 INFO : TensorRT (with cuDNN 7.1) on Target : download ‘TensorRT (with cuDNN 7.1) on Target’ success
10:55:24 INFO : CUDA on Host : download ‘CUDA on Host’ success
10:55:24 INFO : DPX Patch : download ‘DPX Patch’ success
10:55:24 INFO : TensorRT (with cuDNN 7.1) on Host : download ‘TensorRT (with cuDNN 7.1) on Host’ success
10:55:24 INFO : DriveWorks on Host : download ‘DriveWorks on Host’ success
10:55:24 INFO : DriveWorks Samples : download ‘DriveWorks Samples’ success
10:55:24 INFO : Tegra Graphics Debugger : download ‘Tegra Graphics Debugger’ success
10:55:24 INFO : DevTools Documentation : download ‘DevTools Documentation’ success
10:55:24 INFO : DriveWorks Cross Compilation : download ‘DriveWorks Cross Compilation’ success
10:55:24 INFO : PerfWorks SDK : download ‘PerfWorks SDK’ success
10:55:24 INFO : DriveWorks on Target : download ‘DriveWorks on Target’ success
10:55:24 INFO : NVIDIA Nsight Systems : download ‘NVIDIA Nsight Systems’ success
10:55:24 INFO : P2379 specific package : download ‘P2379 specific package’ success
10:55:24 INFO : install ‘GNU Toolchains’ success
10:55:24 INFO : install ‘DRIVE Foundation Packages’ success
10:55:24 INFO : install ‘DRIVE Foundation OSS Packages’ success
10:55:24 INFO : install ‘OSS and NV packages’ success
10:55:24 INFO : install ‘DPX Packages’ success
10:55:24 INFO : install ‘Aurix Updater’ success
10:55:24 INFO : install ‘CUDA on Target’ success
10:55:24 INFO : install ‘TensorRT (with cuDNN 7.1) on Target’ success
10:55:24 INFO : install ‘CUDA on Host’ success
10:55:24 INFO : install ‘DPX Patch’ success
10:55:24 INFO : install ‘TensorRT (with cuDNN 7.1) on Host’ success
10:55:24 INFO : install ‘DriveWorks on Host’ success
10:55:24 INFO : install ‘DriveWorks Samples’ success
10:55:24 INFO : install ‘Tegra Graphics Debugger’ success
10:55:24 INFO : install ‘DevTools Documentation’ success
10:55:24 INFO : install ‘DriveWorks Cross Compilation’ success
10:55:24 INFO : install ‘PerfWorks SDK’ success
10:55:24 INFO : install ‘DriveWorks on Target’ success
10:55:24 INFO : install ‘NVIDIA Nsight Systems’ success
10:55:24 INFO : install ‘P2379 specific package’ success
10:55:45 INFO : Start to install ‘Flash Dual Tegras in Parallel’
10:55:45 DEBUG : Flash Dual Tegras in Parallel : running command < cd ‘/media/ed/Data/nvidia/hw_image/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS_P2379’ ; ‘/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter’ -a=‘install’ -c=‘eyJpZCI6Ik5WX0ZMQVNIX0RVQUxfVEVHUkFTX0lOX1BBUkFMTEVMX0NPTVAiLCJuYW1lIjoiRmxhc2ggRHVhbCBUZWdyYXMgaW4gUGFyYWxsZWwiLCJkZXNjcmlwdGlvbiI6IkZsYXNoIEJvdGggVGVncmEgQSBhbmQgVGVncmEgQiBpbiBwYXJhbGxlbC4iLCJpc1Zpc2libGUiOnRydWUsImxpY2Vuc2VJZCI6Ik5WX0RSSVZFX1NMQV9PQ1QyMDE3IiwiaXNEZXRlY3RhYmxlSW5zdGFsbCI6ZmFsc2UsImlzSW5zdGFsbFBhdGhDdXN0b21pemFibGUiOnRydWUsInRpbWVvdXRTZWNvbmRzIjozNjAwLCJ2ZXJzaW9uIjoiNS4wLjEwLjMiLCJvcGVyYXRpbmdTeXN0ZW1zIjpbInVidW50dTE0MDQiLCJ1YnVudHUxNjA0Il0sImluc3RhbGxTaXplTUIiOjAsImRvd25sb2FkRmlsZXMiOltdLCJ0YXJnZXRJZHMiOlsiUFgyX0FVVE9DSEFVRkZFVVIiXSwiZGVwZW5kZW5jaWVzIjpbeyJpZCI6Ik5WX0dOVV9UT09MQ0hBSU5TX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9HTlVfVE9PTENIQUlOU19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RSSVZFX0ZPVU5EQVRJT05fUEFDS0FHRVNfU0RLX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9EUklWRV9GT1VOREFUSU9OX1BBQ0tBR0VTX1NES19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RSSVZFX0ZPVU5EQVRJT05fT1NTX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9EUklWRV9GT1VOREFUSU9OX09TU19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX09TU19BTkRfTlZfUEFDS0FHRVNfU0RLX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9PU1NfQU5EX05WX1BBQ0tBR0VTX1NES19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RQWF9QQUNLQUdFU19DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMC4zIiwiX2lkIjoiTlZfRFBYX1BBQ0tBR0VTX0NPTVBAUFgyX0FVVE9DSEFVRkZFVVIifSx7ImlkIjoiTlZfQVVSSVhfVVBEQVRFUl9DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMC4zIiwiX2lkIjoiTlZfQVVSSVhfVVBEQVRFUl9DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RQWF9QQVRDSF9DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMC4zIiwiX2lkIjoiTlZfRFBYX1BBVENIX0NPTVBAUFgyX0FVVE9DSEFVRkZFVVIifV0sImV4dGVybmFsX2RlcGVuZGVuY2llcyI6W10sInRhcmdldElEIjoiUFgyX0FVVE9DSEFVRkZFVVIiLCJfaWQiOiJOVl9GTEFTSF9EVUFMX1RFR1JBU19JTl9QQVJBTExFTF9DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIiwicGFyZW50SUQiOiJOVl9EUklWRV9GTEFTSF9UQVJHRVRfR1JPVVAiLCJfcGFyZW50SUQiOiJOVl9EUklWRV9GTEFTSF9UQVJHRVRfR1JPVVBAUFgyX0FVVE9DSEFVRkZFVVIiLCJjb21wVHlwZSI6ImZsYXNoIiwiaW5zdGFsbFN0YXR1cyI6Im5vbmUiLCJhY3Rpb24iOjEsImJ1bmRsZVRpdGxlIjoiRFJJVkVfT1NfNS4wLjEwLjNfU0RLX3dpdGhfRHJpdmVXb3Jrc19MaW51eF9PUyIsImluc3RhbGxQYXRoIjoiL21lZGlhL2VkL0RhdGEvbnZpZGlhL2h3X2ltYWdlL0RSSVZFX09TXzUuMC4xMC4zX1NES193aXRoX0RyaXZlV29ya3NfTGludXhfT1NfUDIzNzkiLCJpbnN0YWxsUm9vdCI6Ii9tZWRpYS9lZC9EYXRhL252aWRpYS9od19pbWFnZSIsImJvYXJkSUQiOiJQMjM3OSIsImlzRHJ5UnVuIjpmYWxzZX0=’ -i=‘NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP’ -v=‘5.0.10.3’ -l=’/media/ed/Data/nvidia/hw_image/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS_P2379’ -L=’/home/ed/.nvsdkm/logs/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS’ -p=‘4862’ -t=‘PX2_AUTOCHAUFFEUR’ -e=‘undefined’ -b=‘NV_DRIVE_LINUX_BUNDLE’ -x=‘SDK’ >
10:55:45 INFO : Flash Dual Tegras in Parallel : Using LegacyInstaller to install NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP
10:55:45 INFO : Flash Dual Tegras in Parallel : exec_command: awk ‘/^\s*deb.*archive.ubuntu.com/{print $2}’ /etc/apt/sources.list | head -1 | tr -d ‘\n’
10:55:45 INFO : Flash Dual Tegras in Parallel : ed
10:55:45 INFO : Flash Dual Tegras in Parallel : exec_command: df -l -B1 -T --total | tail -1 | awk ‘{ printf $5 }’
10:55:45 INFO : Flash Dual Tegras in Parallel : exec_command: sudo rm -f /var/lock/LCK…ttyUSB1
10:55:45 INFO : Flash Dual Tegras in Parallel : [host] [sudo] password for ed:
10:55:45 INFO : Flash Dual Tegras in Parallel :
10:55:45 INFO : Flash Dual Tegras in Parallel : exec_command: sudo rm -f /var/lock/LCK…bootburn_seq
10:55:45 INFO : Flash Dual Tegras in Parallel : exec_command: sudo rm -f /var/lock/LCK…bootburn
10:55:45 INFO : Flash Dual Tegras in Parallel : exec_command: ./pdk_flash.sh -b p2379c01-t186
10:55:45 INFO : Flash Dual Tegras in Parallel :
10:55:45 INFO : Flash Dual Tegras in Parallel : p2379c01-t186 will be flashed
10:55:45 INFO : Flash Dual Tegras in Parallel :
10:55:45 INFO : Flash Dual Tegras in Parallel : linux will be flashed
10:55:45 INFO : Flash Dual Tegras in Parallel : Make sure only one target is connected to USB
10:55:45 INFO : Flash Dual Tegras in Parallel : and Aurix port is not open in minicom or another terminal
10:55:45 INFO : Flash Dual Tegras in Parallel :
10:55:45 INFO : Flash Dual Tegras in Parallel : ERROR: drive-t186ref-foundation doesn’t exist !
10:55:45 INFO : Flash Dual Tegras in Parallel : exit status 200
10:55:45 ERROR : Flash Dual Tegras in Parallel : Failed to flash device: please check /home/ed/.nvsdkm/logs/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS/flash_2379_parallel.log for more details.
10:55:45 INFO : Flash Dual Tegras in Parallel :
10:55:45 INFO : Flash Dual Tegras in Parallel : InstallUtil returns: exit status 1
10:55:45 ERROR : Flash Dual Tegras in Parallel : command terminated with error
10:55:45 ERROR : install ‘Flash Dual Tegras in Parallel’ failure, command < cd ‘/media/ed/Data/nvidia/hw_image/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS_P2379’ ; ‘/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter’ -a=‘install’ -c=‘eyJpZCI6Ik5WX0ZMQVNIX0RVQUxfVEVHUkFTX0lOX1BBUkFMTEVMX0NPTVAiLCJuYW1lIjoiRmxhc2ggRHVhbCBUZWdyYXMgaW4gUGFyYWxsZWwiLCJkZXNjcmlwdGlvbiI6IkZsYXNoIEJvdGggVGVncmEgQSBhbmQgVGVncmEgQiBpbiBwYXJhbGxlbC4iLCJpc1Zpc2libGUiOnRydWUsImxpY2Vuc2VJZCI6Ik5WX0RSSVZFX1NMQV9PQ1QyMDE3IiwiaXNEZXRlY3RhYmxlSW5zdGFsbCI6ZmFsc2UsImlzSW5zdGFsbFBhdGhDdXN0b21pemFibGUiOnRydWUsInRpbWVvdXRTZWNvbmRzIjozNjAwLCJ2ZXJzaW9uIjoiNS4wLjEwLjMiLCJvcGVyYXRpbmdTeXN0ZW1zIjpbInVidW50dTE0MDQiLCJ1YnVudHUxNjA0Il0sImluc3RhbGxTaXplTUIiOjAsImRvd25sb2FkRmlsZXMiOltdLCJ0YXJnZXRJZHMiOlsiUFgyX0FVVE9DSEFVRkZFVVIiXSwiZGVwZW5kZW5jaWVzIjpbeyJpZCI6Ik5WX0dOVV9UT09MQ0hBSU5TX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9HTlVfVE9PTENIQUlOU19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RSSVZFX0ZPVU5EQVRJT05fUEFDS0FHRVNfU0RLX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9EUklWRV9GT1VOREFUSU9OX1BBQ0tBR0VTX1NES19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RSSVZFX0ZPVU5EQVRJT05fT1NTX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9EUklWRV9GT1VOREFUSU9OX09TU19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX09TU19BTkRfTlZfUEFDS0FHRVNfU0RLX0NPTVAiLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiNS4wLjEwLjMiLCJfaWQiOiJOVl9PU1NfQU5EX05WX1BBQ0tBR0VTX1NES19DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RQWF9QQUNLQUdFU19DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMC4zIiwiX2lkIjoiTlZfRFBYX1BBQ0tBR0VTX0NPTVBAUFgyX0FVVE9DSEFVRkZFVVIifSx7ImlkIjoiTlZfQVVSSVhfVVBEQVRFUl9DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMC4zIiwiX2lkIjoiTlZfQVVSSVhfVVBEQVRFUl9DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIn0seyJpZCI6Ik5WX0RQWF9QQVRDSF9DT01QIiwib3BlcmF0b3IiOiI9PSIsInZlciI6IjUuMC4xMC4zIiwiX2lkIjoiTlZfRFBYX1BBVENIX0NPTVBAUFgyX0FVVE9DSEFVRkZFVVIifV0sImV4dGVybmFsX2RlcGVuZGVuY2llcyI6W10sInRhcmdldElEIjoiUFgyX0FVVE9DSEFVRkZFVVIiLCJfaWQiOiJOVl9GTEFTSF9EVUFMX1RFR1JBU19JTl9QQVJBTExFTF9DT01QQFBYMl9BVVRPQ0hBVUZGRVVSIiwicGFyZW50SUQiOiJOVl9EUklWRV9GTEFTSF9UQVJHRVRfR1JPVVAiLCJfcGFyZW50SUQiOiJOVl9EUklWRV9GTEFTSF9UQVJHRVRfR1JPVVBAUFgyX0FVVE9DSEFVRkZFVVIiLCJjb21wVHlwZSI6ImZsYXNoIiwiaW5zdGFsbFN0YXR1cyI6Im5vbmUiLCJhY3Rpb24iOjEsImJ1bmRsZVRpdGxlIjoiRFJJVkVfT1NfNS4wLjEwLjNfU0RLX3dpdGhfRHJpdmVXb3Jrc19MaW51eF9PUyIsImluc3RhbGxQYXRoIjoiL21lZGlhL2VkL0RhdGEvbnZpZGlhL2h3X2ltYWdlL0RSSVZFX09TXzUuMC4xMC4zX1NES193aXRoX0RyaXZlV29ya3NfTGludXhfT1NfUDIzNzkiLCJpbnN0YWxsUm9vdCI6Ii9tZWRpYS9lZC9EYXRhL252aWRpYS9od19pbWFnZSIsImJvYXJkSUQiOiJQMjM3OSIsImlzRHJ5UnVuIjpmYWxzZX0=’ -i=‘NV_FLASH_DUAL_TEGRAS_IN_PARALLEL_COMP’ -v=‘5.0.10.3’ -l=’/media/ed/Data/nvidia/hw_image/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS_P2379’ -L=’/home/ed/.nvsdkm/logs/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS’ -p=‘4862’ -t=‘PX2_AUTOCHAUFFEUR’ -e=‘undefined’ -b=‘NV_DRIVE_LINUX_BUNDLE’ -x=‘SDK’ > terminated with error
10:55:45 INFO : install ‘Flash Tegra A’ Skipped
10:55:45 INFO : install ‘Flash Tegra B’ Skipped
10:55:46 INFO : All done!

SDKM_logs_DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_for_DRIVE_PX_2_AutoChauffeur_2019-08-15_10-36-39.zip (457 KB)

Hi 944637442,

From the log, it seems the following directory is missing:
/media/ed/Data/nvidia/hw_image/DRIVE_OS_5.0.10.3_SDK_with_DriveWorks_Linux_OS_P2379/drive-t186ref-foundation
This usually happens if the directory is manually deleted. However, it still has a record in SDK Manager database, and further installation will only install components that do not exist in the database.

To fix the problem, can you please try following steps?

  1. Fully uninstall 5.0.10.3 with SDK Manager.
  2. Re-install 5.0.10.3 then flash device.

Hi Edward,

Thanks for your help! I follow those steps and flash successfully.

After Drive PX2 reboots, the pop-up window says that “First boot script processing complete.” But the Next button is still inactivated.

What should I do now?

Dear 944637442,
It is required to connect board to internet when you flash and boot first time. It downloads some packages to finish installation on board. Could you confirm that?

Hi Siva Rama Krishna,
I have connected the device to the network using an ethernet cable and booted again. But the Next button is still inactivated.
How can I confirm whether the device is connnected to the network?

You can connect tegra A/B via minicom and check ping some url to know if internet is working.

Just to confirm, If you have not connected both board and host to internet while flashing the device, could you please check re-install using SDK manager and make sure you have no issues with internet.

Dear Siva,

I cannot connect tegra A/B via minicom.
After executing ‘sudo minicom -w -D /dev/ttyUSB2’, the terminal doesn’t prompt a login dialogue.

The terminal displays the following information:
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB2, 10:22:18

Press CTRL-A Z for help on special keys

Should I re-install using SDK Manager?

dear 944637442
Did you press ENTER after launching minicom?

Dear Siva,
Yes, I have pressed ENTER after launching minicom. But nothing happened.
I re-install the minicom and try again, and I get the same result.

Dear 944637442,

Did you setup minicom configuration for DrivePX2?

https://docs.nvidia.com/drive/active/5.0.10.3L/nvvib_docs/index.html#page/NVIDIA%20DRIVE%20Linux%20SDK%20Development%20Guide%2FUtilities%2Fuart_dpx.html

Dear Steve,
Yes, I have settup minicom configuration before connecting DrivePX2 and I still cannot connect tegra A.
I have re-flashed tegra A again, but it didn’t work.

Dear 944637442,

Can you access Aurix terminal with minicom tool(sudo minicom -D /dev/ttyUSB1)?

Dear Steve,

I can access Aurix terminal with minicom tool. But I cannot connect tegra A or B.
Could you please tell me what to do next?

Dear 944637442,

Could you please check if you can get the following information through status and help commands on Aurix terminal?

shell> <b>status</b>
Info: Executing cmd: status, argc: 0, args: 
Alive       : 45:29:56
CPU load     Core 0: 9%
CPU load max Core 0: 12%
CPU load     Core 1: 0%
CPU load max Core 1: 0%
CPU load     Core 2: 0%
CPU load max Core 2: 0%

Hardware information: 
PMU-chip: B-Step
SCU_CHIPID: 0x4B459051
SystemUpInit-Time[ms]: 49
FPD-switch = 1 (Tegra-B)

IP-address (Tegra-A): 10.42.0.28
IP-address (Tegra-B): 10.42.0.29
IP-address   (AURIX): 10.42.0.146

MAC-address (Tegra-A): 0x000000044B706DCD
MAC-address (Tegra-B): 0x000000044B706DCE
MAC-address   (AURIX): 0x000000044B706DCF
MAC-address    (FPGA): 0x0000000000000000

ADC0_HRNS2: 0x0919
ADC1_HRNS2: 0x091A
Command Executed

shell> <b>help</b>
Info: Executing cmd: help, argc: 0, args: 
DEBUG: command_help()
aurixreset                             : Power cycle board including Aurix
campower [a|b|c] [on|off|z]            : Turn on/off/set to high impedance Group A/B/C Cae
cancyclic [a|b|c|d|e|f] [on|off]       : Enable/disable cyclic CAN frames from can contro]
canfdtx [a|b|c|d|e|f] [on|off]         : Switches the transmit path for CAN FD TX PDUs on)
canrxlog [on|off]                      : Turn on/off the log of all received CAN messages.
cansend f 0x75 0xffff0000 0xaaaa5555   : Send data = 0xffff0000aaaa5555 with id 0x75 fromf
cansetbr [a|b|c|d|e|f] [125|250|500|1000] : Switch baudrate of requested CAN channel to se
canstress [on|off]                     : Turn on/off the measurements and can-tx-results t
date [0x12345678]                      : Set date = 0x12345678 on Aurix in seconds(Unix s)
debugled [on|off]                      : Turn on or off the debug led on Aurix
debugvar [0x1f4]                       : Sets a debug variable to 500
ethrxlog [on|off]                      : Turn on/off the log of received Ethernet message.
fpdlsource [a|b]                       : Select Tegra A/B as FPDL source
getportvlan [port]                     : Gets the bitmask of the port based VLAN at the M]
gmslcable [coax|diff]                  : Select GMSL cable coax or differential
gmslsource [a|b]                       : Select Tegra A/B as GMSL source
gptpon                                 : Switch gPTP on (for AURIX)
gptpoff                                : Switch gPTP off (for AURIX, this is the default )
help                                   : Shows all available commands supported
i2cinit [0|1]                          : Initializes the I2C-module 0 or 1
i2cread c d a n                        : Reads 'n' bytes from device 'd' at address 'a' o)
i2cscan [0|1]                          : Scan all connected I2C devices at I2C module 0 o1
i2cwrite c d a n b0 b1 ...             : Writes 'n' bytes to device 'd' at address 'a' , )
inforom [dump][help][readbyid][readbyname] : dump inforom, help, readbyid (id in hex), re 
mdiord [layer] [reg]                   : gets the register [reg] value of [layer] at the e
mdiowr [layer] [reg] [val]             : sets the register [reg] value of [layer] at the e
pgoodstatus                            : Show Power Good Status
ping 10.0.0.1                          : Ping to IP Address e.g. 10.0.0.1 from Aurix.
power [a|b|ab] [on|off]                : Power on/off the Tegra A/B/Both system EXCLUDINGx
readNvRam                              : Read NvRam content 
regrd [0xf003c100]                     : Read aurix register 0xf003c100
regwr r v n                            : Writes one 'n' (1..4) bytes-value 'v' to aurix r 
setdio [0|1|2|3] [on|off]              : Set DIO pin on Aurix '0=GPIO_RELAY0_HRNS2|1=GPIO 
setfanspeed [a|b] [on|off]             : Select Tegra A/B to de-/activate the fan speed cl
setip a 10.42.0.33                     : Set new ip address for a(Aurix), ta(Tegra A) and3
setportvlan [port] [mask]              : Sets the [mask] of the port based VLAN at the Ma]
status                                 : Display the Aurix internal clock
tegraqsinit [a|b]                      : Initialize qspi module connected to Tegra A and B
tegrarecovery [ |a|b] [ |on|off]       : Set or clear Tegra A/B force recovery mode
tegrareset [ |a|b] [ |h]               : Toggle reset Tegra A/B. Default is 'a'. If h is .
tegrawr [a|b] 1 0xaaaa                 : Write with value 0xaaaa/read 1 16-bit word to/frB
version                                : Shows the SW version
enablesafetylogs                       : Enable safety logs on the console. To get full sd
showsafetylogs [d|e]                   : Display past safety logs d - shows logs safety ds
getswversion[a|b]                      : Send command for Get SW Version
getstartupstatus[a|b]                  : Send command for Get Startup Status
gettegrahealth[a|b]                    : Get Tegra Health
gethbstatus[a|b]                       : Get Tegra Heartbeat Status
gethbpkt[a|b]                           : Get Heartbeat Packet
Command Executed

Then could you please try reset tegraA with tegrareset a command on Aurix terminal and try to re-connect TegraA via minicom?

<b>shell> tegrareset a </b>  
Info: Executing cmd: tegrareset, argc: 1, args: a 
Command Executed
shell>

Dear Steve,

I reset tegraA on Aurix terminal as you said and try to re-connect tegraA with minicom.
After excuting ‘sudo minicom -D /dev/ttyUSB2’, the terminal displays the following information:

     Starting Cleanup of Temporary Directories...

[ OK ] Started Cleanup of Temporary Directories.
[ *** ] A start job is running for Setup Wizard (15min 21s / no limit)[ 925.7k
[ 925.865347] tegradc 15220000.nvdisplay: can’t set parent_clk_safe for sor->rk
[*** ] A start job is running for Setup Wizard (15min 21s / no limit)[ 926.1k
[ **] A start job is running for Setup Wizard (3h 12min 58s / no limit)[1158k
[11582.573673] tegradc 15220000.nvdisplay: can’t set parent_clk_safe for sor->rk
[ *] A start job is running for Setup Wizard (3h 12min 59s / no limit)[1158k
[ **] A start job is running for Setup Wizard (5h 46min 23s / no limit)[2078k
[20786.780995] tegradc 15220000.nvdisplay: can’t set parent_clk_safe for sor->rk
[ ] A start job is running for Setup Wizard (5h 46min 23s / no limit)[2078k
[
] A start job is running for Setup Wizard (6h 7min 47s / no limit)[22070k
[22070.706410] tegradc 15220000.nvdisplay: can’t set parent_clk_safe for sor->rk
[
] A start job is running for Setup Wizard (6h 7min 47s / no limit)

The start job ran for more than 6 hours, is this normal?
Should I continue to wait for it?

Dear 944637442,

If just look at the log, it does not seem to bring the information of the monitor properly.
Is the screen output to the monitor when the monitor is connected?

If not, could you please re-flash the board after connect Internet and a monitor to DrivePX?

Dear Steve,

I re-flash the board after connect Internet and a monitor, but I have the same problem again after re-booting.

The pop-up window says that “First boot script processing complete.” But the Next button is still inactivated.

Here is the picture of screen.
20190906100630.jpg

20190906100630.jpg

Did you solve the problem. I am having the same issue

Hi 944637442,

Is it still an issue at your side?

If yes, could you please remove the installed 5.0.10.3 release by SDKM, clean up the release folder under install location(~/nvidia/nvidia_sdk by default) and reinstall the release?

Current NV OSS and packages doesn’t support to install on existing directory.