Jetson orin NX 8G Flash jetson Linux fail

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
,
1

hi team
we design the carrier board ourselves, we design the sch according to Xavier NX reference design. when we install the orin NX 8GB CPU module and the NvME SSD. put the CPU into Recover Mode, and the download process will fail at 91% of flash Jetson linux. when happens,the USB device disappear first, then the sdkmanager display error.

SDKM_logs_2023-04-04_14-00-01.zip (740.6 KB)
13:57:25 ERROR: Flash Jetson Linux - flash: kpoint 540000

13:57:26 ERROR: Flash Jetson Linux - flash: 550000

13:57:57 ERROR: Flash Jetson Linux - flash: [ 0.4338 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported

13:57:57 ERROR: Flash Jetson Linux - flash: [ 0.4363 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported

13:57:57 ERROR: Flash Jetson Linux - flash: [ 0.4684 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported

13:58:03 ERROR: Flash Jetson Linux - flash: 39726 blocks

13:58:03 ERROR: Flash Jetson Linux - flash: gzip: /home/nvidia/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format

13:58:11 ERROR: Flash Jetson Linux - flash: 56174 blocks

13:58:12 ERROR: Flash Jetson Linux - flash: 20 bytes copied, 0.000684374 s, 29.2 kB/s

13:58:14 ERROR: Flash Jetson Linux - flash: 67108864 bytes (67 MB, 64 MiB) copied, 1.63707 s, 41.0 MB/s

13:58:20 ERROR: Flash Jetson Linux - flash: Node /fragment@0 has a unit name, but no reg property

13:58:20 ERROR: Flash Jetson Linux - flash: /home/nvidia/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property

13:58:25 ERROR: Flash Jetson Linux - flash: [ 4.3418 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported

13:58:28 ERROR: Flash Jetson Linux - flash: [ 7.2748 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported

13:58:28 ERROR: Flash Jetson Linux - flash: [ 7.3192 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED5/ is not supported

13:58:28 ERROR: Flash Jetson Linux - flash: [ 7.3276 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_MCE_COVERAGE/ is not supported

13:58:34 ERROR: Flash Jetson Linux - flash: 56174 blocks

13:58:42 ERROR: Flash Jetson Linux - flash: 83155 blocks

13:58:49 ERROR: Flash Jetson Linux - flash: [ 0.4828 ] ERROR: might be timeout in USB write.

13:58:49 ERROR: Flash Jetson Linux - flash: command terminated with error

13:58:49 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

the full sdkmanager log is in attachment.
the CPU module + SSD can be download ok in your xavier NX developer kit.
we want to know what cause this issue, what’s wrong prevent the download going on?

2

Is this a ubuntu 20.04 host? Is this host ever able to flash any orin platform before?

3

yes the host is Ubuntu 20.04,and not use the Virtual Box or VMware.
this PC flash the orin NX first time.

4

There is a known issue that some ubuntu 20.04 host has problem in flashing Orin.

Could you share the info of this host machine? Kernel version, which vendor is it.

5

Screenshot from 2023-04-04 14-11-16
Screenshot from 2023-04-04 14-11-161920×1080 103 KB

it’s a Industry PC. if needed, i can change the OS to 18.04.
do you advise?

6

Do you have xavier nx devkit to test instead of custom board first?

7

no，we don’t have one.
last Friday, I took one pcs CPU+SSD to Nvidia agilent, the CPU+SSD can download the image and bring up ok.
update the debug uart log:
2304062021-debug_usb_log_fail.txt (50.0 KB)

8

Looks same as this post.

9

we have modify the DTSI in Linux_for_Tegra/bootloader/t186ref/BCT/tegra234-mb2-bct-misc-p3767-0000.dts, when bring-up, we check the log message, it became effect.
we don’t know how to make sure the CPU in RCM mode, find the USB device(0955:7423)?
无法确认这个芯片是否在RCM模式，通过USB设备？但是上位机已经有USB设备了，还是无法烧录，是什么条件或者缺少什么？

10

請問一下你現在的error是什麼？

如果lsusb可以看到0955:7423 而且flash tool可以開始跑, 那就是在rcm mode了

至於燒錄失敗就要看你的error log決定了. 到目前為止我從其他custom board那邊看下來大概有4~5種原因. 所以還是需要你們的log判斷

11

失败的原因似乎是cvm通讯异常，刷写日志如下：
[ 1.2807 ] MB2 Applet version 01.00.0000
[ 1.3180 ] 000000001f1e0506: E> NV3P_SERVER: Could not read eeprom for module cvm.

[ 1.4207 ] tegradevflash_v2 --oem platformdetails eeprom cvm /home/muyi/Desktop/sdk/rootfs/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 1.4220 ] Error: Invalid option --chip
debug usb日志如下：
E> NV3P_SERVER: Failed to get eeprom handle for cvm from eeprom manager.
E> NV3P_SERVER: Could not read eeprom for module cvm.
debug_usb_log_1120.txt (6.0 KB)
flash_log_1120.txt (15.3 KB)

12

這邊麻煩注意一下… 我們的文件只請你把cvb eeprom關掉… 沒有說cvm eeprom也要關掉…
如果你不小心關掉了 麻煩改回來.

13

muyi@ubuntu:~/Desktop/sdk/rootfs/Linux_for_Tegra/bootloader$ cat t186ref/BCT/tegra234-mb2-bct-misc-p3767-0000.dts
/dts-v1/;

#include “tegra234-mb2-bct-common.dtsi”

/ {
mb2-misc {
eeprom {
cvm_eeprom_i2c_instance = <0>;
cvm_eeprom_i2c_slave_address = <0xa0>;
cvm_eeprom_read_size = <0x100>;
cvb_eeprom_i2c_instance = <0x0>;
cvb_eeprom_i2c_slave_address = <0xae>;
cvb_eeprom_read_size = <0>;
};
};
};

14

CVM部分，我们肯定没有修改。报错很多都和这个相关。
我们在烧录过程中，不论是命令，还是SDK，报错返回值有3，4，8，甚至会读不到RCM state.

15

如果cvm這部份沒有更動的話 可能是硬體部份的問題.

16

您估计是哪一块？烧录部分只涉及供电，usb，reset/recovery，nvme，上电时序。

18

这个是我拿了一片新的CPU+SSD，第一次刷机的log：
log如txt：
muyi_newCPU_PClog_230407.txt (16.5 KB)

[ 0.9964 ] Retrieving EEPROM data
[ 0.9965 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/nvidia/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 1.0000 ] MB2 Applet version 01.00.0000
[ 1.0033 ] 000000001414032a: E> NV3P_SERVER: Could not read eeprom for module cvm.
[ 1.0464 ]
[ 1.0464 ]
[ 1.0517 ] tegradevflash_v2 --oem platformdetails eeprom cvm /home/nvidia/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 1.0559 ] Error: Invalid option --chip

19

Hi,

建議你可以把log弄成txt然後附件. 直接複製貼上format都會跑掉…

另外flash error也需要UART那邊的log. 麻煩也附上一下 我猜應該還是cvm read failure.

20

把两个log都上传了。
PC_flash_log_1722.txt (15.4 KB)

debugUART_log_1722.txt (6.0 KB)

21

any comments?