Question about AGX Xavier broken eMMC

I have an AGX Xavier that I obtained a while ago from an acquaintance.

I was booting fine but neither of us had the login credentials anymore. I set it aside for a long time and now I’m trying to revive it and it will not boot. I figure a device with a GPU and 32GB of unified memory is going to be useful for quite a few things still these days.

It goes straight into DFU mode as seen via lsusb on an attached linux box.

When attempting to flash to eMMC I get

16:09:50 INFO: Flash Jetson Linux - flash: [ 17.9260 ] [...] 100%
16:09:50 INFO: Flash Jetson Linux - flash: [ 17.9275 ] 000000000d0d2c01: E> NV3P_SERVER: Failed to initialize partition table from GPT.

error, and upon doing some more research on these forums it’s apparent the eMMC probably died. Example: AGX Xavier error during flashing - #16 by stefan.sesser

I attempted to flash to NVMe after installing one, and I got a blinking cursor to show on HDMI off the device, but this flash also failed!

17:00:59 INFO: Flash Jetson Linux - flash: tar: Read checkpoint 540000
17:01:00 INFO: Flash Jetson Linux - flash: tar: Read checkpoint 550000
17:01:07 INFO: Flash Jetson Linux - flash: writing item=16, 9:0:secondary_gpt, 61203267072, 16896, gpt_secondary_9_0.bin, 16896, fixed--0, d39dffceb0d95c536057ff095e2b8a0394c02d2f
17:01:07 INFO: Flash Jetson Linux - flash: [ 140]: l4t_flash_from_kernel: Failed to write to APP
17:01:07 INFO: Flash Jetson Linux - flash: Cleaning up...
17:01:07 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
17:01:07 ERROR: Flash Jetson Linux - flash: command terminated with error
17:01:07 SUMMARY: DateTime Target Setup - target: Depends on failed component

I wonder if I am likely to see success from poking around any further with the flash.sh script and whatnot. Does anyone know if this means there is some interaction required with eMMC even to boot NVMe and i’ve got a bricked device?

At this point resetting the device has it boot up in DFU mode again.

How would I go about RMAing this device?

I got a response from Customer Care regarding RMA for this device. They said that the warranty for the device is out because it was manuf. in 2018 and it’s now well beyond the 1 year warranty duration.

This is understandable but it leaves me holding the bag on it since I also can’t in good conscience sell it off on ebay without making it clear that it’s basically for parts. Like… there’s a perfectly good GPU on this thing… I’d like to get it functioning again somehow so I can run some LLMs on it! Even if I have to ship it to Louis Rossman and have him replace the eMMC or something :D

Questions:

Assuming that it is the eMMC that is faulty,

I know that Xavier NX (prod SoM) can boot “directly” from NVMe. Supposedly by initializing their QSPI-NOR and not interacting with eMMC at all. But I do not know if the architecture for this Xavier AGX is different. I feel like it could well be.

Next, I will attempt the carolyuu approach as mentioned from here: How to Boot from USB Drive? - #51 by jhench to see if I can obtain functioning boot from USB.

Hi,

Before answering the question, I would suggest you to dump the uart log during flash and share both device side and host side (full) log for us to check…

Sure. Here is the serial log:

Welcome to minicom 2.7.1

OPTIONS: I18n
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyUSB3, 23:43:51

Press CTRL-A Z for help on special keys

�
 [0000.094] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 1 from HW fuses.
