On our custom board. We have no EEPROM on it. how can we boot Jetson Xavier NX module sucess?

▒▒
[0000.025] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[0000.033] I> MB1 (prd-version: 2.6.0.0-t194-41334769-cab45716)
[0000.038] I> Boot-mode: Coldboot
[0000.041] I> Platform: Silicon
[0000.044] I> Chip revision : A02P
[0000.047] I> Bootrom patch version : 15 (correctly patched)
[0000.052] I> ATE fuse revision : 0x200
[0000.056] I> Ram repair fuse : 0x0
[0000.059] I> Ram Code : 0x2
[0000.061] I> rst_source: 0x0, rst_level: 0x0
[0000.066] I> Boot-device: QSPI (instance: 0)
[0000.070] I> Qspi flash params source = brbct
[0000.074] I> Qspi clock source : pllp
[0000.078] I> Qspi-0 initialized successfully
[0000.082] I> Boot chain mechanism: A/B
[0000.085] I> Current Boot-Chain Slot: 0
[0000.089] I> BR-BCT Boot-Chain: 0, status: 0. update flag: 0
[0000.094] I> Qspi flash params source = brbct
[0000.100] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0000.107] I> Temperature = 30500
[0000.110] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.115] W> Skipping boost for clk: BPMP_APB
[0000.119] W> Skipping boost for clk: AXI_CBB
[0000.123] W> Skipping boost for clk: AON_CPU_NIC
[0000.127] W> Skipping boost for clk: CAN1
[0000.131] W> Skipping boost for clk: CAN2
[0000.135] I> Boot-device: QSPI (instance: 0)
[0000.139] I> Qspi flash params source = mb1bct
[0000.143] I> Qspi clock source : pllc_out0
[0000.147] I> Qspi-0 reinitialized
[0000.150] I> Qspi flash params source = mb1bct
[0000.163] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.170] W> Thermal config not found in BCT
[0000.178] W> MEMIO rail config not found in BCT
[0000.190] I> Qspi flash params source = mb1bct
[0000.203] I> Qspi flash params source = mb1bct
[0000.237] I> Qspi flash params source = mb1bct
[0000.801] I> Qspi flash params source = mb1bct
[0000.818] I> Qspi flash params source = mb1bct
[0000.857] W> Platform config not found in BCT
[0000.884] I> Qspi flash params source = mb1bct
[0000.909] 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.919] I> Welcome to MB2(TBoot-BPMP) (version: default.t194-mobile-74494172)
[0000.919] I> DMA Heap @ [0x526fa000 - 0x52ffa000]
[0000.920] I> Default Heap @ [0xd486400 - 0xd48a400]
[0000.921] E> DEVICE_PROD: Invalid value data = 70020000, size = 0.
[0000.926] W> device prod register failed
[0000.930] I> gpio framework initialized
[0000.934] I> tegrabl_gpio_driver_register: register ‘nvidia,tegra194-gpio’ driver
[0000.941] I> tegrabl_gpio_driver_register: register ‘nvidia,tegra194-gpio-aon’ driver
[0000.949] I> No valid sdcard_params in mb1_bct
[0000.953] I> Boot_device: QSPI_FLASH instance: 0
[0000.958] I> qspi flash-0 params source = boot args
[0000.963] I> QSPI-0l initialized successfully
[0000.966] I> sdmmc-3 params source = safe params
[0001.366] I> sdmmc DDR50 mode
[0001.384] I> Found 41 partitions in QSPI_FLASH (instance 0)
[0001.401] W> Cannot find any partition table for 00000003
[0001.402] > PARTITION_MANAGER: Failed to publish partition.
[0001.418] I> Found 22 partitions in SDMMC_USER (instance 3)
[0001.419] I> Active Boot chain : 0
[0002.101] I> Relocating BR-BCT
[0002.102] > DEVICE_PROD: device prod is not initialized.
[0002.103] E> I2C: Timeout while polling for bus clear. Last value 0x00000000.
[0002.104] E> I2C: Failed to clear bus for instance 0.
[0002.105] > DEVICE_PROD: device prod is not initialized.
[0002.106] E> I2C: Failed to clear bus for instance 0.
[0002.107] E> I2C_DEV: Failed to initialize instance 0.
[0002.111] E> eeprom: Can’t get handle to eeprom device @160
[0002.116] I> Failed to read CVM eeprom data
[0002.120] E> Error getting EEPROM data!
[0002.124] E> cpubl: Parallel task execution failed
[0002.129] I> ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒: execution failed
[0002.134] I> ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒: execution failed
[0002.140] E> Top caller module: EEPROM, error module: EEPROM, reason: 0x2a, aux_info: 0x00
[0002.148] I> Reset to recovery mode

Your problem has nothing to do with carrier board eeprom. It looks more like your hardware or something else that crashes your module eeprom.


你的問題跟底板沒有eeprom無關 看來是你的hw設定或是你作了什麼其他的讓module eeprom也讀不到了…

[0002.111] E> eeprom: Can’t get handle to eeprom device @160
[0002.116] I> Failed to read CVM eeprom data
[0002.120] E> Error getting EEPROM data!
[0002.124] E> cpubl: Parallel task execution fai

Thank you for your guidance.It’s the carrier board’s fault,makes the SDA signl keep low all the time,so module eeprom can’t be visited success.We had already solved the problem.Thanks.

1 Like

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