Hi,
I have a a reComputer J4012 based on an Orin NX 16GB. I have been able to flash the official SDK as well as Yocto based images for the past few months, but now get EEPROM read errors :
Here are serial logs when using the official SDK:
[0362.129] I> MB1 (version: 1.4.0.1-t234-54845784-08e631ca)
[0362.134] I> t234-A01-1-Silicon (0x12347) Prod
[0362.138] I> Boot-mode : BPMP Diagnostic
[0362.142] I> Entry timestamp: 0x00000000
[0362.146] I> last_boot_error: 0x0
[0362.149] I> BR-BCT: preprod_dev_sign: 0
[0362.153] I> rst_source: 0xb, rst_level: 0x1
[0362.157] I> Task: Initialize MB2 params
[0362.161] I> MB2-params @ 0x40060000
[0362.165] I> Task: Crypto init
[0362.168] I> Task: Perform MB1 KAT tests
[0362.172] I> Task: NVRNG health check
[0362.175] I> NVRNG: Health check success
[0362.179] I> Task: Secure debug controls
[0362.183] I> Task: strap war set
[0362.186] I> Task: Program NV master stream id
[0362.190] I> Task: Verify boot mode
[0362.196] I> Task: Alias fuses
[0362.199] W> FUSE_ALIAS: Fuse alias on production fused part is not supported.
[0362.206] I> Task: Print SKU type
[0362.209] I> FUSE_OPT_CCPLEX_CLUSTER_DISABLE = 0x000001c0
[0362.214] I> FUSE_OPT_GPC_DISABLE = 0x00000002
[0362.219] I> FUSE_OPT_TPC_DISABLE = 0x000000f0
[0362.223] I> FUSE_OPT_DLA_DISABLE = 0x00000000
[0362.227] I> FUSE_OPT_PVA_DISABLE = 0x00000000
[0362.232] I> FUSE_OPT_NVENC_DISABLE = 0x00000000
[0362.236] I> FUSE_OPT_NVDEC_DISABLE = 0x00000000
[0362.240] I> FUSE_OPT_FSI_DISABLE = 0x00000001
[0362.245] I> FUSE_OPT_EMC_DISABLE = 0x00000000
[0362.249] I> FUSE_BOOTROM_PATCH_VERSION = 0x7
[0362.253] I> FUSE_PSCROM_PATCH_VERSION = 0x7
[0362.257] I> FUSE_OPT_ADC_CAL_FUSE_REV = 0x2
[0362.261] I> FUSE_SKU_INFO_0 = 0xd3
[0362.265] I> FUSE_OPT_SAMPLE_TYPE_0 = 0x3 PS
[0362.269] I> FUSE_PACKAGE_INFO_0 = 0x2
[0362.273] I> SKU: Prod
[0362.275] I> Task: Boost clocks
[0362.278] I> Initializing PLLC2 for AXI_CBB.
[0362.282] I> AXI_CBB : src = 35, divisor = 0
[0362.286] I> Task: Voltage monitor
[0362.289] I> VMON: Vmon re-calibration and fine tuning done
[0362.295] I> Task: UPHY init
[0362.298] W> UPHY: UPHY lane info table is empty in MB1 BCT.
[0362.303] I> Task: Boot device init
[0362.306] I> Boot_device: RCM
[0362.309] I> USB configuration success
[0362.313] I> Task: TSC init
[0362.316] I> Task: Enable WDT 5th expiry
[0362.320] I> Task: I2C register
[0362.323] I> Task: Set I2C bus freq
[0362.326] I> Task: Reset FSI
[0362.329] I> Task: Enable clock-mon
[0362.333] I> FMON: Fmon re-programming done
[0362.337] I> Task: Mapper init
[0362.340] I> Task: MB1 fixed firewalls
[0362.346] W> Firewall readback mismatch
[0362.351] I> Task: Load MB2/Applet/FSKP
[0362.355] I> Loading MB2 Applet
[0362.358] I> Slot: 1
[0362.360] E> BLOCK_DEV: Failed to open blockdev.
[0362.365] E> LOADER: Failed to open blockdev 0(0).
[0362.371] E> LOADER: Failed to get storage info for binary 21 from loader.
[0362.378] C> LOADER: Could not read binary 21.
[0362.382] E> Failed to load MB2
[0362.385] C> Task 0x46 failed (err: 0x27228311)
[0362.390] E> Top caller module: MB2_PARAMS, error module: LOADER, reason: 0x11, aux_info: 0x83
[0362.398] C> Boot Info Table status dump :
0111100000111000110111111111000000011110000000000000011000001
Here are the logs from the SDK (I have tried to flash Jetpack 6.0 and 5.1.3): logs.zip (383.2 KB)
When flashing a Yocto-based image I get the same serial logs, but the script returns the additional ERR: could not retrieve EEPROM board information.
Is there a way to fix this ?
Any help would be appreciated, thanks!
Antoine
The UART log was captured at the same time than the provided sdkmanager logs, yes.
In the sdk logs I can see
ERROR: failed to read rcm_state
[...]
Error: Reading board information failed.
Which seemed to indicate the same kind of eeprom error than the Yocto scripts, but I may be wrong.
In any case, I am now unable to flash the board, and it’s been working fine until today.
Strangely enough I am now able to flash the board. I am using the same two computers, same cable, same SDK, USB ports etc. The only thing that I did was to leave the board powered off for the night. I had tried power cycles before but it didn’t help. Any idea of what might have been the issue ?