Flash Orin 32G fail

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
,
1

你好，我们公司之前AGX Xavier出货是用的massflash，使用nvmassflashgen.sh生成mfi_jetson-agx-xavier-devkit.tbz2，然后给到工厂，出过300台。现在改用Orin后，制作给到工厂的tar.gz文件刷机失败，我的步骤如下：
1.sudo ./flash.sh -r -k APP -G clone.img jetson-agx-orin-devkit mmcblk0p1
使用这条命令clone一块安装了我方软件的Orin核心板，得到system.img,这个system.img大小是28G
2.执行“sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --massflash 5 jetson-agx-orin-devkit mmcblk0p1”后会把我28G大小的system.img替换为5G的
请问怎样才能让l4t_initrd_flash使用我安装了软件的28G大小的system.img?

3

hello lihl,

actually, there’s tool to backup/restore a Jetson device using the backup image.
please use the tool, /tools/backup_restore/l4t_backup_restore.sh.
for example,
there’s -b options to generate the backup image, and you could enable -r options to restore the backup image.

after you complete back-up process and have the image store to your local host,
you may read README_backup_restore.txt for the workflow to massflash the backup image.
for example,
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --massflash <x> <board-name> mmcblk0p1

1 Like
4

Massflash package is generated successfully, thank you very much

5

刷机后新设备无法启动，详细描述如下：
按照<README_backup_restore.txt>中“Workflow 3: To massflash the backup image”操作，最后一步操作后(sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 5)，Log中提示新设备刷机成功。但重新上电后，被刷机的新设备无法启动，现象是：Debug串口没有任何输出，跟刚买到没有刷过的Orin核心板一样。
我这要量产出货还挺着急的
请问，其他使用Orin-32G的客户量产是怎么做的？

8

hello lihl,

we cannot repo the failure,
please check below for our steps to backup/restore a Jetson device using the backup image…
after flash completed, device can boot up normally with backup rootfs.

$ sudo ./tools/backup_restore/l4t_backup_restore.sh -b -c jetson-agx-orin-devkit
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --massflash 1 jetson-agx-orin-devkit
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 1

1 Like
9

使用上面的3条命令后可以成功刷机和启动了，包括“–massflash 5”，感谢您的支持

1 Like
10

上面十月4号的帖子，我验证成功刷机和启动是用的稍微改动的system.img，大小是5G，是为了节省验证时的刷机时间.
今天用实际出货的大小是28G的system.img，刷机成功后还是启动不了，问题依然存在。具体如下：
我完全照搬上面的3条命令，刷机Log中提示刷机成功，但重启 启动不了，Debug串口没有任何log输出，刷过的Orin核心板跟没刷过的Orin核心板一样。
请问，是不是bootloader没刷进去？或者我还能再怎么尝试下？是system.img太大了，有什么地方参数不对？

11

hello lihl,

could you please check rootfs image size after this command-line executed?

12

生成的mmcblk0p1.tar.gz大小是24.3GB.
另外有个奇怪的现象：我昨天用“l4t_initrd_flash.sh --flash-only”命令分5次，每次刷一台，共刷了5台Orin核心板，都能重启能正常使用。今天同样的主机和环境，又出现刷机后不能启动的问题了，刷了2台Orin核心板刷完log提示成功，但都不能重启。懵圈了。
如果其他用户没这种刷机成功但不能启动的问题，那可能是我们PCBA的问题？我已经找了一块其他公司的Orin载板验证，要周六才能到

13

hello lihl,

we’ve tested it and we cannot repo the failure,
please have cross validation to confirm whether it’s hardware issue.

15

can you comment out these lines in tools/kernel_flash/l4t_network_flash.func

enable_nfs_for_folder ()
{
    set +e
    rpcbind > /dev/null 2>&1
    set -e

    local nfs_dir=$1
    local networkargs=$2

    local arr=
    IFS=':' read -r -a arr <<< "${networkargs}"

    local target_ip=${arr[1]:-fc00:1:1::/48}

    chmod 755 "${nfs_dir}"
    chown root.root "${nfs_dir}"
#   if ! grep -qvE "^\s*#|^\s*$" /etc/exports; then
#           echo "# Entry added by NVIDIA initrd flash tool" >> /etc/exports
#           echo "${nfs_dir} ${target_ip}(${PERMISSION_STR})" >> /etc/exports
#   fi
    if [[ "${target_ip}" =~ : ]]; then
            target_ip="[${target_ip}]"
    fi
    exportfs -o "${PERMISSION_STR}" "${target_ip}:${nfs_dir}"
}

and try these commands instead?

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --network usb0 --massflash 5 jetson-agx-orin-devkit mmcblk0p1

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 5 --network usb0 --showlogs

1 Like
16

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