[0000.102] I> MB1 (prd-version: 2.3.0.0-t194-41334769-0a17edc1)
[0000.107] I> Boot-mode: Coldboot
[0000.110] I> Platform: Silicon
[0000.113] I> Chip revision : A02
[0000.116] I> Bootrom patch version : 7 (correctly patched)
[0000.121] I> ATE fuse revision : 0x200
[0000.125] I> Ram repair fuse : 0x0
[0000.128] I> Ram Code : 0x0
[0000.130] I> rst_source: 0x0, rst_level: 0x0
[0000.135] I> Boot-device: SDMMC (instance: 3)
[0000.151] I> sdmmc DDR50 mode
[0000.155] I> Boot chain mechanism: A/B
[0000.159] I> Current Boot-Chain Slot: 0
[0000.162] I> BR-BCT Boot-Chain: 0, status: 0. update flag: 0
[0000.169] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0000.176] I> Temperature = 27500
[0000.179] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.183] W> Skipping boost for clk: BPMP_APB
[0000.187] W> Skipping boost for clk: AXI_CBB
[0000.191] W> Skipping boost for clk: AON_CPU_NIC
[0000.196] W> Skipping boost for clk: CAN1
[0000.199] W> Skipping boost for clk: CAN2
[0000.204] I> Boot-device: SDMMC (instance: 3)
[0000.214] I> Sdmmc: HS400 mode enabled
[0000.219] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.226] W>  Thermal config not found in BCT
[0000.234] W>  MEMIO rail config not found in BCT
[0000.252] I> sdmmc bdev is already initialized
[0000.258] E> LOADER: Invalid value HeaderMagic.
[0000.263] C> LOADER: Could not read binary 6.
[0000.267] C> Task 0x5b failed (err: 0x1d1d0d02)
[0000.271] E> Top caller module: LOADER, error module: LOADER, reason: 0x02, aux_info: 0x0d
[0000.279] C> Error: 0x1d1d0d02
[0000.282] C> MB1(2.3.0.0-t194-41334769-0a17edc1) BIT boot status dump :
000000000011111111100100000000000111101111110111011111111111111111111100111111110010100111100000000000000000000000000000
�
 [0000.054] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 1 from HW fuses.
[0000.063] I> MB1 (prd-version: 2.3.0.0-t194-41334769-0a17edc1)
[0000.068] I> Boot-mode: Coldboot
[0000.071] I> Platform: Silicon
[0000.074] I> Chip revision : A02
[0000.077] I> Bootrom patch version : 7 (correctly patched)
[0000.082] I> ATE fuse revision : 0x200
[0000.085] I> Ram repair fuse : 0x0
[0000.088] I> Ram Code : 0x0
[0000.091] I> rst_source: 0xb, rst_level: 0x1
[0000.096] I> Boot-device: SDMMC (instance: 3)
[0000.112] I> sdmmc DDR50 mode
[0000.116] I> Boot chain mechanism: A/B
[0000.119] I> Current Boot-Chain Slot: 1
[0000.123] I> BR-BCT Boot-Chain: 0, status: 1. update flag: 1
[0000.130] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0000.136] I> Temperature = 27500
[0000.139] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.143] W> Skipping boost for clk: BPMP_APB
[0000.147] W> Skipping boost for clk: AXI_CBB
[0000.151] W> Skipping boost for clk: AON_CPU_NIC
[0000.155] W> Skipping boost for clk: CAN1
[0000.159] W> Skipping boost for clk: CAN2
[0000.163] I> Boot-device: SDMMC (instance: 3)
[0000.174] I> Sdmmc: HS400 mode enabled
[0000.179] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.185] W>  Thermal config not found in BCT
[0000.193] W>  MEMIO rail config not found in BCT
[0000.212] I> sdmmc bdev is already initialized
[0000.218] E> LOADER: Invalid value HeaderMagic.
[0000.222] C> LOADER: Could not read binary 6.
[0000.226] C> Task 0x5b failed (err: 0x1d1d0d02)
[0000.230] E> Top caller module: LOADER, error module: LOADER, reason: 0x02, aux_info: 0x0d
[0000.238] C> Error: 0x1d1d0d02
[0000.241] C> MB1(2.3.0.0-t194-41334769-0a17edc1) BIT boot status dump :
000000000011111111100100000000000111101111110111011111111111111111111100111111110010100111100000000000000000000000000000
�
 [0000.054] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 1 from HW fuses.
[0000.063] I> MB1 (prd-version: 2.3.0.0-t194-41334769-0a17edc1)
[0000.068] I> Boot-mode: Coldboot
[0000.071] I> Platform: Silicon
[0000.074] I> Chip revision : A02
[0000.077] I> Bootrom patch version : 7 (correctly patched)
[0000.082] I> ATE fuse revision : 0x200
[0000.085] I> Ram repair fuse : 0x0
[0000.088] I> Ram Code : 0x0
[0000.091] I> rst_source: 0xb, rst_level: 0x1
[0000.096] I> Boot-device: SDMMC (instance: 3)
[0000.112] I> sdmmc DDR50 mode
[0000.116] I> Boot chain mechanism: A/B
[0000.119] I> Current Boot-Chain Slot: 0
[0000.123] E> Error, current slot 0 fails: sr_bl: 0x4d14ef1, sr_br: 0x0
[0000.129] I> Reset to recovery mode

