Device not booting with custom carrier board,

hello team, we are using jetson orin nano 8GB SOM with custom board,
and flashed the image with haltest jestson 36.2.0, while booting we are getting ‘Busy Spin’ error, its trying to read EEPROM with 0xAE address repeadtedly, i have attached the logs for reference,
please help us on this

Logs:
I> Task: Prepare eeprom data
E> I2C: slave not found in slaves.
E> I2C: Could not write 0 bytes to slave: 0x00ae with repeat start true.
E> I2C_DEV: Failed to send register address 0x00000000.
E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via instance 0.
E> eeprom: Retry to read I2C slave device.
E> I2C: slave not found in slaves.
E> I2C: Could not write 0 bytes to slave: 0x00ae with repeat start true.
E> I2C_DEV: Failed to send register address 0x00000000.
E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via instance 0.
E> eeprom: Failed to read I2C slave device
C> Task 0x0 failed (err: 0x1f1e050d)
E> Top caller module: I2C_DEV, error module: I2C, reason: 0x0d, aux_info: 0x05
I> Busy Spin

https://docs.nvidia.com/jetson/archives/r36.2/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html#eeprom-modifications

Also modify Linux_for_Tegra/bootloader/tegra234-mb2-bct-misc-p3767-0000.dts.

Hello DaveYYY,

we had already done those changes u mentioned, but still same issue.

we cahgned in Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts

  • cvb_eeprom_read_size = <0x100>
  • cvb_eeprom_read_size = <0x0>

after modifying the file, we did below steps

  1. sudo ./jetson-disk-image-creator.sh -o sd-blob.img -b jetson-orin-nano-devkit -d SD

  2. copied image to sd card using baleno Etcher (Flashing Support — NVIDIA Jetson Linux Developer Guide 1 documentation)

  3. we inserted SD card and booted, seeing the same issue

This file resides in the QSPI bootloader, not SD card.
The situation won’t change no matter how many times you flash the SD card.

do we need to flash qspi bootloder or how it will take these changes?
how do we know that it accepted our changes

Either do this:

sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

to update only the QSPI bootloader,
or do this:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device mmcblk0p1 \
  -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal

to update everything.

Hi Dave, thanks for the quick reply, with that command its working now, and device is able to boot and landed in askling for username and password,

what could be the default password from jetpack36.2.0 .

tegra-ubuntu login:

tried: ubuntu/ubuntu
nvidia/nvidia

There is no such thing.
Do this if you are not greeted with the OEM config:
https://docs.nvidia.com/jetson/archives/r36.2/DeveloperGuide/SD/FlashingSupport.html#skipping-oem-config

Hello DaveYYY, Now we are able to boot the device and OS is up and running, i see that gpio sysfs is depricated now, with another gpio lib (gpiodetct, gpioinfo) commands we are not able to make the particular pin as output and write value as high,

for example: PAC.06(line144 in gpiochip0), can you please help on how we can make high that pin, we calculated with offset value its comes gpio number 492,

we have attached the gpiod
gpiod_logs.txt (11.1 KB)
logs for reference

Please file another topic for the GPIO issue.

sure thank you

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