Jetson AGX stuck in boot, can't connect to a monitor

Today our Jetson AGX Xavier Development Kit 32GB stopped suddenly working.
When connecting a monitor nothing show up and the LEDs of the keyboard do not turn on.

I managed to connect the Serial Console and I got this :

[0000.156] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[0000.165] I> MB1 (prd-version:
[0000.170] I> Boot-mode: Coldboot
[0000.173] I> Platform: Silicon
[0000.176] I> Chip revision : A02P
[0000.179] I> Bootrom patch version : 15 (correctly patched)
[0000.184] I> ATE fuse revision : 0x200
[0000.187] I> Ram repair fuse : 0x0
[0000.190] I> Ram Code : 0x2
[0000.193] I> rst_source: 0x0, rst_level: 0x0
[0000.198] I> Boot-device: SDMMC (instance: 3)
[0000.214] I> sdmmc DDR50 mode
[0000.218] I> Boot chain mechanism: A/B
[0000.222] I> Current Boot-Chain Slot: 0
[0000.225] W> No valid slot number is found in scratch register
[0000.231] W> Return default slot: _a
[0000.235] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0000.242] I> Temperature = 30500
[0000.245] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.250] W> Skipping boost for clk: BPMP_APB
[0000.254] W> Skipping boost for clk: AXI_CBB
[0000.258] W> Skipping boost for clk: AON_CPU_NIC
[0000.262] W> Skipping boost for clk: CAN1
[0000.266] W> Skipping boost for clk: CAN2
[0000.270] I> Boot-device: SDMMC (instance: 3)
[0000.281] I> Sdmmc: HS400 mode enabled
[0000.285] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.292] W> Thermal config not found in BCT
[0000.300] W> MEMIO rail config not found in BCT
[0000.322] I> sdmmc bdev is already initialized
[0000.367] W> Platform config not found in BCT
[0000.401] I> MB1 done
����main enter
SPE VERSION #: R01.00.18 Created: Jan 29 2021 @ 14:18:27
HW Function test
Start Scheduler.
in late init
[0000.410] I> Welcome to MB2(TBoot-BPMP) (version: default.t194-mobile-f46b9673)
[0000.411] I> DMA Heap @ [0x526fa000 - 0x52ffa000]
[0000.411] I> Default Heap @ [0xd486400 - 0xd48a400]
[0000.412] E> DEVICE_PROD: Invalid value data = 70020000, size = 0.
[0000.418] W> device prod register failed
[0000.421] I> Boot_device: SDMMC_BOOT instance: 3
[0000.426] I> sdmmc-3 params source = boot args
[0000.431] I> sdmmc-3 params source = boot args
[0000.434] I> sdmmc bdev is already initialized
[0000.443] I> Found 21 partitions in SDMMC_BOOT (instance 3)
[0000.449] I> Found 41 partitions in SDMMC_USER (instance 3)
[0000.450] W> No valid slot number is found in scratch register
[0000.455] W> Return default slot: _a
[0000.459] I> Active Boot chain : 0
[0000.486] I> Relocating BR-BCT
[0000.487] > DEVICE_PROD: device prod is not initialized.
[0000.512] E> I2C: slave not found in slaves.
[0000.513] E> I2C: Could not write 0 bytes to slave: 0x00ae with repeat start true.
[0000.514] E> I2C_DEV: Failed to send register address 0x00000000.
[0000.515] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via instance 0.
[0000.516] E> eeprom: Failed to read I2C slave device
[0000.519] I> Failed to read CVB eeprom data @ AE
[0000.523] I> Retrying CVB eeprom read @ AC …
[0000.563] I> Relocating OP-TEE dtb from: 0x6bfff0f0 to 0x70050000, size: 703
[0000.564] I> [0] START: 0x80000000, SIZE: 0x2f000000
[0000.565] I> [1] START: 0xaf200000, SIZE: 0x18a00000
[0000.565] I> dram_block larger than 80000000
[0000.566] I> [2] START: 0x100000000, SIZE: 0x780000000
[0000.569] I> Setting NS memory ranges to OP-TEE dtb finished.
[0000.621] I> EKB detected (length: 0x410) @ VA:0x526ff400
[0000.623] I> Setting EKB blob info to OPTEE dtb finished.
��NOTICE: BL31: v2.5(release):ef8af0b99
NOTICE: BL31: Built : 20:57:59, May 16 2022
��I/TC: Non-secure external DT found
��bpmp: init
bpmp: tag is 128431eec76692047e1ac1ebc0392266
sku_dt_init: not sku 0x00
clk_early initialized
mail_early initialized
fuse initialized
hwwdt initialized
t194_ec_get_ec_list: found 45 ecs
ec initialized
vmon_setup_monitors: found 3 monitors
vmon initialized
adc initialized
fmon_populate_monitors: found 73 monitors
fmon initialized
mc initialized
reset initialized
nvhs initialized
uphy_early initialized
emc_early initialized
��I/TC: OP-TEE version: 6f444ac��392 clocks registered
��f (gcc version 9.3.0 (Buildroot 2020.08)��clk initialized
��)��io_dpd initialized
�� #��thermal initialized
thermal_mrq initialized
��2 Tue May��i2c initialized
�� ��vrmon_dt_init: vrmon node not found
vrmon_chk_boot_state: found 0 rail monitors
vrmon initialized
��17 04:00:18 UT��regulator initialized
��C 2022 aarch64
I/TC: Primary CPU initializing
��avfs_clk_platform initialized
soctherm initialized
aotag initialized
powergate initialized
dvs initialized
pm initialized
suspend initialized
pg_late initialized
pg_mrq_init initialized
strap initialized
nvl initialized
emc initialized
emc_mrq initialized
clk_dt initialized
tj_init initialized
uphy_dt initialized
uphy_mrq initialized
uphy initialized
ec_swd_poll_start: 281 reg polling start w period 47 ms
ec_late initialized
hwwdt_late initialized
reset_mrq initialized
ec_mrq initialized
fmon_mrq initialized
clk_mrq initialized
avfs_mrq initialized
mail_mrq initialized
i2c_mrq initialized
tag_mrq initialized
console_mrq initialized
mrq initialized
clk_sync_fmon_post initialized
��I/TC: Prim��clk_dt_late initialized
noc_late initialized
��a��pm_post initialized
dbells initialized
��ry ��dmce initialized
��C��cvc initialized
��PU switching to ��avfs_clk_mach_post initialized
��norm��avfs_clk_platform_post initialized
��al ��cvc_late initialized
regulator_post initialized
��world��rm initialized
console_late initialized
clk_dt_post initialized
�� b��mc_reg initialized
��pg_post initialized
profile initialized
fuse_late initialized
extras_post initialized
bpmp: init complete
entering main console loop
] ��
Jetson UEFI firmware (version r34.1-975eef6 built on 2022-05-16T20:58:45-07:00)

Does anyone know what is going on and what could I do to fix it ?

Thank you very much for your help.

Could you try to reflash it with sdkmanager?

The thing is when I hold the recovery button and the reset button for two seconds and then I release the recovery button and then the reset button (I hope it is the right way to put it in force recovery…) the same message appears on the Serial Console and the sdkmanager says that the Jeston is not connected even though it is plugin to my pc with the usb-c port.
Do you know why and what could I try ?

Recovery button is the last one got released.

Well that was it thank you ! It is working again now that I reflashed it.

1 Like

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