Also, in this topic: Cannot flash AGX Xavier I have attached my SDKM flashing logs.

Looking at this, it’s saying SDMMC, is it trying to boot SD card??

Hi,

You didn’t get it. I mean the uart log during the flash process.

You mean to have minicom set up like this while I proceed with SDKM flash?

I will attempt this now.

Hi,

I just checked some history and notice the problem here is your module is too old and is already got EOL.

Latest jetpack does not support this module(2888-0001-400) anymore.

You can only try some old jetpack like jp4.3/4.2 first.

OK thank you. that is good to know. i suspected it but it is not easy to confirm. I already downloaded the ubuntu 18.04 SDKM docker image and will use that in my 20.04 system to flash a jetpack 4.x. Do you know if 4.6 is supported though? Or I have to go even earlier?

I’m attempting a 4.6.4 emmc flash now, because 4.6.x is as early of a jetpack as the 18.04 SDKManager docker allows me to install. I’ll search around for older BSP package for trying to JP 4.3 with, if this fails, I suppose.

Still fails with the SDK Manager showing a familiar

┌─ Terminal Log ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│info: [  19.9222 ] Writing partition secondary_gpt with gpt_secondary_0_3.bin                                                                                                                              │
│info: [  19.9224 ] [...] 100%                                                                                                                                                                              │
│                                                                                                                                                                                                           │
│info: Get:32 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 gcc-aarch64-linux-gnu amd64 4:7.4.0-1ubuntu2.3 [1,396 B]                                                                           │
│info: Get:33 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 linux-libc-dev-arm64-cross all 4.15.0-35.38cross1.1 [859 kB]                                                                       │
│info: Get:34 file:/var/cuda-repo-cross-aarch64-ubuntu1804-10-2-local  libcusolver-cross-aarch64-10-2 10.3.0.300-1 [15.8 MB]                                                                                │
│info:                                                                                                                                                                                                      │
│info: Get:35 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libc6-dev-arm64-cross all 2.27-3ubuntu1cross1.1 [2,044 kB]                                                                         │
│info: Get:36 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libstdc++-7-dev-arm64-cross all 7.5.0-3ubuntu1~18.04cross1 [1,450 kB]                                                              │
│info: Get:37 file:/var/cuda-repo-cross-aarch64-ubuntu1804-10-2-local  libcusparse-cross-aarch64-10-2 10.3.1.300-1 [61.4 MB]                                                                                │
│info: Get:38 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 g++-7-aarch64-linux-gnu amd64 7.5.0-3ubuntu1~18.04cross1 [6,595 kB]                                                                │
│info: [  20.0298 ] Erasing sdmmc_user: 3 ... [Done]                                                                                                                                                        │
│info: [  20.5231 ] Writing partition master_boot_record with mbr_1_3.bin                                                                                                                                   │
│info: [  20.5233 ] [...] 100%                                                                                                                                                                              │
│info: [  20.5243 ] Writing partition primary_gpt with gpt_primary_1_3.bin                                                                                                                                  │
│info: [  20.5308 ] [...] 100%                                                                                                                                                                              │
│info: [  20.5323 ] 000000000d0d0001: o initialize partition table from GPT.                                                                                                                                │
│info: [  20.5460 ]                                                                                                                                                                                         │
│info: [  20.5460 ]                                                                                                                                                                                         │
│error: Error: Return value 1                                                                                                                                                                               │
│info: Command tegradevflash_v2 --pt flash.xml.bin --create                                                                                                                                                 │
│error: Failed flashing t186ref.                                                                                                                                                                            │
│error: *** ERROR: flashing failed.                                                                                                                                                                         │
│info: [ Component Install Finished with Error ]                                                                                                                                                            │
│info: [host] [ 15.86 GB used. Disk Avail: 27.84 GB ]                                                                                                                                                       │
│info: [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 2m12s ]                                                                                                                                        │
│info:                                                                                                                                                                                                      │
│error: command terminated with error                               

And the uart was showing


