Xavier start failed

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

[14:19:06.087]收←◆\0
[14:19:06.456]收←◆\0?
[0000.084] I> MB1 (prd-version: 1.1.0.0-t194-41334769
[14:19:06.509]收←◆-514a1108)
[0000.090] I> Boot-mode: L0 coldboot
[0000.093] I> Chip revision : A02P
[0000.096] I> Bootrom patch version : 15 (correctly patched)
[0000.101] I> ATE fuse revision : 0x200
[0000.105] I> Ram repair fuse : 0x0
[0000.108] I> Ram Code : 0x2
[0000.110] I> rst_source : 0x0
[0000.113] I> rst_level : 0x0
[0000.116] I> Boot-device: eMMC
[0000.119] W> DEVICE_PROD: device prod is not initialized.
[0000.124] W> DEVICE_PROD: device prod is not initialized.
[000
[14:19:06.685]收←◆0.141] I> sdmmc DDR50 mode
[0000.145] W> DEVICE_PROD: device prod is not initialized.
[0000.151] W> No valid slot number is found in scratch register
[0000.156] W> Return default slot: _a
[0000.159] I> Active Boot chain : 0
[0000.162] I> Boot-device: eMMC
[0000.166] E> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.172] E> MB1_PLATFORM_CONFIG: Failed to initialize device prod.
[0000.180] I> Temperature = 33500
[0000.183] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.187] W> Skipping boost for clk: BPMP_APB
[0000.191] W> Skipping boost for clk: AXI_CBB
[0000.195] W> Skipping boost for clk: AON_CPU_NIC
[0000.199] W> Skipping boost for clk: CAN1
[0000.203] W> Skipping boost for clk: CAN2
[0000.207] I> Boot-device: eMMC
[0000.210] I> Boot-device: eMMC
[0000.220] I> Sdmmc: HS400 mode enabled
[0000.228] I> ECC region[0]: Start:0x0, End:0x0
[0000.232] I> ECC region[1]: Start:0x0, End:0x0
[0000.236] I> ECC region[2]: Start:0x0, End:0x0
[0000.240] I> ECC region[3]: Start:0x0, End:0x0
[0000.244] I> ECC region[4]: Start:0x0, End:0x0
[0000.248] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.254] I> Non-ECC region[1]: Start:0x0, End:0x0
[0000.258] I> Non-ECC region[2]: Start:0x0, End:0x0
[0000.263] I> Non-ECC region[3]: Start:0x0, End:0x0
[0000.267] I> Non-ECC region[4]: Start:0x0, End:0x0
[0000.273] W> MB1_PLATFORM_CONFIG: Rail ID 9 not found in pmic rail config table.
[0000.280] E> FAILED: Thermal config
[0000.283] W> DEVICE_PROD: device prod is not initialized.
[0000.288] W> DEVICE_PROD: device prod is not initialized.
[0000.297] W> MB1_PLATFORM_CONFIG: Rail ID 7 not found in pmic rail config table.
[0000.304] E> FAILED: MEMIO rail config

[14:19:06.713]收←◆[0000.325] I> scrub mode: full dram
[0000.328] E> FUSE: Failed to verify ECID.
[0000.343] I> sdmmc bdev is already
[14:19:06.728]收←◆initialized

[14:19:06.760]收←◆[0000.379] W> No fuse-bypass data

2

Hello，Xavier carrier board failed to start and the debug UART showed log as stated above. So I want to know why xavier failed start and what does the log message mean?something about fuse?

4

hello ligang20,

may I know which JetPack release it was flashed. is this Xavier enable Jetson security, such as secureBoot or secureOS?

5

The version is Jetpack4.2. SecureBoot and Secure OS are disabled.

6

hello ligang20,

are you able to download the latest JetPack release and flash the target again?
thanks

7

This is just accurred a few times. I want to konw whick step the xavier is stucked in when it boot. And what could cause this failure.

8

hello ligang20,

did you mean it could workaround by another reboot cycle?
may I know what’s the failure rate, thanks

9

yes. maybe happen for about 4~5 times.

10

hello ligang20,

did you have any customization, how many reboot cycles able to see the failure, is there a percentage about the failure rate?

11

That is not sure. Only a few times happened.

12

hello ligang20,

since it’s test with JetPack-4.2.
could you please moving to the latest JetPack release, (i.e. JetPack-4.5.1) for confirmation.
thanks

15

Does Jetpack Version have impact on the Xavier startup?

16

hello ligang20,

I’ve never seems this failure before,
please moving to the latest JetPack release and you should initial another new discussion thread for further supports.
please also check Release Notes, to review the known issues and bug fixes.
thanks

17

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