Issue flashing SSD with SDK manager

I am trying to flash the latest version of JetPack 5.1.2 on a XavierNX developer kit. When I flash the root partition does not use the full size of the SDD (1024gb) and 15 partitions are created.
I tried to change some files in SDK manager as the following post, but the flash process gets stuck on 99%:

When trying to flash the SDK manager displays a message:

Installation of ‘Flash Jetson Linux’ is taking longer than expected.
Do you want to continue installing this package?

I am attaching the logs.
This is the last part of the logs:

17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3381 ] tegrasign_v3.py --key None --list blob_tegra194-p3668-0000-p3509-0000_aligned_sigheader.dtb_list.xml --pubkeyhash pub_key.key
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3386 ] Assuming zero filled SBK key
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3521 ] Warning: pub_key.key is not found
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.2980 ] tegrahost_v2 --chip 0x19 0 --updatesigheader blob_tegra194-p3668-0000-p3509-0000_aligned_sigheader.dtb.encrypt blob_tegra194-p3668-0000-p3509-0000_aligned_sigheader.dtb.hash zerosbk
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3186 ] tegrahost_v2 --chip 0x19 --generateblob blob.xml blob.bin
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3210 ] number of images in blob are 11
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3216 ] blobsize is 6500424
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3219 ] Added binary blob_nvtboot_recovery_cpu_t194_sigheader.bin.encrypt of size 232976
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3321 ] Added binary blob_nvtboot_recovery_t194_sigheader.bin.encrypt of size 206016
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3331 ] Added binary blob_preboot_c10_prod_cr_sigheader.bin.encrypt of size 24016
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3338 ] Added binary blob_mce_c10_prod_cr_sigheader.bin.encrypt of size 145184
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3349 ] Added binary blob_mts_c10_prod_cr_sigheader.bin.encrypt of size 3430416
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3434 ] Added binary blob_bpmp-2_t194_sigheader.bin.encrypt of size 1007392
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3459 ] Added binary blob_tegra194-a02-bpmp-p3668-a00_lz4_sigheader.dtb.encrypt of size 36176
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3506 ] Added binary blob_spe_t194_sigheader.bin.encrypt of size 95232
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3514 ] Added binary blob_tos-optee_t194_sigheader.img.encrypt of size 977664
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3534 ] Added binary blob_eks_t194_sigheader.img.encrypt of size 5136
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3544 ] Added binary blob_tegra194-p3668-0000-p3509-0000_sigheader.dtb.encrypt of size 340032
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3746 ] Sending bootloader and pre-requisite binaries
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3775 ] tegrarcm_v2 --download blob blob.bin
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.3796 ] Applet version 01.00.0000
17:28:58 INFO: Flash Jetson Linux - flash: [ 7.4310 ] Sending blob
17:29:00 INFO: Flash Jetson Linux - flash: [ 7.4313 ] [... ] 016% [ 7.4313 ] [... ] 032% [ 7.4313 ] [... ] 048% [ 7.4313 ] [... ] 064% [ 7.4313 ] [... ] 080% [ 7.4313 ] [...] 096% [ 7.4313 ] [...] 100%
17:29:00 INFO: Flash Jetson Linux - flash: [ 8.8587 ] tegrarcm_v2 --boot recovery
17:29:00 INFO: Flash Jetson Linux - flash: [ 8.8617 ] Applet version 01.00.0000
18:19:46 INFO: Flash Jetson Linux - flash: [ 9.9331 ] tegrarcm_v2 --isapplet
18:19:46 INFO: Flash Jetson Linux - flash: [ 1023.7076 ] tegrarcm_v2 --ismb2
18:19:46 INFO: Flash Jetson Linux - flash: [ 2039.5310 ] tegradevflash_v2 --iscpubl

At the end I got tired of waiting and disconnected the board.

Any help would be highly appreciated.
Thank you,
Luis
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_Xavier_NX_modules_2023-11-13_17-24-55.zip (51.0 KB)

Hi,

Please also dump serial console log as instructed here:

Sorry I do not have the USB-serial device available now

Then it’s hard to further allocate the issue.
I can only suggest trying more times or maybe switching for a different host PC or USB cable/port.

I have an USB-232 header that I will have to take apart, but I do not know if it will work because it is old.
If I get it working: when does the logs need to be captured? During the whole flashing process?

YES, please capture log during the whole flashing process.

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