�ain enter
SPE VERSION #: R01.00.14 Created: Sep 19 2018 @ 11:03:21
HW Function test
Start Scheduler.
in late init
�[[0081.614] I> Welcome to MB2(TBoot-BPMP) Recovery (version: 00.00.2018.32-mobile-035a6dd2)
[0081.614] I> DMA Heap @ [0x526fa000 - 0x52ffa000]
[0081.615] I> Default Heap @ [0xd486400 - 0xd48a400]
[0081.617] I> parsing oem signed section of bpmp-fw header done
[0081.625] I> bpmp-fw binary copied from blob
[0081.626] I> oem authentication of bpmp-fw header done
[0081.631] I> bpmp-fw: Authentication init Done
[0081.635] I> parsing oem signed section of cpubl header done
[0081.642] I> cpubl binary copied from blob
[0081.645] I> bpmp-fw: Authentication Finalize Done
[0081.650] I> oem authentication of cpubl header done
[0081.654] I> cpubl: Authentication init Done
[0081.658] I> parsing oem signed section of tos header done
[0081.665] I> tos binary copied from blob
[0081.668] I> Relocating BR-BCT
[0081.671] I> cpubl: Authentication Finalize Done
[0081.675] I> oem authentication of tos header done
[0081.679] I> tos: Authentication init Done
[0081.683] I> parsing oem signed section of bpmp-fw-dtb header done
[0081.690] I> bpmp-fw-dtb binary copied from blob
[0081.694] I> tos: Authentication Finalize Done
[0081.700] I> oem authentication of bpmp-fw-dtb header done
[0081.703] I> bpmp-fw-dtb: Authentication init Done
[0081.708] I> parsing oem signed section of cpubl-dtb header done
[0081.715] I> cpubl-dtb binary copied from blob
[0081.718] I> bpmp-fw-dtb: Authentication Finalize Done
[0081.723] I> found decompressor handler: lz4
[0082.090] I> oem authentication of cpubl-dtb header done
[0082.091] I> cpubl-dtb: Authentication init Done
[0082.091] I> parsing oem signed section of eks header done
[0082.092] I> eks binary copied from blob
[0082.093] I> cpubl-dtb: Authentication Finalize Done
[0082.093] I> oem authentication of eks header done
[0082.094] I> eks: Authentication init Done
[0082.097] I> eks: Authentication Finalize Done
[0082.102] I> EKB detected (length: 0x410) @ VA:0x526fb600
�OTICE:  BL31: v1.3(release):f9bf1e1
NOTICE:  BL31: Built : 21:07:06, Jun  8 2023
ipc-unittest-main: 1519: Welcome to IPC unittest!!!
ipc-unittest-main: 1531: waiting forever
ipc-unittest-srv: 329: Init unittest services!!!
hwkey-agent: 41: hwkey-agent is running!!
hwkey-agent: 347: key_mgnt_processing .......
hwkey-agent: 255: Setting EKB key 0 to slot 14
hwkey-agent: 178: Init hweky-agent services!!
luks-srv: 40: luks-srv is running!!
luks-srv: 157: Init luks-srv IPC services!!
platform_bootstrap_epilog: trusty bootstrap complete
�[1;89r
welcome to lk
calling constructors
initializing heap
creating bootstrap completion thread
top of bootstrap2()
initializing platform
bpmp: platform_init
tag is e73a758761f0c6d24a1e69a2ac6b5035
tag_show initialized
dt initialized
mail initialized
chipid initialized
fuse initialized
sku initialized
speedo initialized
ec_get_ec_list: found 45 ecs
ec initialized
ec_mrq initialized
vmon_populate_monitors: found 3 monitors
vmon initialized
adc initialized
fmon_populate_monitors: found 73 monitors
fmon initialized
fmon_mrq initialized
reset initialized
nvhs initialized
392 clocks registered
clk_mrq_init: mrq handler registered
clk initialized
nvlink initialized
io_dpd initialized
io_dpd initialized
thermal initialized
i2c5 controller initialized
initialized i2c mrq handling
i2c initialized
regulator initialized
avfs_clk_platform initialized
soctherm initialized
aotag initialized
powergate initialized
dvs initialized
pm initialized
pg_late initialized
strap initialized
tag initialized
emc initialized
clk_dt initialized
avfs_ccplex_platform initialized
tj_max: dt node not found
tj_init initialized
/uphy is not enabled status = disabled
uphy_dt initialized
uphy initialized
safereg_init: period 80 ms
ec_late initialized
mrq initialized
�[[0082.557] I> Welcome to TBoot-CPU Recovery
�mon_post initialized
�0082.557] I> Heap: [0xa4000000 ... 0xaa000000
[0082.562] I> gpio framework initialized
�lk_set_parent failed for clk i2c2, parent pll_aon (-22)
clk_set_parent failed for clk i2c8, parent pll_aon (-22)
�0082.574] I> tegrabl_gpio_driver_register: register 'nvidia,tegra194-gpio' driver
�lk_dt_late initialized
machine_check initialized
pm_post initialized
dbells initialized
avfs_clk_platform_post initialized
dmce initialized
cvc initialized
ccplex_avfs_hw_init: nafll_cluster0: not monitored
ccplex_avfs_hw_init: nafll_cluster1: not monitored
ccplex_avfs_hw_init: nafll_cluster2: not monitored
ccplex_avfs_hw_init: nafll_cluster3: not monitored
avfs_clk_mach_post initialized
regulator_post initialized
rm initialized
sc7_diag initialized
thermal_test initialized
serial_late initialized
clk_post initialized
clk_dt_post initialized
mc_reg initialized
pg_post initialized
dyn_modules initialized
sku_debugfs initialized
speedo_debugfs initialized
adc_debugfs initialized
clk_debugfs initialized
�0082.588] I> tegrabl_gpio_driver_register: register 'nvidia,tegra194-gpio-aon' driver
[0082.657] I> tegrabl_tca9539_init: i2c bus: 1, slave addr: 0x46
[0082.669] W> fetch_driver_phandle_from_dt: failed to get node with compatible ti,tca9539
[0082.676] W> fetch_driver_phandle_from_dt: failed to get node with compatible nxp,tca9539
[0082.678] W> tegrabl_tca9539_init: failed to fetch phandle from dt
[0082.684] I> tegrabl_tca9539_init: i2c bus: 1, slave addr: 0x44
�mc_debugfs initialized
dvs_debugfs initialized
�0082.695] W> fetch_driver_phandle_from_dt: failed to get node with compatible ti,tca9539
�mon_debugfs initialized
vmon_debugfs initialized
pg_debugfs initialized
profile_fs initialized
debugfs_cons initialized
mail_fs initialized
profile initialized
cvc_debugfs initialized
dmce_debugfs initialized
ec_debugfs initialized
rm_debugfs initialized
soctherm_debug initialized
gr_reader initialized
mods initialized
dt_fs initialized
debugfs_mrq initialized
debug_mrq initialized
debug_safereg initialized
initializing target
calling apps_init()
starting app shell
entering main console loop
] �0082.706] W> fetch_driver_phandle_from_dt: failed to get node with compatible nxp,tca9539
[0082.757] W> tegrabl_tca9539_init: failed to fetch phandle from dt
[0082.766] I> fixed regulator driver initialized
[0082.788] I> CPU: Nvidia Carmel
[0082.789] I> CPU: MIDR: 0x4e0f0040, MPIDR: 0x80000000
[0082.789] I> chip revision : A02
[0082.789] I> Boot-device: eMMC
[0082.790] I> Boot_device: SDMMC_BOOT instance: 3
[0083.231] I> sdmmc-3 params source = boot args
[0083.232] I> sdmmc bdev is already initialized
[0083.232] I> sdmmc-3 params source = boot args
[0083.259] I> Found 20 partitions in SDMMC_BOOT (instance 3)
[0083.272] W> Cannot find any partition table for 00010003
[0083.272] I> Recovery boot_type: 0
[0083.272] I> Entering 3p server
[0083.273] I> USB configuration success
[0086.708] I> Populate storage info
[0087.252] I> Erasing device 0: 3
[0088.324] I> Writing device 0: 3.
[0088.430] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[0088.431] I> Erasing device 1: 3
[0088.925] I> Writing device 1: 3.
[0088.932] I> Writing device 1: 3.
[0088.946] W> Cannot find any partition table for 00010003
[0088.946] E> NV3P_SERVER: Failed to initialize partition table from GPT.

