R35.4.1 failed to flash jetson xavier NX 8GB module, erasing spi failed

when I flash the L4T R35.4.1, some error info printed now(Days ago,the process is normal).
1,start flash it by sdkmanager. open the terminal window of sdkmanager.
2,in the middle of the process, some error info printed.

10:16:53 ERROR: Flash Jetson Linux - flash: 42010 blocks
10:16:53 ERROR: Flash Jetson Linux - flash: gzip: /home/herman/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format
...
10:17:19 ERROR: Flash Jetson Linux - flash: 20 bytes copied, 0.000903706 s, 22.1 kB/s
...
10:26:11 ERROR: Flash Jetson Linux - flash: /home/herman/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration_updated.dts: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property

3,when the message showing ‘erasing spi:0 …’, a window showing the info below.

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

4,I selected “yes”, then the printinfo block for a long time(longer than 40mins) until i stop the process manually.

10:28:26 INFO: Flash Jetson Linux - flash: [ 13.6514 ] Erasing spi: 0 .........
11:00:13 INFO: Flash Jetson Linux - flash: [Failed]
11:00:13 INFO: Flash Jetson Linux - flash: Command tegradevflash_v2 --pt flash.xml.bin --create
11:00:13 INFO: Flash Jetson Linux - flash: Failed flashing t186ref.
11:00:13 ERROR: Flash Jetson Linux - flash: *** ERROR: flashing failed.
11:00:14 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 43m52s ]
11:00:14 ERROR: Flash Jetson Linux - flash: command terminated with error
11:00:14 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

Is there anybody know what happend?

Dump the full log, please.
Don’t crop it yourself.

Please also do this:

SDKM_logs_2024-01-17_11-36-18.zip (181.4 KB)
hiDaveY Y Y,
this is the full log file, I need your help! thank you!

Please also dump the serial console log as indicated.

[com COM4] (2024-01-18_115437) COM4 (USB-Enhanced-SERIAL CH9102 (COM4)).log (6.9 KB)
sdkm-2024-01-18-11-50-02.log (219.5 KB)
Hi DaveYYY,
The two log files are the sdkm and serial console log.Thank you!

Hi,

Do you have other modules for testing?

[2702.509] E> SPI_FLASH: Could not erase Qspi Bulk.
[2702.510] E> Blockdev erase: exit error = e111006
[2702.511] E> NV3P_SERVER: Could not erase blocks from 0 to 65536 of 0 instance of device 3.

I feel like maybe the module itself is broken.

[com COM4] (2024-01-18_140445) COM4 (USB-Enhanced-SERIAL CH9102 (COM4)).log (77.2 KB)
sdkm-2024-01-18-14-01-17.log (496.7 KB)
Hi, DaveYYY,
this are the log files of an other modules. thank you!

These logs look fine, so the issue is clearly about the module you tried first.
If the same issue keeps happening, please RMA it.

could we get the info that which component is broken from the log, and repair the module?

Please don’t try to repair it yourself.
Ask our service team.

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