Jetson Orin on custom board is Updating on every boot

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
,
1

Hello,

After doing some SPI work on my Orin it now runs some sort of update every time I power on the machine. It runs the update then goes to a normal boot. It starts -

Jetson System firmware version 36.4.0-gcid-37537400 date 2024-09-13T04:02:39+00:
00
ESC   to enter Setup.
F11   to enter Boot Manager Menu.
Enter to continue boot.

Update Progress -   7% ***+++++++++++++++++++++++++++++++++++++++++++++++

That takes a few minutes, then I see :

Jetson System firmware version 36.4.0-gcid-37537400 date 2024-09-13T04:02:39+00:00
ESC   to enter Setup.
F11   to enter Boot Manager Menu.
Enter to continue boot.
L4TLauncher: Unable to locate L4T Support protocol: Not Found
L4TLauncher: Using legacy interface. Support would be deprecated soon!!!
L4TLauncher: Attempting Direct Boot

L4T boot options
0: primary kernel
1: backup kernel
2: primary kernel backup
Press 0-2 to boot selection within 3.0 seconds.
Press any other key to boot default (Option: 0)
EFI stub: Booting Linux Kernel...

and then it finally starts up and loads the desktop. There is a window open that says

Update information 
nvidia-l4t-bootloader Post Install Notification.  
reboot is required to complete the installation'.

What could be causing this and how do I get it to stop ‘Updating’ every time?

sudo apt policy nvidia-jetpack
nvidia-jetpack:
  Installed: (none)
  Candidate: 6.2+b77
  Version table:
     6.2+b77 600
        600 https://repo.download.nvidia.com/jetson/common r36.4/main arm64 Packages
     6.1+b123 600
        600 https://repo.download.nvidia.com/jetson/common r36.4/main arm64 Packages


sudo apt policy nvidia-l4t-core
nvidia-l4t-core:
  Installed: 36.4.3-20250107174145
  Candidate: 36.4.3-20250107174145
  Version table:
 *** 36.4.3-20250107174145 600
        600 https://repo.download.nvidia.com/jetson/t234 r36.4/main arm64 Packages
        100 /var/lib/dpkg/status
     36.4.0-20240912212859 600
        600 https://repo.download.nvidia.com/jetson/t234 r36.4/main arm64 Packages

orin_dmesg.txt (2.3 MB)

3

Hi,

Please record the serial console log for us to review.

Thanks

4

Hello DavidDDD

I mislabeled the serial console output as ‘orin_dmesg.txt’ in the above post. Would you like me to fix the name and re-upload ?

5

Hi,

Could you describe in detail what spi work doing(Any modified/ commands)?
Is your Orin Nano a dev kit or a custom board?

Thanks

Thanks

6

Basically adding to system dtb file - same as this thread - JP6 - SPI3 (/dev/spidev2.0) is not showing up after setting up overlay

Flashed on the dev kit and running on custom board. Have run this process dozens of times w/o issue. Our other dev system which was prepared the same way is not having this issue. It boots normally.

What exactly is it trying to update every time and what is failing ?

7

Hi,

with your log,

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

Please try to modify eeprom followed by Jetson Orin NX and Nano Series — NVIDIA Jetson Linux Developer Guide 1 documentation.
And check whether the issue exists.

Thanks

9

Thank you for your response.

~/Linux_for_Tegra/bootloader/generic/BCT$ grep cvb_eeprom_read_size tegra234-mb2-bct-misc-p3767-0000.dts
			cvb_eeprom_read_size = <0x0>;

From my notes, we’ve been updating that value for our boards since Sept 2023.

10

I ended up re-flashing the Orin on the official dev kit (to an SD card) then moved the orin back to my board and booted from USB w/o issue.

Update - still seeing

L4TLauncher: Unable to locate L4T Support protocol: Not Found
L4TLauncher: Using legacy interface. Support would be deprecated soon!!!
L4TLauncher: Attempting Direct Boot

But it is not running Update (?)

However, once the desktop is dispalyed, there is still a pop up window w/

"nvidia-l4t-bootloader Post Install Notification

Reboot is required to complete the installation"

How do I resolve that issue ?

11

Hi,

The log might be related to bsp version mismatch.
Do you flash with the same bsp version?

Thanks

12

Same l4t_initrd_flash.sh parameters, except --external-devices, for USB HD or SD card.

13

Hi,

Please provide the commands for us to review.

Thanks

14

Flashing to HD attached via USB:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device sda1 -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

Flashing to SD card (on board) :

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
15

This Orin also has the annoying habit of reseting my /boot/extlinux/extlinux.conf file after every reboot.

It copies my ‘primary’ stanza to ‘primary-backup’

LABEL primary-backup
      MENU LABEL primary kernel backup
      LINUX /boot/Image
      FDT /boot/dtb/experimental.dtb
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=fb2b2b2d-5b2d-4299-b03f-99f67367d156 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0 ipv6.disable=1

and reverts to:

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
#      OVERLAYS /boot/jetson-io-hdr40-user-custom.dtbo
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=fb2b2b2d-5b2d-4299-b03f-99f67367d156 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0 ipv6.disable=1

I need the FDT line for my software to work. So, I remove the ‘primary-backup’ stanza and add the FDT line back to the ‘primary’ stanza. When I reboot, my .dtb has loaded but extlinux.conf is reverted to the non-FDT ‘primary’ stanza. As a temporary fix, I’ve just set the default to be primary-backup instead.

Why would it keep reseting itself? Does it have something to do with the pop-up window (from above) that keeps showing up?

16

Is this still an issue to support? Any result can be shared?