I found I could specify JP 4.4.1 with this sdkmanager docker. It failed also in the same fashion as the above. So hopefully 4.3 will be the ticket.

4.3 still not working

┌─ INSTALLATION FAILED ───────────────────────────────────────────────────────────────────────────────────────┐┌─ Terminal Log ───────────────────────────────────────────────────────────────────────────────────────────────┐
│  Do you want to retry?                                                                                      ││info: [  11.9465 ] Writing partition secondary_gpt with gpt_secondary_0_3.bin                                 │
│   Retry                                                                                                     ││info: [  11.9471 ] [...] 100%                                                                                 │
│   Exit                                                                                                      ││info:                                                                                                         │
│                                                                                                             ││info: [  12.0578 ] Erasing sdmmc_user: 3 ... [Done]                                                           │
│                                                                                                             ││info: [  12.5512 ] Writing partition master_boot_record with mbr_1_3.bin                                      │
│                                                                                                             ││info: [  12.5517 ] [...] 100%                                                                                 │
│                                                                                                             ││info: [  12.5527 ] Writing partition primary_gpt with gpt_primary_1_3.bin                                     │
│                                                                                                             ││info: [  12.5593 ] [...] 100%                                                                                 │
│                                                                                                             ││info: [  12.5608 ] 000000000d0d0001: o initialize partition table from GPT.                                   │
│                                                                                                             ││info: [  12.5741 ]                                                                                            │
│                                                                                                             ││info: [  12.5741 ]                                                                                            │
│                                                                                                             ││error: Error: Return value 1                                                                                  │
│                                                                                                             ││info: Command tegradevflash_v2 --pt flash.xml.bin --create                                                    │
│                                                                                                             ││info: Failed flashing t186ref.                                                                                │
│                                                                                                             ││info: [ Component Install Finished with Error ]                                                               │
│                                                                                                             ││info: [host] [ 8.68 GB used. Disk Avail: 41.26 GB ]                                                           │
│                                                                                                             ││info: [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 1m4s ]                                            │
│                                                                                                             ││info:                                                                                                         │
│                                                                                                             ││error: command terminated with error                                                                          │
│                                                                                                             ││info: Installation failed.                                                                                    │
│                                                                                                             ││info: Depends on failed component                                                                             │
│                                                                                                             ││info: Depends on failed component                                                                             │
│                                                                                                             ││info: Depends on failed component                                                                             │
│                                                                                                             ││info: Depends on failed component                                   
s initialized
profile initialized
cvc_debugfs initialized
dmce_debugfs initialized
ec_debugfs initialized
rm_debugfs initialized
soctherm_debug initialized
gr_reader initialized
mods initialized
dt_fs initialized
debugfs_mrq initialized
debug_mrq initialized
debug_safereg initialized
initializing target
calling apps_init()
starting app shell
entering main console loop
] �
[0051.618] W> tegrabl_tca9539_init: failed to fetch phandle from dt
[0051.629] I> fixed regulator driver initialized
[0051.650] I> CPU: Nvidia Carmel
[0051.650] I> CPU: MIDR: 0x4e0f0040, MPIDR: 0x80000000
[0051.651] I> chip revision : A02
[0051.651] I> Boot-device: eMMC
[0051.651] I> Boot_device: SDMMC_BOOT instance: 3
[0052.094] I> sdmmc-3 params source = boot args
[0052.094] I> sdmmc bdev is already initialized
[0052.095] I> sdmmc-3 params source = boot args
[0052.121] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[0052.134] W> Cannot find any partition table for 00010003
[0052.134] I> Recovery boot_type: 0
[0052.135] I> Entering 3p server
[0052.135] I> USB configuration success
[0053.402] I> Populate storage info
[0053.633] I> Erasing device 0: 3
[0054.692] I> Writing device 0: 3.
[0054.802] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[0054.803] I> Erasing device 1: 3
[0055.297] I> Writing device 1: 3.
[0055.304] I> Writing device 1: 3.
[0055.318] W> Cannot find any partition table for 00010003
[0055.318] E> NV3P_SERVER: Failed to initialize partition table from GPT.

