Can’t backup OEM AGX Orin board. Waiting for target to boot-up

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

backup.txt (107.1 KB)
I have set cvb_eeprom_read_size = <0x0>; in bootloader/tegra234-mb2-bct-common.dtsi.

I have created the OEM config named nd004a.conf, then I run the commond:
sudo ./tools/backup_restore/l4t_backup_restore.sh -b nd004a

When I backup, console always output waiting for target to boot-up…

My sdk version is jetpack r36.4.3

Best regards,
Jacobe Zang

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I’ll try to help you with your issue.

It appears that you’re working with a Jetson device, specifically with the Jetpack r36.4.3 SDK. You’ve modified the bootloader/tegra234-mb2-bct-common.dtsi file to set cvb_eeprom_read_size to <0x0>. You’ve also created an OEM config file named nd004a.conf.

The issue you’re facing is that when you try to backup, the console output is stuck at “waiting for target to boot-up…”.

Here are a few potential causes and suggestions:

  1. OEM config file: Double-check that your nd004a.conf file is correctly formatted and contains the necessary settings for your Jetson device. You can refer to the oem-config configuration file document for more information on the required settings.
  2. Bootloader configuration: Verify that your modifications to the bootloader/tegra234-mb2-bct-common.dtsi file are correct and not causing any issues with the boot process. You can try reverting the changes to see if the issue persists.
  3. SDK version: Although you’re using Jetpack r36.4.3, it’s possible that there are known issues or limitations with this version that might be causing the problem. You can try checking the NVIDIA forums or documentation for any known issues or workarounds.
  4. Backup process: Ensure that you’re using the correct backup process for your Jetson device. You can refer to the Reconfiguring a Jetson Device with oem-config procedure for more information on the correct steps to follow.

To further troubleshoot the issue, you can try the following:

  • Check the console output for any error messages or clues that might indicate what’s causing the issue.
  • Verify that the target device is correctly connected and configured.
  • Try using a different OEM config file or reverting to a previous version to see if the issue persists.

If none of these suggestions help, please provide more information about your setup, including the exact commands you’re using and any relevant configuration files. This will help me better understand your issue and provide a more accurate solution.

4

HI,

Please record the serial console log for us to review.

Thanks

5

device_log.txt (65.8 KB)

Okay

6

Hi,

Some questions to confirm:

Have you used this OEM config to flash the AGX Orin Successfully?

Thanks

7

Yes.

I use the following command:
sudo ./flash.sh nd004a internal

8

Hi,

Please try below commands

sudo ./tools/backup_restore/l4t_backup_restore.sh -e mmcblk0p1 -b nd004a

Thanks

9

The same error. I post the console log.

I also test the jetson-agx-orin-devkit to backup and contrast them. I found that devkit has the ssh. May I lost something like usb net in my OEM configuration?

image
image3019×507 109 KB

console_log.txt (65.7 KB)

10

Hi,

No known UDC device found

We see your log show similar issue discussed in

Please confirm your device tree could enable usb device mode.

Thanks

11

I followed the developer guide to config USB, but seemed still no UDC. Could you help me check is there something I forget to config?
nd004a_dtc.txt (326.2 KB)

12

Hello @DavidDDD

Is there other advices for this post..?

13

Thanks for all your help!

Now my dts config as followings:

				usb2-0 {
					mode = "otg";
					usb-role-switch;
					status = "okay";
					role-switch-default-mode = "host";

Works good for me.

1 Like