Top caller module: SDMMC, error module: SDMMC, reason: 0x02, aux_info: 0x09

Hi Nvidia team,

There are two devices that cannot boot and get stuck at the following log :

I> MB2 (version: 0.0.0.0-t234-54845784-af79ed0a)
I> t234-A01-1-Silicon (0x12347)
I> Boot-mode : Coldboot
I> Emulation:
I> Entry timestamp: 0x001e8717
I> Regular heap: [base:0x40040000, size:0x10000]
I> DMA heap: [base:0x102e000000, size:0x800000]
I> Task: SE error check
I> Task: Crypto init
I> Task: MB2 Params integrity check
I> Task: Enable CCPLEX WDT 5th expiry
I> Task: ARI update carveout TZDRAM
I> Task: Configure OEM set LA/PTSA values
I> Task: Check MC errors
I> Task: Enable hot-plug capability
I> Task: PSC mailbox init
I> Task: Enable clock for external modules
I> Task: Measured Boot init
I> Task: fTPM silicon identity init
I> fTPM is not enabled.
I> Task: OEM SC7 context save init
I> Task: I2C register
I> Task: Map CCPLEX_INTERWORLD_SHMEM carveout
I> Task: Program CBB PCIE AMAP regions
I> Task: Boot device init
I> Boot_device: QSPI_FLASH instance: 0
I> Qspi clock source : pllc_out0
I> QSPI Flash: Macronix 64MB
I> QSPI-0l initialized successfully
I> Secondary storage device: QSPI_FLASH instance: 0
I> Secondary storage device: SDMMC_USER instance: 3
C> Task 0x0 failed (err: 0x39390902)
E> Top caller module: SDMMC, error module: SDMMC, reason: 0x02, aux_info: 0x09
I> Busy Spin

Other devices do not have this issue , and all of them are using the same software image.
We are not using an SD card or eMMC in our system. The rootfs and other images are stored on NVMe . In this case, is the SDMMC-related error shown in the log associated with eMMC or SD card initialization?

Could you help analyze what might be causing the error shown in the boot log?

Thanks
uart.log (220.3 KB)

I’m using Jetpack6.0 on a custom board.

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I’ll analyze the issue and provide a comprehensive answer.

The error log you provided indicates that the boot process is getting stuck at a certain point, and the SDMMC-related error is shown. Since you mentioned that you’re not using an SD card or eMMC in your system, and the rootfs and other images are stored on NVMe, it’s likely that the error is not directly related to SD card or eMMC initialization.

However, it’s essential to understand the boot flow of the Jetson AGX Orin to determine the possible cause of the error. The Jetson AGX Orin boot flow consists of the following stages:

  1. BootROM: This is the first stage of the boot process, which is responsible for initializing the system and loading the next stage.
  2. PSCROM: This stage is responsible for configuring the system and loading the next stage.
  3. MB1: This stage is responsible for initializing the memory and loading the next stage.
  4. MB2: This stage consists of two parts: MB2 Applet and MB2. The MB2 Applet is responsible for loading the UEFI firmware, while the MB2 is responsible for loading the operating system.
  5. UEFI: This is the final stage of the boot process, which is responsible for loading the operating system and initializing the system.

Given that the error log shows an SDMMC-related error, it’s possible that the issue is related to the initialization of the SDMMC controller, which is used for SD card and eMMC interfaces. However, since you’re not using an SD card or eMMC, it’s likely that the error is related to the initialization of the SDMMC controller for other purposes, such as NVMe storage.

To further analyze the issue, I would recommend checking the following:

  1. Verify that the NVMe storage is properly configured and initialized.
  2. Check the UEFI settings to ensure that the SDMMC controller is properly configured.
  3. Review the boot log to see if there are any other errors or warnings that may indicate the cause of the issue.

In comparison to the Jetson Xavier NX and Jetson AGX Xavier boot flow, the Jetson AGX Orin boot flow is similar, but with some differences. The Jetson Xavier NX and Jetson AGX Xavier boot flow consists of the following stages:

  1. BootROM: This is the first stage of the boot process, which is responsible for initializing the system and loading the next stage.
  2. Bootloader Components: This stage consists of two parts: Common Driver Framework and Microboot1.
  3. TegraBoot: This stage consists of two parts: TegraBoot-BPMP and TegraBoot-CPU.
  4. UEFI: This is the final stage of the boot process, which is responsible for loading the operating system and initializing the system.