Trying to tell it to install 4.2 gives

Jetson version 4.2 does not support Linux target OS on JETSON_AGX_XAVIER_TARGETS
Available options are:

JetPack 4.6.1
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6.1 --targetos Linux --host --target JETSON_AGX_XAVIER_TARGETS --flash all --additionalsdk 'DeepStream 6.0.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6.1 --targetos Linux --host --target JETSON_XAVIER_NX_TARGETS --flash all --additionalsdk 'DeepStream 6.0.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6.1 --targetos Linux --host --target JETSON_TX2_TARGETS --flash all --additionalsdk 'DeepStream 6.0.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6.1 --targetos Linux --host --target JETSON_TX1_TARGETS --flash all --additionalsdk 'DeepStream 6.0.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6.1 --targetos Linux --host --target JETSON_NANO_TARGETS --flash all --additionalsdk 'DeepStream 6.0.1'

JetPack 4.6 (rev. 3)
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6 --targetos Linux --host --target JETSON_AGX_XAVIER_TARGETS --flash all --additionalsdk 'DeepStream 6.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6 --targetos Linux --host --target JETSON_XAVIER_NX_TARGETS --flash all --additionalsdk 'DeepStream 6.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6 --targetos Linux --host --target JETSON_TX2_TARGETS --flash all --additionalsdk 'DeepStream 6.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6 --targetos Linux --host --target JETSON_TX1_TARGETS --flash all --additionalsdk 'DeepStream 6.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.6 --targetos Linux --host --target JETSON_NANO_TARGETS --flash all --additionalsdk 'DeepStream 6.0'

