Unable to boot Ubuntu

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

My DRIVE AGX can’t boot Ubuntu, and it shows nothing on display via HDMI.

I’d like to ask two questions.

  1. How can I debug this situation?
  2. Are there any documentations of the shell on AURIX?

l3_getsafetystatus

shell> l3_getsafetystatus
Info: Executing cmd: l3_getsafetystatus, argc: 0, args: 

Platform FuSa State: UNSAFE STATE
Platform Startup Status: STARTUP FAIL
Tegra A FuSa State: INIT STATE
Tegra B FuSa State: SAFE STATE
Tegra A nSAFE State: nSAFE ASSERTED
Tegra B nSAFE State: nSAFE DEASSERTED
Platform Error Log Count: 1

version

shell> version
Info: Executing cmd: version, argc: 0, args: 
SW Version: DRIVE-V5.0.10-E3550-EB-Aurix-With3LSS-ForHyperion-3.00.07
Compilation date: Jul 20 2018, 09:08:33
Command Executed

Port /dev/ttyUSB2 (Pushing Enter shows Data abort)

...
Running System clock period config
Current clock period: 1000 usec 
Applying clock period as: 10000 usec 
��Waiting forever until network is up...
��Enabling WDT driver...
��platform_guest_warm_boot: guest warm reboot
����[    2.505400] CPU4: Booted secondary processor [4e0f0040]
[    2.505852] CPU4: CPU online now.
[    2.556982] CPU5: Booted secondary processor [4e0f0040]
[    2.558064] CPU5: CPU online now.
[    2.611417] CPU6: Booted secondary processor [4e0f0040]
[    2.615881] CPU6: CPU online now.
��nvsafety starting
��[    2.670498] CPU7: Booted secondary processor [4e0f0040]
[    2.673149] CPU7: CPU online now.
[    2.680508] Brought up 8 CPUs
[    2.682699] SMP: Total of 8 processors activated.
[    2.686082] CPU features: detected feature: User Access Override
��Starting nvrm
Starting dtree-nvhvnet
��nvsafety started
starting NvGuard_Layer_1
��# ��# No error
��[    2.912297] CPU features: detected feature: 32-bit EL0 Support
��------------------------------------------------------------------------------
Exception: Data abort
DFAR: 0x03c10000, DFSR: 0x00001008
PC: 0x0c480804
LR: 0x0c4837e7, SP:  0x0c49bcd8, PSR: 0x4000003f
R0: 0x0c48fbc4, R1:  0x00000000, R2:  0x0000000d
R3: 0x03c10000, R4:  0x0c494404, R5:  0x0c480afd
R6: 0x8100000d, R7:  0x148e3494, R8:  0x00000000
R9: 0x00000000, R10: 0x00000000, R11: 0x00000000
R12: 0x00000000
--------------------------------------------------------------------------------

Port /dev/ttyUSB6