While the boot flow is similar, the Jetson AGX Orin has some additional stages, such as PSCROM and MB1, which are not present in the Jetson Xavier NX and Jetson AGX Xavier boot flow.

In summary, the SDMMC-related error in the boot log is likely not directly related to SD card or eMMC initialization, but rather to the initialization of the SDMMC controller for other purposes, such as NVMe storage. Further analysis is required to determine the root cause of the issue.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

please put the module on NV devkit and try with latest Jetpack release.

Hi WayneWWW,
The device can’t boot up when I try to flash the Images to emmc. I’m using below command

sudo ./flash.sh jetson-agx-orin-devkit internal

It got stuck at the same place

[0086.036] I> MB1 (version: 1.4.0.2-t234-54845784-08a4de08)
[0086.041] I> t234-A01-1-Silicon (0x12347) Prod
[0086.045] I> Boot-mode : Coldboot
[0086.048] I> Entry timestamp: 0x00000000
[0086.052] I> last_boot_error: 0x27228311
[0086.056] I> BR-BCT: preprod_dev_sign: 0
[0086.060] I> rst_source: 0xb, rst_level: 0x1
[0086.064] I> Task: SE error check
[0086.067] I> Task: Bootchain select WAR set
[0086.071] I> Task: Enable SLCG
[0086.074] I> Task: CRC check
[0086.077] I> Task: Initialize MB2 params
[0086.081] I> MB2-params @ 0x40060000
[0086.084] I> Task: Crypto init
[0086.087] I> Task: Perform MB1 KAT tests
[0086.091] I> Task: NVRNG health check
[0086.095] I> NVRNG: Health check success
[0086.098] I> Task: MSS Bandwidth limiter settings for iGPU clients
[0086.104] I> Task: Enabling and initialization of Bandwidth limiter
[0086.111] I> No request to configure MBWT settings for any PC!
[0086.116] I> Task: Secure debug controls
[0086.120] I> Task: strap war set
[0086.123] I> Task: Initialize SOC Therm
[0086.127] I> Task: Program NV master stream id
[0086.131] I> Task: Verify boot mode
[0086.137] I> Task: Alias fuses
[0086.140] W> FUSE_ALIAS: Fuse alias on production fused part is not supported.
[0086.147] I> Task: Print SKU type
[0086.150] I> FUSE_OPT_CCPLEX_CLUSTER_DISABLE = 0x00000000
[0086.156] I> FUSE_OPT_GPC_DISABLE = 0x00000000
[0086.160] I> FUSE_OPT_TPC_DISABLE = 0x00000000
[0086.164] I> FUSE_OPT_DLA_DISABLE = 0x00000000
[0086.169] I> FUSE_OPT_PVA_DISABLE = 0x00000000
[0086.173] I> FUSE_OPT_NVENC_DISABLE = 0x00000000
[0086.177] I> FUSE_OPT_NVDEC_DISABLE = 0x00000000
[0086.182] I> FUSE_OPT_FSI_DISABLE = 0x00000000
[0086.186] I> FUSE_OPT_EMC_DISABLE = 0x00000000
[0086.190] I> FUSE_BOOTROM_PATCH_VERSION = 0x7
[0086.194] I> FUSE_PSCROM_PATCH_VERSION = 0x7
[0086.199] I> FUSE_OPT_ADC_CAL_FUSE_REV = 0x2
[0086.203] I> FUSE_SKU_INFO_0 = 0xd0
[0086.206] I> FUSE_OPT_SAMPLE_TYPE_0 = 0x3 PS
[0086.210] I> FUSE_PACKAGE_INFO_0 = 0x2
[0086.214] I> SKU: Prod
[0086.216] I> Task: Boost clocks
[0086.219] I> Initializing NAFLL for BPMP_CPU_NIC.
[0086.224] I> BPMP NAFLL: fll_lock = 1, dvco_min_reached = 0
[0086.229] I> BPMP NAFLL lock success.
[0086.233] I> BPMP_CPU_NIC : src = 42, divisor = 0
[0086.238] I> Initializing PLLC2 for AXI_CBB.
[0086.242] I> AXI_CBB : src = 35, divisor = 0
[0086.246] I> Task: Voltage monitor
[0086.249] I> VMON: Vmon re-calibration and fine tuning done
[0086.255] I> Task: UPHY init
[0086.259] I> HSIO UPHY init done
[0086.263] W> Skipping GBE UPHY config
[0086.266] I> Task: Boot device init
[0086.269] I> Boot_device: RCM
[0086.272] I> USB configuration success
[0086.730] I> Task: TSC init
[0086.733] I> Task: Load membct
[0086.736] I> RAM_CODE 0x4000431
[0086.739] I> Loading MEMBCT
[0086.741] I> Slot: 1
[0086.743] I> Binary[0] block-0 (partition size: 0x40000)
[0086.749] I> Binary name: MEM-BCT-0
[0086.752] I> Size of crypto header is 8192
[0086.756] I> Size of crypto header is 8192
[0086.760] I> BCH of MEM-BCT-0 read from storage
[0086.764] I> BCH address is : 0x40050000
[0086.768] I> MEM-BCT-0 header integrity check is success
[0086.773] I> Binary magic in BCH component 0 is MEM0
[0086.778] I> component binary type is 0
[0086.784] I> MEM-BCT-0 binary is read from storage
[0086.789] I> MEM-BCT-0 binary integrity check is success
[0086.794] I> Binary MEM-BCT-0 loaded successfully at 0x40040000 (0xe580)
[0086.801] I> RAM_CODE 0x4000431
[0086.806] I> RAM_CODE 0x4000431
[0086.810] I> Task: Load Page retirement list
[0086.815] I> Task: SDRAM params override
[0086.818] I> Task: Save mem-bct info
[0086.822] I> Task: Carveout allocate
[0086.825] I> Update CCPLEX IST carveout from MB1-BCT
[0086.830] I> ECC region[0]: Start:0x0, End:0x0
[0086.834] I> ECC region[1]: Start:0x0, End:0x0
[0086.839] I> ECC region[2]: Start:0x0, End:0x0
[0086.843] I> ECC region[3]: Start:0x0, End:0x0
[0086.847] I> ECC region[4]: Start:0x0, End:0x0
[0086.851] I> Non-ECC region[0]: Start:0x80000000, End:0x1080000000
[0086.857] I> Non-ECC region[1]: Start:0x0, End:0x0
[0086.862] I> Non-ECC region[2]: Start:0x0, End:0x0
[0086.867] I> Non-ECC region[3]: Start:0x0, End:0x0
[0086.871] I> Non-ECC region[4]: Start:0x0, End:0x0
[0086.882] I> allocated(CO:44) base:0x1049800000 size:0x36800000 align: 0x100000
[0086.889] I> allocated(CO:31) base:0x1040000000 size:0x8000000 align: 0x8000000
[0086.896] I> allocated(CO:43) base:0x103c000000 size:0x4000000 align: 0x200000
[0086.904] I> allocated(CO:39) base:0x1039e00000 size:0x2200000 align: 0x10000
[0086.911] I> allocated(CO:20) base:0x1036000000 size:0x2000000 align: 0x2000000
[0086.918] I> allocated(CO:24) base:0x1034000000 size:0x2000000 align: 0x2000000
[0086.925] I> allocated(CO:28) base:0x1032000000 size:0x2000000 align: 0x2000000
[0086.932] I> allocated(CO:29) base:0x1030000000 size:0x2000000 align: 0x2000000
[0086.940] I> allocated(CO:22) base:0x1048000000 size:0x1000000 align: 0x1000000
[0086.947] I> allocated(CO:35) base:0x1038e00000 size:0x1000000 align: 0x100000
[0086.954] I> allocated(CO:41) base:0x102f000000 size:0x1000000 align: 0x100000
[0086.961] I> allocated(CO:02) base:0x1049000000 size:0x800000 align: 0x800000
[0086.968] I> allocated(CO:03) base:0x1038000000 size:0x800000 align: 0x800000
[0086.975] I> allocated(CO:06) base:0x102e800000 size:0x800000 align: 0x800000
[0086.982] I> allocated(CO:56) base:0x102e000000 size:0x800000 align: 0x200000
[0086.989] I> allocated(CO:07) base:0x1038800000 size:0x400000 align: 0x400000
[0086.996] I> allocated(CO:33) base:0x102dc00000 size:0x400000 align: 0x200000
[0087.003] I> allocated(CO:19) base:0x102d980000 size:0x280000 align: 0x10000
[0087.010] I> allocated(CO:23) base:0x1038c00000 size:0x200000 align: 0x200000
[0087.017] I> allocated(CO:01) base:0x102d800000 size:0x100000 align: 0x100000
[0087.024] I> allocated(CO:05) base:0x102d700000 size:0x100000 align: 0x100000
[0087.031] I> allocated(CO:08) base:0x102d600000 size:0x100000 align: 0x100000
[0087.038] I> allocated(CO:09) base:0x102d500000 size:0x100000 align: 0x100000
[0087.045] I> allocated(CO:12) base:0x102d400000 size:0x100000 align: 0x100000
[0087.052] I> allocated(CO:15) base:0x102d300000 size:0x100000 align: 0x100000
[0087.059] I> allocated(CO:17) base:0x102d200000 size:0x100000 align: 0x100000
[0087.066] I> allocated(CO:27) base:0x102d100000 size:0x100000 align: 0x100000
[0087.073] I> allocated(CO:42) base:0x102d000000 size:0x100000 align: 0x100000
[0087.081] I> allocated(CO:54) base:0x102d900000 size:0x80000 align: 0x80000
[0087.087] I> allocated(CO:34) base:0x102cff0000 size:0x10000 align: 0x10000
[0087.094] I> allocated(CO:72) base:0x102cdf0000 size:0x200000 align: 0x10000
[0087.101] I> allocated(CO:46) base:0x1000000000 size:0x20000000 align: 0x20000000
[0087.109] I> allocated(CO:47) base:0x102c800000 size:0x400000 align: 0x200000
[0087.116] I> allocated(CO:50) base:0x102c600000 size:0x200000 align: 0x100000
[0087.123] I> allocated(CO:52) base:0x102cdc0000 size:0x30000 align: 0x10000
[0087.129] I> allocated(CO:48) base:0x102cda0000 size:0x20000 align: 0x10000
[0087.136] I> allocated(CO:69) base:0x102cd80000 size:0x20000 align: 0x10000
[0087.143] I> allocated(CO:49) base:0x102cd70000 size:0x10000 align: 0x10000
[0087.150] I> NSDRAM base: 0x80000000, end: 0x102cdf0000, size: 0xfacdf0000
[0087.157] I> Task: Thermal check
[0087.160] I> Using min_chip_limit as min_tmon_limit
[0087.165] I> Using max_chip_limit as max_tmon_limit
[0087.169] I> BCT max_tmon_limit = 105
[0087.173] I> BCT min_tmon_limit = -28
[0087.176] I> BCT max_tmon_limit = 105
[0087.180] I> BCT min_tmon_limit = -28
[0087.183] I> SKU specific max_chip_limit = 105
[0087.188] I> SKU specific min_chip_limit = -28
[0087.192] I> BCT max_chip_limit = 105
[0087.195] I> BCT min_chip_limit = -28
[0087.199] I> enable_soctherm_polling = 0
[0087.203] I> max temp read = 36
[0087.206] I> min temp read = 36
[0087.209] I> Enabling thermtrip
[0087.212] I> Task: Update FSI SCR with thermal fuse data
[0087.217] I> Task: Enable WDT 5th expiry
[0087.221] I> Task: I2C register
[0087.224] I> Task: Set I2C bus freq
[0087.227] I> Task: Reset FSI
[0087.230] I> Task: Pinmux init
[0087.233] I> Task: Prod config init
[0087.236] I> Task: Pad voltage init
[0087.240] I> Task: Prod init
[0087.243] I> Task: Program rst req config reg
[0087.247] I> Task: Common rail init
[0087.250] I> DONE: Thermal config
[0087.254] W> DEVICE_PROD: module = 13, instance = 4 not found in device prod.
[0087.263] I> DONE: SOC rail config
[0087.267] W> PMIC_CONFIG: Rail: MEMIO rail config not found in MB1 BCT.
[0087.273] I> DONE: MEMIO rail config
[0087.276] I> DONE: GPU rail info
[0087.280] I> DONE: CV rail info
[0087.283] I> Task: Mem clock src
[0087.286] I> Task: Misc. board config
[0087.290] I> PMIC_CONFIG: Platform config not found in MB1 BCT.
[0087.296] I> Task: SDRAM init
[0087.299] I> MemoryType: 4 MemBctRevision: 8
[0087.306] I> MSS CAR: PLLM/HUB programming for MemoryType: 4 and MemBctRevision: 8
[0087.313] I> MSS CAR: Init PLLM
[0087.316] I> MSS CAR: Init PLLHUB
[0087.321] I> Encryption:   MTS: en, TX: en, VPR: en, GSC: en
[0087.333] I> SDRAM initialized!
[0087.336] I> SDRAM Size in Total 0x1000000000
[0087.340] I> Task: Dram Ecc scrub
[0087.343] I> Task: DRAM alias check
[0087.359] I> Task: Program NSDRAM carveout
[0087.363] I> NSDRAM carveout encryption is enabled
[0087.368] I> Program NSDRAM carveout
[0087.372] I> Task: Register checker
[0087.375] I> Task: Enable clock-mon
[0087.389] I> FMON: Fmon re-programming done
[0087.393] I> Task: Mapper init
[0087.396] I> Task: SC7 Context Init
[0087.400] W> SC7_CONTEXT_SAVE: SC7 ctx save is not supported.
[0087.405] I> Task: CCPLEX IST init
[0087.408] I> Task: CPU WP0
[0087.412] I> Loading MCE
[0087.414] I> Slot: 1
[0087.416] I> Binary[8] block-134217728 (partition size: 0x80000)
[0087.422] I> Binary name: MCE
[0087.425] I> Size of crypto header is 8192
[0087.429] I> Size of crypto header is 8192
[0088.143] I> BCH of MCE read from storage
[0088.147] I> BCH address is : 0x4003e000
[0088.151] I> MCE header integrity check is success
[0088.156] I> Binary magic in BCH component 0 is MTSM
[0088.161] I> component binary type is 8
[0088.164] I> Size of crypto header is 8192
[0088.171] I> MCE binary is read from storage
[0088.176] I> MCE binary integrity check is success
[0088.181] I> Binary MCE loaded successfully at 0x40000000 (0x2baf0)
[0088.187] I> Size of crypto header is 8192
[0088.191] I> Sending WP0 mailbox command to PSC
[0088.200] I> Task: XUSB Powergate
[0088.203] I> Skipping powergate XUSB.
[0088.207] I> Task: MB1 fixed firewalls
[0088.213] W> Firewall readback mismatch
[0088.218] I> Task: Load bpmp-fw
[0088.221] I> Slot: 1
[0088.223] I> Binary[15] block-251658240 (partition size: 0x180000)
[0088.229] I> Binary name: BPMP_FW
[0088.232] I> Size of crypto header is 8192
[0088.236] I> Size of crypto header is 8192
[0088.240] I> BCH of BPMP_FW read from storage
[0088.244] I> BCH address is : 0x807fe000
[0088.248] I> BPMP_FW header integrity check is success
[0088.253] I> Binary magic in BCH component 0 is BPMF
[0088.258] I> component binary type is 15
[0088.262] I> Size of crypto header is 8192
[0088.283] I> BPMP_FW binary is read from storage
[0088.290] I> BPMP_FW binary integrity check is success
[0088.295] I> Binary BPMP_FW loaded successfully at 0x80000000 (0xf8bc0)
[0088.301] I> Slot: 1
[0088.303] I> Binary[16] block-268435456 (partition size: 0x400000)
[0088.309] I> Binary name: BPMP_FW_DTB
[0088.313] I> Size of crypto header is 8192
[0088.317] I> Size of crypto header is 8192
[0088.321] I> BCH of BPMP_FW_DTB read from storage
[0088.325] I> BCH address is : 0x807fc000
[0088.329] I> BPMP_FW_DTB header integrity check is success
[0088.335] I> Binary magic in BCH component 0 is BPMD
[0088.339] I> component binary type is 16
[0088.343] I> Size of crypto header is 8192
[0088.351] I> BPMP_FW_DTB binary is read from storage
[0088.357] I> BPMP_FW_DTB binary integrity check is success
[0088.362] I> Binary BPMP_FW_DTB loaded successfully at 0x807bd4f0 (0x3eb00)
[0088.369] I> Task: BPMP fw ast config
[0088.373] I> Task: Load psc-fw
[0088.375] I> Slot: 1
[0088.378] I> Binary[17] block-285212672 (partition size: 0xc0000)
[0088.383] I> Binary name: PSC_FW
[0088.387] I> Size of crypto header is 8192
[0088.390] I> Size of crypto header is 8192
[0088.395] I> BCH of PSC_FW read from storage
[0088.399] I> BCH address is : 0x80ffe000
[0088.403] I> PSC_FW header integrity check is success
[0088.407] I> Binary magic in BCH component 0 is PFWP
[0088.412] I> component binary type is 17
[0088.416] I> Size of crypto header is 8192
[0088.425] I> PSC_FW binary is read from storage
[0088.430] I> PSC_FW binary integrity check is success
[0088.435] I> Binary PSC_FW loaded successfully at 0x80fb4210 (0x49df0)
[0088.441] I> Task: Load nvdec-fw
[0088.445] I> Slot: 1
[0088.447] I> Binary[7] block-117440512 (partition size: 0x100000)
[0088.453] I> Binary name: NVDEC
[0088.456] I> Size of crypto header is 8192
[0088.459] I> Size of crypto header is 8192
[0088.464] I> BCH of NVDEC read from storage
[0088.468] I> BCH address is : 0x800fe000
[0088.471] I> NVDEC header integrity check is success
[0088.476] I> Binary magic in BCH component 0 is NDEC
[0088.481] I> component binary type is 7
[0088.485] I> Size of crypto header is 8192
[0088.494] I> NVDEC binary is read from storage
[0088.499] I> NVDEC binary integrity check is success
[0088.503] I> Binary NVDEC loaded successfully at 0x80000000 (0x46000)
[0088.512] I> Task: Load tsec-fw
[0088.515] I> TSEC-FW load support not enabled
[0088.519] I> Task: GPIO interrupt map
[0088.523] I> Task: SC7 context save
[0088.527] W> SC7_CONTEXT_SAVE: SC7 ctx save is not supported.
[0088.533] I> Task: Load MB2/Applet/FSKP
[0088.536] I> Loading MB2
[0088.539] I> Slot: 1
[0088.541] I> Binary[6] block-100663296 (partition size: 0x80000)
[0088.547] I> Binary name: MB2
[0088.549] I> Size of crypto header is 8192
[0088.553] I> Size of crypto header is 8192
[0088.557] I> BCH of MB2 read from storage
[0088.561] I> BCH address is : 0x8007e000
[0088.565] I> MB2 header integrity check is success
[0088.570] I> Binary magic in BCH component 0 is MB2B
[0088.575] I> component binary type is 6
[0088.578] I> Size of crypto header is 8192
[0088.590] I> MB2 binary is read from storage
[0088.595] I> MB2 binary integrity check is success
[0088.599] I> Binary MB2 loaded successfully at 0x80000000 (0x696a0)
[0088.605] I> Task: Map CCPLEX SHARED carveout
[0088.610] I> Task: Prepare MB2 params
[0088.613] I> Task: Dram ecc test
[0088.617] I> Task: Misc NV security settings
[0088.621] I> NVDEC sticky bits programming done
[0088.625] I> Successfully powergated NVDEC
[0088.629] I> Task: Disable/Reload WDT
[0088.633] I> Task: Program misc carveouts
[0088.636] I> Program IPC carveouts
[0088.640] I> Task: Disable SCPM/POD reset
[0088.644] I> SLCG Global override status := 0x0
[0088.648] I> MB1: MSS reconfig completed
I> MB2 (version: 0.0.0.0-t234-54845784-af79ed0a)
I> t234-A01-1-Silicon (0x12347)
I> Boot-mode : RCM Flash
I> Emulation:
I> Entry timestamp: 0x05491463
I> Regular heap: [base:0x40040000, size:0x10000]
I> DMA heap: [base:0x102e000000, size:0x800000]
I> Task: SE error check
I> Task: MB2 Params integrity check
I> Task: Enable CCPLEX WDT 5th expiry
I> Task: ARI update carveout TZDRAM
I> Task: Configure OEM set LA/PTSA values
I> Task: Check MC errors
I> Task: PSC mailbox init
I> Task: Map CCPLEX_INTERWORLD_SHMEM carveout
I> Task: Program CBB PCIE AMAP regions
I> Task: Boot device init
I> Boot_device: QSPI_FLASH instance: 0
I> Qspi clock source : pllc_out0
I> QSPI Flash: Macronix 64MB
I> QSPI-0l initialized successfully
I> Secondary storage device: QSPI_FLASH instance: 0
**I> Secondary storage device: SDMMC_USER instance: 3**
**C> Task 0x0 failed (err: 0x39390902)**
**E> Top caller module: SDMMC, error module: SDMMC, reason: 0x02, aux_info: 0x09**
**I> Busy Spin**

