Thank you for the link to the PCN; this is helpful. Can you provide the part number of the original eMMC chip? We would like to compare the datasheets for the old part and the new Western Digital SDINBDG4-32G-1212 part to see if there are any changes that would affect temperature or wearout reliability.
Could we firstly confirm your module can get flashed with new BSP? Is that working?
I will put the module back onto the devkit and try flashing again on Monday. I’ll use Jetpack 4.6.2 and capture the debug logs.
In the meantime, we are going to cut open two of the Xavier modules and compare the flash ICs. We have an old 16GB module (presumably with the old eMMC chip) and we have 3 failed 32GB modules. We are going to open one of the failed 32GB modules to see if it has the new eMMC chip.
Does Nvidia do date/lot code tracking on the eMMC chips? If we provide a list of serial numbers, can you tell us which modules have the new eMMC ICs?
Hi,
There is one mistake here that the problem is not from new eMMC. But the new DRAM.
We do track every module so if you provide serial number of each jetson module, we can tell you whether it has PCN update or not. But this query may take time since we need to contact with factory.
I have 3 serial numbers documented now, and I’ll work on getting the remainder:
- 1421222062525, failed to flash after test
- 1421222062535, failed to flash after test
- 1421222062521, was able to re-flash and recover
I tried flashing the failed module using Jetpack4.6.2, but I got the same failure. Here are the UART logs:
(prd-version: 1.5.1.9-t194-41334769-73a9b7ef)
[0005.243] I> Boot-mode: Platform RCM
[0005.246] I> Chip revision : A02P
[0005.249] I> Bootrom patch version : 15 (correctly patched)
[0005.254] I> ATE fuse revision : 0x200
[0005.258] I> Ram repair fuse : 0x0
[0005.261] I> Ram Code : 0x2
[0005.264] I> rst_source : 0x0
[0005.266] I> rst_level : 0x0
[0005.270] I> USB configuration success
[0007.333] I> mb2 image downloaded
[0007.346] I> Recovery boot mode 0
[0007.350] I> Boot-device: eMMC
[0007.354] I> UPHY full init done
[0007.361] I> MB1 done
[0007.366] W> Profiler not initialized
[0007.369] I> Welcome to MB2(TBoot-BPMP) Applet (version: 00.00.2018.32-mobile-ca3b3e95)
[0007.377] W> Profiler not initialized
[0007.381] I> DMA Heap @ [0x40020000 - 0x40065800]
[0007.385] I> Default Heap @ [0xd486400 - 0xd48a400]
[0007.390] W> Profiler not initialized
[0007.394] W> Profiler not initialized
[0007.397] E> DEVICE_PROD: Invalid value data = 0, size = 0.
[0007.402] W> device prod register failed
[0007.406] W> Profiler not initialized
[0007.628] I> sdmmc DDR50 mode
[0007.632] I> No supported QSPI flash found
[0007.636] E> QSPI Flash: Insufficient flash size (0 MB)
[0007.641] I> QSPI Flash is not present.
[0007.693] E> Link startup dme_set failed
[0007.696] E> UFS initialization failed
[0007.700] I> UFS is not present
[0007.703] W> Profiler not initialized
[0007.713] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[0007.720] W> Cannot find any partition table for 00010003
[0007.725] W> Profiler not initialized
[0007.729] W> Profiler not initialized
[0007.732] W> Profiler not initialized
[0007.736] I> Entering 3p server
[0007.739] I> USB configuration success
[0008.397] I> Populate chip info
[0008.411] I> Populate eeprom info
[0008.415] I> Populate eeprom info for module cvm
-41334769-73a9b7ef)
[0089.321] I> Boot-mode: RCM
[0089.324] I> Chip revision : A02P
[0089.327] I> Bootrom patch version : 15 (correctly patched)
[0089.332] I> ATE fuse revision : 0x200
[0089.335] I> Ram repair fuse : 0x0
[0089.338] I> Ram Code : 0x2
[0089.341] I> rst_source : 0xb
[0089.344] I> rst_level : 0x1
[0089.348] I> USB configuration success
[0091.322] I> bct_bootrom image downloaded
[0091.331] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0091.339] I> Temperature = 25000
[0091.342] W> Skipping boost for clk: BPMP_CPU_NIC
[0091.346] W> Skipping boost for clk: BPMP_APB
[0091.350] W> Skipping boost for clk: AXI_CBB
[0091.354] W> Skipping boost for clk: AON_CPU_NIC
[0091.358] W> Skipping boost for clk: CAN1
[0091.362] W> Skipping boost for clk: CAN2
Hi @user1111111
May I get confirmation of below info
-
You have 3 modules listed and 2 of them are failed to get flashed? or even the 3rd module failed to get flashed again?
-
Are you using NV devkit to test?
-
Is the result of (1) based on jp4.6.2?
-
Have you tested jp5.0.2 with devkit?
We are also checking the S/N you shared internally.
Hi WayneWWW,
-
We have 6 modules, 3 of which we were able to flash successfully and 3 of which failed to flash. I only wrote down the serial numbers for some of the modules, so that serial number list is incomplete.
-
Yes, I am now using the NV devkit to test the flashing; it is still failing to flash.
-
We originally used jetpack 4.3 for our testing, but I am now using jetpack 4.6.2 as requested. The logs I posted on October 9 are from jetpack 4.6.2.
-
We have not tried jetpack 5.0.2 with the devkit because that version of jetpack is not compatible with our software.
Thanks!
Hi @user1111111
Just want to clarify that this is not “this software is not compatible with my software so I don’t want to try”. This is the moment of RMA these modules or not.
Please try with jp5.0.2 on devkit. If the stuck point in flash is still the same, then please RMA those 3 modules.
I get the same failure with Jetpack5.0.2. See UART logs below.
[0055.916] I> Boot-mode: Platform RCM
[0055.919] I> Platform: Silicon
[0055.922] I> Chip revision : A02P
[0055.925] I> Bootrom patch version : 15 (correctly patched)
[0055.930] I> ATE fuse revision : 0x200
[0055.934] I> Ram repair fuse : 0x0
[0055.937] I> Ram Code : 0x2
[0055.940] I> rst_source: 0xb, rst_level: 0x1
[0055.945] I> USB configuration success
[0058.191] I> mb2 image downloaded
[0058.278] I> Recovery boot mode 0
[0058.284] I> UPHY full init done
[0058.291] I> MB1 done
[0058.296] I> Welcome to MB2(TBoot-BPMP) Applet (version: default.t194-mobile-27d8d121)
[0058.303] I> DMA Heap @ [0x40020000 - 0x40065800]
[0058.308] I> Default Heap @ [0xd486400 - 0xd48a400]
[0058.312] W> Profiler not initialized
[0058.337] I> sdmmc DDR50 mode
[0058.341] E> SPI_FLASH: Invalid value device id: 7.
[0058.346] I> QSPI Flash is not present.
[0058.352] E> CLK_RST: instance 6 not found in module 44.
[0058.357] E> MPhy CAR configuration failed error = 1747992077
[0058.363] E> UFS initialization failed
[0058.366] I> UFS is not present
[0058.374] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[0058.381] W> Cannot find any partition table for 00010003
[0058.387] > PARTITION_MANAGER: Failed to publish partition.
[0058.392] W> Profiler not initialized
[0058.395] I> Entering 3p server
[0058.398] I> USB configuration success
[0059.552] I> Populate chip info
[0059.636] I> Populate eeprom info
[0059.640] I> Populate eeprom info for module cvm
[0059.645] > DEVICE_PROD: device prod is not initialized.
[0059.861] I> Rebooting : reboot-recovery
ratchet level 2 from HW fuses.
[0103.560] I> MB1 (prd-version: 2.3.0.0-t194-41334769-0a17edc1)
[0103.566] I> Boot-mode: RCM
[0103.568] I> Platform: Silicon
[0103.571] I> Chip revision : A02P
[0103.574] I> Bootrom patch version : 15 (correctly patched)
[0103.579] I> ATE fuse revision : 0x200
[0103.583] I> Ram repair fuse : 0x0
[0103.586] I> Ram Code : 0x2
[0103.588] I> rst_source: 0xb, rst_level: 0x1
[0103.594] I> USB configuration success
[0105.716] I> bct_bootrom image downloaded
[0105.725] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0105.732] I> Temperature = 31500
[0105.736] W> Skipping boost for clk: BPMP_CPU_NIC
[0105.740] W> Skipping boost for clk: BPMP_APB
[0105.744] W> Skipping boost for clk: AXI_CBB
[0105.748] W> Skipping boost for clk: AON_CPU_NIC
[0105.752] W> Skipping boost for clk: CAN1
[0105.756] W> Skipping boost for clk: CAN2
ok. Please RMA those 3 modules which have problem.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.