...
[2018-11-30 06:33:09] (info) [1][ INSTALLER-01] Service init...
[2018-11-30 06:33:09] (info) [1][ INSTALLER-02] Message Engine (ota-installer-1.
[2018-11-30 06:33:09] (attn) [1][      CORE-03] Service (installer) Registered.3
[2018-11-30 06:33:09] (info) [1][ INSTALLER-01] worker thread:3, refId:0, startd
[2018-11-30 06:33:09] (info) [1][ INSTALLER-01] Service init done.
[2018-11-30 06:33:09] (info) [1][ INSTALLER-04] Service main Loop enter.
[2018-11-30 06:33:09] (info) [1][      CORE-01] Success launching 'download' (p)
[2018-11-30 06:33:09] (info) [1][DOWNLOADER-01] Service init
[2018-11-30 06:33:09] (info) [1][DOWNLOADER-02] Message Engine (ota-download-1).
[2018-11-30 06:33:09] (attn) [1][      CORE-03] Service (download) Registered. 2
[2018-11-30 06:33:09] (info) [1][DOWNLOADER-03] Entering downloader work loop
[2018-11-30 06:33:09] (info) [1][DOWNLOADER-04] Entering downloader work loop
[2018-11-30 06:33:09] (info) [1][DOWNLOADER-05] Entering downloader work loop
[2018-11-30 06:33:09] (info) [1][DOWNLOADER-06] Entering downloader work loop
��HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
��[2018-11-30 06:34:24] (info) [1][      CORE-04] Connected to NODE[1] (10.42.0)
[2018-11-30 06:34:24] (info) [1][      CORE-04] NODE[1] (10.42.0.101:65534) cond
[2018-11-30 06:34:24] (info) [1][      CORE-04] [PROXY_NET STATUS: ONLINE]
[2018-11-30 06:34:24] (warn) [1][      CORE-04] NODE[0] - NOT READY
[2018-11-30 06:34:24] (attn) [1][      CORE-04] NODE[1] - READY
��HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
HSM ERROR 244, CRITICAL_ERR_NVL_CAR
2

Dear kenji.funaoka,

Did you flash the Drive AGX system to the latest SDK via SDK manager?

If no, could you please update the Drive AGX system SDK with SDK manager. Thanks.

3

Dear Steve,

Yes, I flashed Xavier A+B via SDK manager successfully.
Though the situation is a little changed, DRIVE AGX still can’t boot Ubuntu

Are there anything that I can do?

l3_getsafetystatus

shell> l3_getsafetystatus
Info: Executing cmd: l3_getsafetystatus, argc: 0, args: 

Platform FuSa State: UNSAFE STATE
Platform Startup Status: STARTUP FAIL
Tegra A FuSa State: INIT STATE
Tegra B FuSa State: SAFE STATE
Tegra A nSAFE State: nSAFE ASSERTED
Tegra B nSAFE State: nSAFE DEASSERTED
Platform Error Log Count: 1

version

shell> version                                                                  
Info: Executing cmd: version, argc: 0, args:                                    
SW Version: DRIVE-V5.0.10-E3550-EB-Aurix-With3LSS-ForHyperion-3.00.07           
Compilation date: Jul 20 2018, 09:08:33                                         
Command Executed

Port /dev/ttyUSB2

...
Starting Safety                                                                 
��Starting virtualized QSPI driver ...                                          
��[    1.828073] CPU4: Failed to come online. Waiting 1s more...                
��Starting pipe manager...                                                     
��# Starting dtree-nvhvnet                                                      
��Starting pipe manager...                                                     
��Starting Clock init...                                                       
Unknown ttc option type = 0x0000000b                                            
��Starting Clock init...                                                       
��Running System clock period config                                           
Current clock period: 1000 usec                                                 
Applying clock period as: 10000 usec                                            
Enabling WDT driver...                                                          
��Unknown ttc option type = 0x0000000b                                         
Running System clock period config                                              
Current clock period: 1000 usec                                                 
Applying clock period as: 10000 usec                                            
��mount: Can't mount /ota/upload (type qnx6)                                    
mount: Possible reason: Corrupted file system detected                          
Formatting usr2-ota partition ...                                               
��Enabling WDT driver...                                                       
��platform_guest_warm_boot: guest warm reboot                                   
����[    2.575800] CPU4: Booted secondary processor [4e0f0040]                  
[    2.576044] CPU4: CPU online now.                                            
[    2.653539] CPU5: Booted secondary processor [4e0f0040]                      
[    2.655200] CPU5: CPU online now.                                            
��nvsafety starting                                                            
��[    2.708565] CPU6: Booted secondary processor [4e0f0040]                    
[    2.711081] CPU6: CPU online now.                                            
��Starting nvrm                                                                
Starting dtree-nvhvnet                                                          
# ��mount: Can't mount /ota/file_share (type qnx6)                              
mount: Possible reason: Corrupted file system detected                          
Formatting pers-ota partition ...                                               
��nvsafety started                                                             
starting NvGuard_Layer_1

Port /dev/ttyUSB6

...
[  OK  ] Started CUPS Scheduler.                                                
         Starting Initialization of TACP...                                     
         Starting LSB: automatic crash report generation...                     
��HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                           
��         Starting System Logging Service...                                   
[  OK  ] Started crash report submission daemon.                                
         Starting Permit User Sessions...                                       
         Starting Login Service...                                              
[  OK  ] Started Hypervisor initiated Shutdown Service.                         
         Starting LSB: Set up cgroupfs mounts....                               
         Starting Accounts Service...                                           
[  OK  ] Started D-Bus System Message Bus.                                      
[  OK  ] Started Avahi mDNS/DNS-SD Stack.                                       
[  OK  ] Started Make remote CUPS printers available locally.                   
[ INFO ] Network Manager is not active.                                         
[DEPEND] Dependency failed for Network Manager Wait Online.                     
[  OK  ] Reached target Network.                                                
         Starting Network Name Resolution...                                    
         Starting OpenBSD Secure Shell server...                                
         Starting oFono Mobile telephony stack...                               
[  OK  ] Started tos_daemon_service assists ... storage TA with FS operations.. 
[  OK  ] Started Run anacron jobs.                                              
[  OK  ] Started System Logging Service.                                        
[  OK  ] Started Network Name Resolution.                                       
[  OK  ] Started OpenBSD Secure Shell server.                                   
[  OK  ] Started Restore /etc/resolv.conf if...fore the ppp link was shut down. 
[  OK  ] Started Initialization of TACP.                                        
[  OK  ] Started Permit User Sessions.                                          
[  OK  ] Started LSB: Set up cgroupfs mounts..                                  
��HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                           
��[  OK  ] Started oFono Mobile telephony stack.                                
[  OK  ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".     
[  OK  ] Started LSB: Speech Dispatcher.                                        
[  OK  ] Started CUPS Scheduler.                                                
[  OK  ] Started LSB: automatic crash report generation.                        
[  OK  ] Started CUPS Scheduler.                                                
[  OK  ] Started CUPS Scheduler.                                                
[  OK  ] Started Login Service.                                                 
         Starting Docker Application Container Engine...                        
[  OK  ] Reached target Network is Online.                                      
         Starting LSB: Advanced IEEE 802.11 management daemon...                
         Starting Hyperion network setup...                                     
         Starting /etc/rc.local Compatibility...                                
[  OK  ] Started Fan control daemon.                                            
         Starting Light Display Manager...                                      
         Starting dnsmasq - A lightweight DHCP and caching DNS server...        
���34469192|HV/c0: �����vpr base=0:f0000000, size=80, ctrl=1, override:(a01a834)
�����34470955|HV/c0: �����(255) csw_pcie0w: MC request violates VPR requirements
�����34472270|HV/c0: �����  status = 0x0ff740d9; addr = 0xffffffff00            
�����34473371|HV/c0: �����  secure: yes, access-type: write                     
�����34474327|HV/c0: �����SMMU instance: 1                                      
�����34476329|HV/c0: �����CB32 SMMU fault. StreamID: 86                         
�����34481514|HV/c0: �����FSR: 0x80000402; FAR: 0xfff0b000; FSYND0: 0x340013    
����HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                         
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
���[00068073] wdt: expired vmid 0                                               
��HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                           
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
��[00128073] wdt: expired vmid 0                                                
��HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                           
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
HSM ERROR 244, CRITICAL_ERR_NVL_CAR                                             
��[00188073] wdt: expired vmid 0                                                
��HSM ERROR 244, CRITICAL_ERR_NVL_CAR
4

Hi kenji.funaoka,

Would you please help to upload the full logs available at below locations?
-. ~/.nvsdkm/sdkm.log
-. ~/.nvsdkm/logs

The log file I asked is in your host PC.

Thanks

5

Hi kenji.funaoka,

mount: Can’t mount /ota/upload (type qnx6)
Why is there a qnx partition? Isn’t your target operating system “linux”?

6

Hi kayccc and vickyy,

I’ll upload the log files tomorrow.

I’m not sure why qnx partition appears.
AFAIR, there is no choice about qnx on SDK manager.
nvsdkm_boot_problem_20181205.tar.gz (395 KB)

7

P.S. My target OS is Linux. I don’t have QNX.

8

Dear kenji.funaoka,

I uploaded the file you provided on your topic.
We will check the log and update. Thanks.

9

Hi, Steve,

Thank you for the upload.
I found the following lines in sdkm.log for examples:

2018-11-30 15:10:38.173 - info: validating product line for target OS: QNX

2018-12-04 11:16:55.660 - info: /home/autoware/nvidia/nvidia_sdk/DRIVE/Linux/5.0.10.3/SW/DrivePDK/toolchains/tegra-4.9-nv/usr/bin/aarch64-gnu-linux/aarch64-gnu-linux-gcc -E -D __QNX__ -MMD -MP -x assembler-with-cpp -I/home/autoware/nvidia/nvidia_sdk/DRIVE/Linux/5.0.10.3/SW/DrivePDK/drive-t186ref-foundation/virtualization/pct/e3550b01-t194b/../dtb_include -I/home/autoware/nvidia/nvidia_sdk/DRIVE/Linux/

I’m not sure where QNX come from.

10

Hi,

Have you resolved your problem?

11

Not yet. Another person told me that similar issue occured. It seems not only my environment.

I’m having very similar issues like you are having in the thread you started below.

12

May I have the thorough steps to reproduce such error?

Did you install QNX on your platform before?

13

Just one more confirm here. What revision is your sdkmanager?

14

Thank you for your help!

Did you install QNX on your platform before?

No.

What revision is your sdkmanager?

The revision of my sdkmanager is 0.9.8.

May I have the thorough steps to reproduce such error?

I’ve retried the procedure. The results are changed as shown in the following.

  1. Launch NVIDIA SDK MANAGER GUI
$ ./sdkmanager

  1. Login DEVZONE on the GUI

  2. Push Update button in “New version is available. SDK Manager version 0.9.9 is now available [current version installed: 0.9.8].”

  3. STEP 01: PRODUCT CATEGORY = “DRIVE”, HARDWARE CONFIGURATION = “Host Machine” and “Target Hardware DRIVE AGX DevKit”, TARGET OPERATING SYSTEM = “Linux DRIVE Software 1.0” and CONTINUE TO STEP 02

  4. STEP 02: Check “I accept the terms and conditions of the license agreements” and CONTINUE TO STEP 03

  5. Push OK button in “Installation of the following component requires privileged access to your host machine: OSS and NV packages”

Finally, the GUI shows INSTALLATION FAILED Review terminal tab for details. Resolve and RETRY.

The terminal tab shows

13:42:8 ERROR : Zombie components detected, please check log
etc...

I’ll attach the log.
nvsdkm.tar.gz (133 KB)

15

So there is installation issue now. Did you change any setting on your host?

16

No setting is changed. I’ve uploaded the log into the previous post. Can something be found?

17

My acquaintance who has PX2 said that he recovery a PX2 by using bootburn.sh.
Can I use bootburn.sh for DRIVE AGX? If yes, would you tell me where it is?
I can’t find it in sdkm_downloads dir specified in NVIDIA SDK MANAGER.

18

Not sure if this is related. I will look into it.

In the mean time, are you able to try different host or different drive AGX device and see if you can always hit installation error?

19

Thanks, I’ll try

20

bootburn should be under the folder like below.

~/nvidia/nvidia_sdk/DRIVE/Linux.