Drive OS 6.0.8.1 flashing error

[abdul.rehman3]

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

I am trying to flash DriveOS 6.0.8 on Orin with Nvidia Docker container. Before that I installed 6.0.6 and it was successful. Here is the ticket for that topic. Nvidia Drive AGX Orin Flashing Error - #12 by abdul.rehman3

Now I am getting a flashing error. I have tried almost all the solutions. Flashing Drive AGX Orin fails

I followed these guidelines. Set Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC) | NVIDIA Docs

I made sure that all serial ports of ORIN were closed before flashing. When Orin was flashing. It restarted once automatically.
Following were the questions asked in the previous ticket.

1. Current DRIVE OS version on target (check cat /etc/nvidia/version-ubuntu-rootfs.txt on target
   nvidia@tegra-ubuntu:~$ cat /etc/nvidia/version-ubuntu-rootfs.txt
6.0.6.0-32441545

2. See if Tegra and Aurix is accessible from host using minicom.
   Yes it is
   

   

3. Make sure there is two wire connection between host and target as mentioned in Quick start guide. Check if an additional NVIDIA device is visible on host when running lsusb on host when the target in put in recovery mode.
   

   

4. Make sure target is in normal mode before trying to flash.
   It was in normal mode.

5. Attach the flashing logs.
   driveinstaller.log (1.5 MB)
   log_0i8v4rdyahw2tomuc6bfzq1573nskgl9.txt (2.1 KB)

I also run bootburn.py separately and got the following error

`tempBuf written to A_34_kernel_zerosign.img
Creating Filesystem image for partition gos0-rw-overlay
:[E]: QbCreateFSImagesExt : 386: Error (Unknown) (0x8900)
:[E]: mkfs failed cmd= [sudo /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/__temp_t234/Tegra-A-50df0b1f795/flash-images/mkfs.ext4 -F -q -b 4096 A_gos0-rw-overlay_36_ext4.img]
:[E]: QbFindAndCreateImages : 1286: Error (Unknown) (0x8900)
:[E]: FSImage creation failed
:[E]: QbCreatePartition : 2021: Error (Unknown) (0x8900)
:[E]: failed to find and create images
Failed to create partitions
:[E]: nvimagegen : 1093: Error (Unknown) (0x8900)
:[E]: Creating Partition images failed
finish nvimagegen
Error Code 8900
nt=0
MB1_BCT: checking sub cfg’s partition 17 name=nvdec-fw adx= 7864320size= 524288 IsPersistent=0
MB1_BCT: selected FW field for partition 54
MB1_BCT: localadx= 7864320, globaladx= 65273856, startblock= 127488 size= 524288
MB1_BCT: checking sub cfg’s partition 18 name=ist-ucode adx= 8388608size= 262144 IsPersistent=0
MB1_BCT: selected FW field for partition 40
MB1_BCT: localadx= 8388608, globaladx= 65798144, startblock= 128512 size= 262144
MB1_BCT: checking sub cfg’s partition 19 name=bpmp-ist adx= 8650752size= 262144 IsPersistent=0
MB1_BCT: selected FW field for partition 41
MB1_BCT: localadx= 8650752, globaladx= 66060288, startblock= 129024 size= 262144
MB1_BCT: checking sub cfg’s partition 20 name=ist-config adx= 8912896size= 262144 IsPersistent=0
MB1_BCT: selected FW field for partition 42
MB1_BCT: localadx= 8912896, globaladx= 66322432, startblock= 129536 size= 262144
MB1_BCT: checking sub cfg’s partition 21 name=ist-testimg adx= 0size= 1342177280 IsPersistent=0
MapPartitionTypeT23x Unknown PartitionType 50
MB1_BCT: checking sub cfg’s partition 22 name=ist-runtimeinfo adx= 1342177280size= 262144 IsPersistent=0
MapPartitionTypeT23x Unknown PartitionType 72
MB1_BCT: checking sub cfg’s partition 23 name=ist-resultdata adx= 1342439424size= 209715200 IsPersistent=1
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 24 name=gr-ist adx= 1552154624size= 262144 IsPersistent=1
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 25 name=gos0-crashlogs adx= 1552416768size= 1048576 IsPersistent=1
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 26 name=custom adx= 1553465344size= 3670016 IsPersistent=0
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 27 name=secure-os adx= 0size= 4194304 IsPersistent=0
MB1_BCT: checking sub cfg’s partition 28 name=adsp-fw adx= 4194304size= 2097152 IsPersistent=0
MB1_BCT: checking sub cfg’s partition 29 name=fsi-fw adx= 6291456size= 6291456 IsPersistent=0
MB1_BCT: checking sub cfg’s partition 30 name=xusb-fw adx= 12582912size= 262144 IsPersistent=0
MB1_BCT: checking sub cfg’s partition 31 name=dce-fw adx= 12845056size= 9437184 IsPersistent=0
MB1_BCT: checking sub cfg’s partition 32 name=pvit adx= 22282240size= 262144 IsPersistent=0
MapPartitionTypeT23x Unknown PartitionType 69
MB1_BCT: checking sub cfg’s partition 33 name=pva-fw adx= 22544384size= 2621440 IsPersistent=0
MB1_BCT: checking sub cfg’s partition 34 name=kernel adx= 25165824size= 10485760 IsPersistent=0
MB1_BCT: checking sub cfg’s partition 35 name=guest-linux adx= 35651584size= 27936161792 IsPersistent=0
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 36 name=gos0-rw-overlay adx= 27971813376size= 1073741824 IsPersistent=0
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 37 name=qnx-update adx= 29045555200size= 25165824 IsPersistent=0
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 38 name=qnx-update-fs adx= 29070721024size= 134217728 IsPersistent=1
MapPartitionTypeT23x Unknown PartitionType 43
MB1_BCT: checking sub cfg’s partition 39 name=ufs-eco-dummy adx= 29204938752size= 1048576 IsPersistent=1
MapPartitionTypeT23x Unknown PartitionType 43
Updating MB1 BCT to file
:[I]: QbPartMgrGetIdByName: Could not find a match for given partition name: mb1-bct
:[I]: QbPartMgrGetIdByName: Could not find a match for given partition name: mb1-bct-r
metadata for partition bct created under filename meta_bct.txt
:[E]: QbFindAndCreateImages : 1502: Error (Unknown) (0xff00)
:[E]: Failed to exectute nvimagegen: ./nvimagegen --parentcfg /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/__temp_t234/Tegra-A-50df0b1f795/flash-images/tmp_global_storage.cfg --cfg /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/__temp_t234/Tegra-A-50df0b1f795/flash-images/tmp_global_storage_sub2.cfg --prefix A --chip 0x23 --chipver A01 --mb1bct bct_MB1.bct --bct_der_consts /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/__temp_t234/Tegra-A-50df0b1f795/der_const_val.bin --pvitversion 6.0.8.1-34176994 --membct membct_0.bct membct_1.bct membct_2.bct membct_3.bct --showpt --man man_A.txt
:[E]: QbCreatePartition : 2021: Error (Unknown) (0xff00)
:[E]: failed to find and create images
Failed to create partitions
:[E]: nvimagegen : 1093: Error (Unknown) (0xff00)
:[E]: Creating Partition images failed
finish nvimagegen
Error Code ff00

[bootburnTegra-A]: [executeShellCommand(172)] : Return code: 255
command line used was:
[‘/drive/drive-foundation//tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘-x’, ‘/dev/ttyACM1’]

s_ERROR_TOOL_NVIMAGEGEN

Exception 46 raised in bootburn_active
Traceback (most recent call last):
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn.py”, line 156, in bootburn_active
bootburnOrin.Boot_Create_Flash_Coldboot()
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn_orin.py”, line 755, in Boot_Create_Flash_Coldboot
self.CreateVDKImages(self.targetConfig.f_FlashCfg, self.targetConfig.p_OutDirPath, “flash-images”)
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn_orin.py”, line 333, in CreateVDKImages
self.GenerateImage(self.storageCfgParser.cfgFileList, l_Operation, operationPath)
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn_lib.py”, line 2505, in GenerateImage
AbnormalTermination(“s_ERROR_TOOL_NVIMAGEGEN”, nverror.NvError_NvImagegen)
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/flashtools_nverror.py”, line 251, in AbnormalTermination
raise OSError(errorCode)
OSError: 46`

Moreover, I can’t find 6.0.8 in the sdkmanager

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,

Check if an additional NVIDIA device is visible on host when running lsusb on host when the target in put in recovery mode.

Here I expect to see two NVIDIA devices in host’s lsusb output when target is set in recovery mode via aurix console. I see only one NVIDIA. Could you share the host/target connection as well for confirmation.

I see docker installation was successful in previous post. So, you could install DRIVE OS 6.0.6 using docker or sdkmanager or both?

I understand you noticed issues when flashing DRIVE OS 6.0.8.1. Do you see flashing issue when trying to flash DRIVE OS 6.0.6 as well. Could you verify that?
Please poweron/off both host and target before you try flashing again.

Did you set board in recovery mode when you try to manual flashing using bootburn?

FYI, DRIVE OS 6.0.8.1 is available only on docker.

[abdul.rehman3]

Dear @SivaRamaKrishnaNV ,

In recovery mode

I see docker installation was successful in previous post. So, you could install DRIVE OS 6.0.6 using docker or sdkmanager or both?
It was success full with both.

I understand you noticed issues when flashing DRIVE OS 6.0.8.1. Do you see flashing issue when trying to flash DRIVE OS 6.0.6 as well. Could you verify that?
Please poweron/off both host and target before you try flashing again.
I tried re-flashing 6.0.6 and it also failed with docker and sdkmanager aswell.

Yes. I tried with recovery button and by turning on recovery mode from shell as well. Getting same error.

Do I need to check permissions for the recovery USB ports? if yes, how can i do it?

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
I am assuming, micro usb debug port and LEFT Type C port on target are connected from host. Can you share the connection picture for confirmation?
After successfully flashing the board with 6.0.6 using docker, Is the board used in office premises only? Is there any change in board state? Did you notice any issue with the board and hence wanted to reflash?

Also, did you make any changes in docker container i.e used for flashing? You may give a try from another host or re-download the docker to rule out host state related issues.

From logs, I see the board is going to recovery mode with out any issue. Lets follow below steps.

1. Reboot host and run common_if_testapp -mcureset to reboot the target.
2. Try flash using bootburn

cd /drive/drive-foundation
make/bind_partitions -b p3710-10-s05 linux clean
make/bind_partitions -b p3710-10-s05 linux
#put the board in recovery mode(run tegrarecovery x1 on and tegrareset x1 on aurix)
tools/flashtools/bootburn/bootburn.py -b <board config> -B qspi
##put the board in normal mode(run tegrarecovery x1 off and tegrareset x1 on aurix)

If you notice errors in any of the above commands, please share the logs.

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
Does host has enough space? Could you share df -h?

[abdul.rehman3]

Dear @SivaRamaKrishnaNV

Connection on the host and target. Blue light indicates that target is connected

Board is only used in office premises. There is no change in board state. New camera rev is not supported on 6.0.6 sdk and is only supported on 6.0.8. Thats why I have to upgrade OS.

Unfortunately, I don’t have another host but I did re-downloaded docker and created a new DriveOS image.

Following are the logs after following your instructions.

log_bootburn.txt (85.6 KB)

df-h

[abdul.rehman3]

Hi @SivaRamaKrishnaNV ,

I have installed everything from scratch on the other system but getting a same error.

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
We notice such errors in past when there is not enough space. Please double check if host meets the requirements at Requirements for Your Development Environment | NVIDIA Docs

[abdul.rehman3]

Dear @SivaRamaKrishnaNV ,

As I told you earlier that I have tried on 2 systems and I also shared with you a disk space in the picture above. I think its not about the space on the host side.

[abdul.rehman3]

Dear @SivaRamaKrishnaNV ,

I have tried to flash 6.0.6 with sdk manager and getting a same error. I am pretty sure that this issue is not related to memory. Please find logs for 6.0.6 flashing. Also the behavior of flashing is no different from 6.0.8. Please provide a concrete solution.

driveinstaller.log (566.4 KB)

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
Thanks for sharing the logs. I am checking internally on this and update you. I assume board is still accessible without any issue.

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
May I know the RAM of host? Is it above 8GB? Did you check if increasing RAM allocation to docker can fix the issue?
Do you have other target to check flashing from same host to see if it succeed?

[abdul.rehman3]

Dear @SivaRamaKrishnaNV ,

RAM before running nvidia container

RAM while running

Docker container stats

By default all the ram is allocated to the container.

RAM is not increasing much. I have tried another target but getting same error.

[abdul.rehman3]

Dear @SivaRamaKrishnaNV

When can i expect a reply from you?

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
I am still discussing on this issue internally.

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
Could you check the private message.

[SivaRamaKrishnaNV]

Dear @abdul.rehman3,
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks
Did you get a chance to test from another host?