then please do RMA for these boards.

I compared Jetson Linux 36.3 and 36.4.4. When flashing the eMMC:

Using the 36.3 BSP environment, the flashing fails, and the serial console gets stuck at the following point, showing a busy spin error.
Using 36.4.4, the flashing succeeds, and no busy spin error is reported.
Due to certain constraints, we are currently unable to upgrade the JetPack version.

Is there any patch or workaround available that can be applied to Jetson Linux 36.3 to resolve this issue?

If this is related to a software fix, then there won’t be any patch for you because the problem that this issue happened might be in the MB1 which is non open source software.

I replaced mb2_t234.bin in R36.3 with the mb2_t234.bin from R36.4.4, and the issue no longer reproduces.
May I only replace mb2_t234.bin from R36.4.4 into R36.3?
Will there be any compatibility/matching issues, and are there any other potential risks?

Thanks

Yes, there could be potential risks which we don’t know as this case is not tested (replacing a MB2 binary from another version)

Given the current situation, we are unable to upgrade the entire system to 36.4.4. If we only upgrade mb2 individually, do any other related images also need to be upgraded together, such as mb2rf_t234.bin?

Hello WayneWWW,

Could you please help me answer this question?

thanks

I would suggest you upgrade mb1/mb2 and sc7 binary altogether.

