Hey,
I’m having trouble flashing the Jetson AGX Orin 64GB SOM. I have 2 variants, 1 with a Kingston eMMC (part number: 170-0695-00X), and another variant with a WD/Sandisk eMMC (170-0637-30X) - everything else is the same. Kingston eMMC fails to flash with the following error, while the WD/Sandisk eMMC succeeds.
JetPack 7.2, R39.2
Kingston eMMC 170-0695-00X, TY2964
MB2 version: t234-54845784-5b8edbc4-01Jun26-131747-0700
Failure:
I> Secondary storage device: SDMMC_USER instance: 3
C> Task 0x18 failed (err: 0x39390902)
E> Top caller module: SDMMC, error module: SDMMC, reason: 0x02, aux_info: 0x09
WD/SanDisk eMMC 170-0637-30X, DG4064
Flashes Jetpack 7.2 successfully.
Are there any new MB2 binaries that I can try so I can get past this error?
Thanks
— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —
I could not find clear support for that in the provided Jetson AGX Orin documentation.
— We support team will also look into your issue to have further suggestions soon. please stay tuned. —
We encountered the same issue. Here are some more details:
flash.sh emmc paused at:
...
[ 4.5078 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[ 4.5093 ] Added binary blob_bpmp_t234-TE990M-A1_prod_sigheader.bin.encrypt of size 1027008
[ 4.5098 ] Added binary blob_tegra234-bpmp-3701-0005-3737-0000_with_odm_sigheader.dtb.encrypt of size 264768
[ 4.5102 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 699616
[ 4.5104 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 419952
[ 4.5106 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[ 4.5108 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1899072
[ 4.5116 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[ 4.5208 ] Sending membct and RCM blob
[ 4.5211 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 4.5213 ] BL: version 1.0.1.17-t234-54845784-9b0d5809 last_boot_error: 0
[ 4.5438 ] Sending bct_mem
[ 4.5439 ] Sending blob
[ 6.0987 ] completed
[ 6.0987 ] Retrieving storage infomation
[ 6.0993 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails storage storage_info.bin
UART console stops at:
[0134.199] I> MB1: MSS reconfig completed
I> MB2 (version: 0.0.0.0-t234-54845784-5b8edbc4-01Jun26-131747-0700)
I> t234-A01-1-Silicon (0x12347) Prod
I> Boot-mode : RCM Flash
I> Entry timestamp: 0x08001237
I> Regular heap: [base:0x40040000, size:0x10000]
I> DMA heap: [base:0x1027000000, size:0x800000]
I> Task: MB2 Params integrity check
I> Task: Enable CCPLEX WDT 5th expiry
I> Task: ARI update carveout TZDRAM
I> Task: Check MC errors
I> Task: SMMU external bypass disable
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 at index: 5
I> QSPI-0l initialized successfully
I> Secondary storage device: QSPI_FLASH instance: 0
I> Secondary storage device: SDMMC_USER instance: 3
C> Task 0x18 failed (err: 0x39390902)
E> Top caller module: SDMMC, error module: SDMMC, reason: 0x02, aux_info: 0x09
BTW, I was able to flash Jetpack 6.2 on this SOM. I then tried OTA upgrade from 6.2 to 7.2, which also works. At least this is the workaround until Nvidia fixes the mb2_t234.bin.
Could you flash this board with rel-36 first and give me result of
sudo cat /etc/nv_boot_control.conf
Also, attach the full text log instead of partial logs. I need your flash command as well.
Here’s the nv_boot_control conf file:
TNSPEC 3701-502-0005-K.0-1-0-auvidea-agx-orin-maxn-X410-
COMPATIBLE_SPEC 3701–0005–1–auvidea-agx-orin-maxn-X410-
TEGRA_BOOT_STORAGE mmcblk0
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
I have also attached the UART log. The flash command is standard:
sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
uart-log.txt (17.4 KB)
flash log:
flash.log (88.2 KB)
We have confirmed it is an issue with the Kingston eMMC specifically. The matrix is here:
- Jetpack 6 R36 works on SOM with Kingston eMMC
- Jetpack 6 R36 works on SOM with Micron/Sandisk/WD eMMC
- Jetpack 7.2 R39 works on SOM with Micron/Sandisk/WD eMMC
- Jetpack 7.2 R39 does NOT work on SOM with Kingston eMMC
@user100132 the OTA approach doesn’t really work - it just boots the older R36 version of MB2 because the R39 version fails, and boot fails over to the partition that contains the R36 version. This makes the R36 version of DCE firmware come up, which is incompatible with R39, which means we can’t talk to the GPU.
@svanshil Your nv_boot_control file shows it is also FAB 502, same as mine or others in this forum who experienced the same issue with Jetpack 5.2.
Regarding the workaround using OTA upgrade from Jetpack 6 to 7.2, we don’t use ROOTFS_AB, so it boots into the new Jetpack 7.2 filesystem which made me thinking we are fully upgraded after I login, but you are right maybe MB2 etc are still on the old I guess. The boot screen still says Jetson System firmware version 36.4.4-gcid-41062509. During the OTA upgrade and final boot, the UART console also gives: E> Top caller module: SDMMC, error module: SDMMC, reason: 0x02, aux_info: 0x09 but at least system boots up into the Jetpack 7.2 rootfs, and “uname -a” shows the new kernel
I checked the boot log from a working Orin (FAB 501) that runs Jetpack 7.2, and it says: t23x_general UEFI firmware (version 39.2.0-gcid-45755727
This indeed confirms my “workaround” doesn’t work fully, though rootfs, kernel and kernel_dtb partitions are properly upgraded to Jetpack 7.2.
Has https://auvidea.eu/firmware/ released anything for Jetpack7.2? Most recent I could find on auvidea.eu is Jetpack 7.1. I wonder if this is relevant? And the auvidea software-setup-guide advanced-flashing-guide Flashing the AGX Orin has some steps you may need to follow, including
In tegra234-mb2-bct-common.dtsi
Replace
cvb_eeprom_read_size = <0x100>
Replace with
cvb_eeprom_read_size = <0x0>
And; Usual File path:
/home/<YOUR_USERNAME>/nvidia/nvidia_sdk/JetPack_<Jetpack_version>_Linux_<Jetson_module>/Linux_for_Tegra/ p3701.conf.common
In p3701.conf.common
Set
ODMDATA="gbe-uphy-config-0,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-16"
Last updated 2 years ago
Yes @WayneWWW - i have already commented on the other issue, they appear to be the same eMMC issue.
@whitesscott this is not an auvidea issue, we have the same carrier board working with Jetpack 7.2 with non Kingston eMMCs. Please see AGX Jetson Orin SOM flashing failure in MB2 init - #6 by svanshil .
We notice that some patches to support Kingston eMMC are missing on JP7 so that some SOM would be affected.
There is a plan to added it in JetPack 7.2.1, that is expected to be released by end of July.
Is this schedule okay for you?
@WayneWWW thanks for the update. Would it be possible at all to have any MB2 binary only (even for testing) before end of July?
We would also prefer to have the MB2 binary for the current Jetpack 7.2, like what Nvidia is already doing for other l4t releases, eg: you can see “Additional Files” section at the bottom of R36 BSP Download Page
we are still working on this.
The patch is ready. Please refer to
Thanks @WayneWWW , this seems to fix the issue on Kingston eMMCs
It works for me too, thanks!