基于36.4.3版本。我制作的工厂烧写镜像,无法烧写成功,请帮忙指导下:
为了减少外因影响,我直接使用的原始的,没有改动过的,压缩包直接解压进行操作:Jetson_Linux_r36.4.3_aarch64.tbz2 ,Tegra_Linux_Sample-Root-Filesystem_r36.4.3_aarch64.tbz2;
制作出来的Linux_for_Tegra是可以通过:./flash.sh jetson-agx-orin-devkit internal 这个命令烧写进去的,板子可以正常启动的。
BOARDID=$(./chkbdinfo -i cvm.bin)
BOARDSKU=$(./chkbdinfo -k cvm.bin)
FAB=$(./chkbdinfo -f cvm.bin)
BOARDREV=$(./chkbdinfo -r cvm.bin)
CHIP_SKU=$(./chkbdinfo -C chip_info.bin_bak)
RAMCODE_ID=$( ./chkbdinfo -R chip_info.bin_bak)
RAMCODE=$(echo “ibase=2; ${RAMCODE_ID//:/}” | bc)
echo "BOARDID=$BOARDID BOARDSKU=$BOARDSKU FAB=$FAB BOARDREV=$BOARDREV CHIP_SKU=$CHIP_SKU RAMCODE_ID=$RAMCODE_ID RAMCODE=$RAMCODE "
BOARDID=3701 BOARDSKU=0004 FAB=500 BOARDREV=J.0 CHIP_SKU=00:00:00:D2 RAMCODE_ID=00:00:00:00 RAMCODE=0
然后我制作工厂烧写镜像:
sudo BOARDID=3701 FAB=500 BOARDSKU=0004 BOARDREV=J.0 CHIP_SKU=“00:00:00:D2” ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --network usb0 --massflash 5 --showlogs jetson-agx-orin-devkit mmcblk0p1
之后开始烧写:
root@sensoro-110:/data2/R36.4.3/temp/Linux_for_Tegra/mfi_jetson-agx-orin-devkit# sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5
rpcbind: another rpcbind is already running. Aborting
Export list for localhost:
/data2/workspace/hzz *
/data2/workspace/lhz/rk3588/rk3588_linux_241112/debian *
/data2/workspace/gsq *
rpcbind: another rpcbind is already running. Aborting
Export list for localhost:
/data2/workspace/hzz *
/data2/workspace/lhz/rk3588/rk3588_linux_241112/debian *
/data2/workspace/gsq *
/data2/R36.4.3/temp/Linux_for_Tegra/mfi_jetson-agx-orin-devkit/tools/kernel_flash/l4t_initrd_flash_internal.sh --network usb0 --usb-instance 3-10 --device-instance 0 --flash-only --network usb0 jetson-agx-orin-devkit mmcblk0p1
Start flashing device: 3-10, rcm instance: 0, PID: 1644489
Log will be saved to Linux_for_Tegra/initrdlog/flash_3-10_0_20250612-101554.log
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes: 1644489
Ongoing processes:
Flash complete (WITH FAILURES)
附件是,flash_3-10_0_20250612-101554.log
以及串口打印:串口.txt
flash_3-10_0_20250612-101554.log (9.5 KB)
串口.txt (59.7 KB)
请帮忙看下,感谢。
I’m wondering if the –massflash 5 flag on the two
l4t_initrd_flash.sh command lines below could matter.
Flashing to Multiple Jetson Devices
The following is from that document and may be relevant.
The actual number of connected devices can be less than the maximum number of devices the package can support.
The tool provides the --keep option to keep the flash environment, and the --reuse options to reuse the flash environment that makes massflash run faster:
For the initial mass flash:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --keep
For subsequent mass flash attempts:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --reuse
请问下,有谁遇到相同的问题了吗,就是说,这个普遍的问题吗?还是只是我这里有问题呢?
I looked for BOARDID=3701 FAB=500 BOARDSKU=0004 BOARDREV=J.0 CHIP_SKU=“00:00:00:D2” and found
j501
If that is your agx orin carrier board I wonder if you need to use seeedstudio 6.2 jetpack mfi_xxxx.tar.gz that can be downloaded from the j501 webpage.
and before trying to flash 5 maybe try their command
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 1 --network usb0 --showlogs
If you’ve already done that but need to create your own initrd massflash package then perhaps do a file diff between the contents of seeedstudios mfi_xxxx.tar.gz and the one that you created.
感谢您的回复,
我可以试一下你说的这个6.2的,但是我肯定需要创建自己的工厂使用包(mfi_xxxx.tar.gz),我们是使用的自己制作的底板,而且,之前使用35.4.1的时候,没有出现过上述的问题,都是正常的。其实我可以用我之前制作的35.4.1的版本的mfi_xxxx.tar.gz,去做实验。
I’m posting this seeedstudio git page in case it could be helpful to make any Jetpack 6.2 modifications.
Here’s the last paragraph from this reply by an Nvidia employee WayneWWW in a post similar to yours. That entire post might be worth reading.
如果你要說你rel-35的時候沒碰到問題, 那只是因為rel-35的kernel並沒有做dependencies check, 不代表說你沒做這件事情就是對的. 你們的usb在這種狀況下使用有機會碰上問題
感谢,您回看了之前的帖子。
是的,您说的这个问题我也想到了。
所以,我现在使用的是我们最初制作的底板,在usb这里没有做过改变的底板。
另外你说的情况,我现在的板子是可以正常通过其他方法,烧写进去的,我想这样应该能说明一些问题。
下周我拿到,nvidia的demo载板的话,我在使用demo载板试一下,现在demo载板不在我身边。下周能拿到。
我使用了,nvidia的官方的devkit底板,还是无法烧写,报错一样。
试了–massflash 1 参数,也不行,报错一样。
You could try preemptively disabling your rpcbind service before launching massflash
sudo systemctl stop rpcbind
sudo systemctl stop rpcbind.socket
Then retry the flash. You can re-enable it after flashing:
After you have an Orin attached via usb cable in recovery mode you could try this.
usbdev=$(lsusb | awk '/0955/ {print $2 "-" $4}' | sed 's/://'); [[ -z "$usbdev" ]] && echo "No Jetson device in recovery mode found." || sudo ./mfi_jetson-agx-orin-devkit/tools/kernel_flash/l4t_initrd_flash_internal.sh --usb-instance "$usbdev" --device-instance 0 --flash-only --network usb0 jetson-agx-orin-devkit mmcblk0p1
用你说的这种发发烧写,报错如下:
root@sensoro-110:/data2/R36.4.3/temp/Linux_for_Tegra#
root@sensoro-110:/data2/R36.4.3/temp/Linux_for_Tegra# lsusb
Bus 002 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:800a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 020: ID 0955:7223 NVIDIA Corp. APX
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@sensoro-110:/data2/R36.4.3/temp/Linux_for_Tegra#
root@sensoro-110:/data2/R36.4.3/temp/Linux_for_Tegra# usbdev=$(lsusb | awk ‘/0955/ {print $2 “-” $4}’ | sed ‘s/://’); [[ -z “$usbdev” ]] && echo “No Jetson device in recovery mode found.” || sudo ./mfi_jetson-agx-orin-devkit/tools/kernel_flash/l4t_initrd_flash_internal.sh --usb-instance “$usbdev” --device-instance 0 --flash-only --network usb0 jetson-agx-orin-devkit mmcblk0p1
*
Step : Build the flashing environment *
*
Create flash environment 0
/data2/R36.4.3/temp/Linux_for_Tegra/mfi_jetson-agx-orin-devkit/bootloader /data2/R36.4.3/temp/Linux_for_Tegra
/data2/R36.4.3/temp/Linux_for_Tegra
Finish creating flash environment 0.
*
Step 1: Boot the device with flash initrd image *
*
/data2/R36.4.3/temp/Linux_for_Tegra/mfi_jetson-agx-orin-devkit/temp_initrdflash/bootloader0 /data2/R36.4.3/temp/Linux_for_Tegra
./tegraflash.py --bl uefi_jetson_minimal_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev --bldtb tegra234-p3737-0000+p3701-0004-nv.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --instance 003-020 --cmd “rcmboot” --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt --bins “psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; tsec_fw tsec_t234_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; pva_fw nvpva_020_sigheader.fw.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE990M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3701-0004-3737-0000_with_odm_sigheader.dtb.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3737-0000+p3701-0004-nv.dtb” --bct_backup
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
Entering RCM boot
[ 0.0258 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[ 0.0258 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[ 0.0258 ] rcm boot with presigned binaries
[ 0.0273 ] tegrarcm_v2 --instance 003-020 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 0.0286 ] No device on specified bus-port[003-020]
Error: Return value 8
Command tegrarcm_v2 --instance 003-020 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
Cleaning up…
I think this is back to your original command line?
sudo ./tools/kernel_flash/l4t_initrd_flash.sh \
–flash-only \
–network usb0 \
jetson-agx-orin-devkit mmcblk0p1
Maybe post a new question on this agxorin forum and then Nvidia will try to help more.
I wonder if
tools/ota_tools/version_upgrade/Image_based_OTA_Examples.txt
or
tools/backup_restore/README_backup_restore.txt
could work for you?
我不太明白,您的意思,我还要再开一个问题单吗? 和现在这个有什么区别呢。 我现在的问题就是使用devkit 板子,和原版的 36.4.3版本的SDK,都无法烧写。
If you open a new ticket with same topic, then I think Nvidia moderators will see it and respond and help.
system
Closed
July 16, 2025, 4:38am
19
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.