Sure, could you tell me the name of these binaries and the location?
thanks

Check the bin files under your Linux_for_Tegra/bootloader. should be files with mb1/mb2/sc7 prefix.

Replaced the following binaries with versions from R36.4.4, Is this change OK?

mb1_t234_prod.bin
mb1_t194_prod.bin 
mb2_t234.bin 
mb2rf_t234.bin 
sc7_t234_prod.bin

mb1_t234_prod.bin
mb2_t234.bin
mb2rf_t234.bin
sc7_t234_prod.bin

These 4 should be sufficient because t194 is for Xavier.

Sure, thanks. I will replace them and test it.

1 Like

After replacing these files, a power on/off stress test encountered a startup error once. The log is shown below.

MmInstallProtocolInterface: 24E70042-D5C5-4260-8C39-0AD3AA32E93D 0
▒▒





  Jetson System firmware version root-e539387f8-dirty date 2026-01-26T11:58:51+00:
00
ESC   to enter Setup.
F11   to enter Boot Manager Menu.
Enter to continue boot.
......▒▒MmInstallProtocolInterface: 7CE88FB3-4BD7-4679-87A8-A8D8DEE50D2B 0
ERROR:   **************************************
ERROR:   RAS Uncorrectable Error in SNOC, base=0xe011000:
ERROR:          Status = 0xe400030d
ERROR:   SERR = Illegal address (software fault): 0xd
ERROR:          IERR = Carveout Uncorrectable Error: 0x3
ERROR:          MISC0 = 0x2200
ERROR:          MISC1 = 0x41842000000000
ERROR:          MISC2 = 0x0
ERROR:          MISC3 = 0x20
ERROR:          ADDR = 0x8000000472f8d6c0
ERROR:   **************************************
ERROR:   sdei_dispatch_event returned -1
ERROR:   **************************************
ERROR:   RAS Uncorrectable Error in ACI, base=0xe01a000:
ERROR:          Status = 0xe8000904
ERROR:   SERR = Assertion failure: 0x4
ERROR:          IERR = FillWrite Error: 0x9
ERROR:          Overflow (there may be more errors) - Uncorrectable
ERROR:          ADDR = 0x8000000472f8d6c0
ERROR:   **************************************
ERROR:   sdei_dispatch_event returned -1
ERROR:   Powering off core

Could this issue be caused by the image replacement, or did the problem already exist before?
Thanks
bootfail.txt (41.4 KB)

as we already mentioned that this is not a guaranteed method to apply software, suggest to do the full upgrade.