JetPack 4.5.1 (rev. 1)
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_AGX_XAVIER --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target CLARA_AGX_DEVKIT --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_XAVIER_NX --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_XAVIER_NX_DEVKIT --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_TX2 --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_TX2I --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_TX2_4GB --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_TX2_NX --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_TX1 --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_NANO_DEVKIT --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_NANO_2GB_DEVKIT --flash all --additionalsdk 'DeepStream 5.1'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5.1 --targetos Linux --host --target JETSON_NANO --flash all --additionalsdk 'DeepStream 5.1'

JetPack 4.5
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_AGX_XAVIER --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_XAVIER_NX_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_XAVIER_NX --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_TX2 --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_TX2_4GB --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_TX2I --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_TX1 --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_NANO_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_NANO --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.5 --targetos Linux --host --target JETSON_NANO_2GB_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'

JetPack 4.4.1
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_AGX_XAVIER --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_XAVIER_NX_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_XAVIER_NX --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_TX2 --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_TX2_4GB --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_TX2I --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_TX1 --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_NANO_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_NANO --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4.1 --targetos Linux --host --target JETSON_NANO_2GB_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'

JetPack 4.4
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_AGX_XAVIER --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_XAVIER_NX_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_XAVIER_NX --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_TX2 --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_TX2_4GB --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_TX2I --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_TX1 --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_NANO_DEVKIT --flash all --additionalsdk 'DeepStream 5.0'
sdkmanager --cli install --logintype devzone --product Jetson --version 4.4 --targetos Linux --host --target JETSON_NANO --flash all --additionalsdk 'DeepStream 5.0'

Then I think it is more than just module EOL. It could be the broken emmc as you said.

There is no alternative solution. AGX Xavier does not have QSPI. If the emmc is dead, then even bootloader software cannot be installed.

Okay that’s helpful information…

I found from generic-no-api_r2 (i believe that L4T 32.6.1 is indeed paired with JP 4.6) that this AGX 2888 0004 should be supported there. Which leads me to think that it is not because I need these really old Jetpacks.

If the emmc is dead, then even bootloader software cannot be installed.

Can you confirm based on the logs I have shown whether at this stage of the process if it is enough to configure booting from an SD card or NVMe or USB? No?

Not possible. No other interface can work for bootloader installation except QSPI and emmc.

Can you confirm based on the logs I have shown whether at this stage of the process if it is enough to configure booting from an SD card or NVMe or USB? No?

OK. as i mentioned in original post, customer service is refusing to issue me an RMA for this device because it’s beyond one year warranty.

Could you help me find the exact component that the eMMC chip is, so that i can take it to a hardware repair shop to get it replaced?

I found another topic of the same issue: High failure rate during reliability testing of 32GB Xavier AGX modules

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