How to Clear the Data on eMMC


Is it possible to clear all the data on eMMC?
We need to recover our SOMs back to shipment state.
If anyone knows how to do it, please let us know.

hello marble_hong,

please check the image flashing logs, it’ll erase the target in the beginning of flash process.

Hi JerryChang,

Thank you for your help. I upload a flash log.
flash_sh.log (71.5 KB)
Could you help point out which line does the erasing eMMC storage work?

here it is…

[  44.5504 ] Erasing spi: 0 ......... [Done]
[ 303.6801 ] Erasing sdmmc_user: 3 ......... [Done]

Hi JerryChang,

We are trying to use tegraflash command to do the erasing work.
By using the following command, we got the following “Boot Rom communication failed” error.
Could you help advise?

~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader (master) $ sudo ./ --bl nvtboot_recovery_cpu.bin --sdram_config tegra186-mb1-bct-memcfg-p3636-0001-a01.cfg --odmdata 0x2090000 --applet mb1_recovery_prod.bin  --cmd "erase APP"  --cfg flash.xml --chip 0x18
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[   0.0096 ] Generating RCM messages
[   0.0121 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 0 --download rcm mb1_recovery_prod.bin 0 0
[   0.0134 ] RCM 0 is saved as rcm_0.rcm
[   0.0139 ] RCM 1 is saved as rcm_1.rcm
[   0.0140 ] List of rcm files are saved in rcm_list.xml
[   0.0140 ] 
[   0.0140 ] Signing RCM messages
[   0.0166 ] --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0167 ] Assuming zero filled SBK key
[   0.0248 ] Copying signature to RCM mesages
[   0.0272 ] tegrarcm_v2 --chip 0x18 0 --updatesig rcm_list_signed.xml
[   0.0287 ] 
[   0.0287 ] Boot Rom communication
[   0.0309 ] tegrarcm_v2 --chip 0x18 0 --rcm rcm_list_signed.xml
[   0.0319 ] BR_CID: 0x88021911647076c21400000012038180
[   0.0343 ] Boot Rom communication failed
[   5.1338 ] 
Error: Return value 8
Command tegrarcm_v2 --chip 0x18 0 --rcm rcm_list_signed.xml

hello marble_hong,

this is device communication issue, during the flashing process, it will connect/disconnect the device for several times.
if you’re using VM, this usually USB port forward issue.
if you’re using a Laptop, please have the power-supply connected or you might test with other USB ports.

Hi JerryChang,

The following tegraflash command could be used to erase the APP partition.

sudo ./ --bl nvtboot_recovery_cpu_t194.bin  --chip 0x19 --applet mb1_t194_prod.bin --sdram_config tegra194-mb1-bct-memcfg-p3668-0001-a00.cfg,tegra194-memcfg-sw-override.cfg --device_confi    g tegra19x-mb1-bct-device-qspi-p3668.cfg --misc_cold_boot_config tegra194-mb1-bct-misc-l4t.cfg --misc_config tegra194-mb1-bct-misc-flash.cfg --pinmux_config tegra19x-mb1-pinmux-p3668-a01.cfg --gpioint    _config tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg --pmic_config tegra194-mb1-bct-pmic-p3668-0001-a00.cfg --pmc_config tegra19x-mb1-padvoltage-p3668-a01.cfg --prod_config tegra19x-mb1-prod-p3668-0001    -a00.cfg --scr_config tegra194-mb1-bct-scr-cbb-mini-p3668.cfg --scr_cold_boot_config tegra194-mb1-bct-scr-cbb-mini-p3668.cfg --br_cmd_config tegra194-mb1-bct-reset-p3668-0001-a00.cfg --dev_params tegr    a194-br-bct-qspi.cfg --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg  --cfg  flash.xml --bin "mb2_bootloader nvtboot_recovery_t194.bin; mts_preboot preboot_c10_prod_cr.bin; mts_mce mce_c10_prod_cr.bin; m    ts_proper mts_c10_prod_cr.bin; bpmp_fw bpmp_t194.bin; bpmp_fw_dtb tegra194-a02-bpmp-p3668-a00.dtb; spe_fw spe_t194.bin; tlk tos-trusty_t194.img; eks eks.img; bootloader_dtb tegra194-p3668-all-p3509-00    00.dtb"  --odmdata 0xB8190000  --cmd "erase APP"

You may close this thread. Thank you for your help.

1 Like

thanks for confirmation, issue closed.

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