Busy spin Orin NX custom carrier

[robyawyx]

1. hello. getting a error when booting with “Busy Spin”. I have tried following page 13 at

https://developer.download.nvidia.com/assets/embedded/secure/jetson/agx_orin/Adaptation_and_Bringup_for_Jetson_AGX_Orin.pdf?pJzJc-9Bc9UKcjzaaBLTcZfeVuALqS_utKBFBvyfKGV2KzbaJOvBouTClN7ttq13T4BV8U9YRH3e_MHZzcENZ2PgqqA_AWUgSAc_7tfAjtZhGFhfWsQ3RRtSZ8OJubXGOwS0LBEV1hBFHfZNtlUe3APDVdw9yFsdF72rrgSUz6bKqsLy2TCjycVkkcBt-6EEpDFdSA==&t=eyJscyI6ImdzZW8iLCJsc2QiOiJodHRwczovL3d3dy5nb29nbGUuY29tLyJ9

which states:

EEPROM is an optional component for a customized carrier board. In the case the carrier board
is designed without an EEPROM, below modifications will be needed on the MB2 BCT file:
Linux_for_Tegra/bootloader/tegra234-mb2-bct-common.dtsi
- cvb_eeprom_read_size = <0x100>
+ cvb_eeprom_read_size = <0x0>

Ive changed in the generated yocto image files, and then flashed, but still got the error when booting.

(I flahsed with initrd flash after doing these changes)

[WayneWWW]

1. Is it rel-36 or rel-35 ?
2. Is it Orin NX or Orin AGX?
3. There are lots of reasons that can lead to busy spin. You could share the log so that we can tell. Maybe it is not related to eeprom at all.

[robyawyx]

Jetson Linux release: R35.5.0 JetPack release: 5.1.3

[WayneWWW]

Reply all the questions please…

Is this Orin NX? or Nano? or AGX?
The document you are reading is for Orin AGX but the topic tells you are using Orin NX…

Orin NX should refer to this doc
https://docs.nvidia.com/jetson/archives/r35.5.0/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html?highlight=cvb_eeprom_read_size#eeprom-modifications