Orin NX 烧录失败

我按照Quick Start文档中的步骤操作:
执行报错:sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-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

Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
blockdev: cannot open /dev/mmcblk3boot0: No such file or directory
[ 0]: l4t_flash_from_kernel: Starting to create gpt for emmc
Active index file is /mnt/internal/flash.idx
Number of lines is 61
max_index=60
[ 1]: l4t_flash_from_kernel: Successfully create gpt for emmc
[ 1]: l4t_flash_from_kernel: Starting to create gpt for external device
Active index file is /mnt/external/flash.idx
Number of lines is 18
max_index=17
writing item=1, 9:0:primary_gpt, 512, 19968, gpt_primary_9_0.bin, 16896, fixed-<reserved>-0, cfc7668651ac7662d1bded6eb20ae9453c9a8f7c
Writing primary_gpt partition with gpt_primary_9_0.bin
Offset is not aligned to K Bytes, no optimization is applied
dd if=/mnt/external/gpt_primary_9_0.bin of=/dev/nvme0n1 bs=1 skip=0  seek=512 count=16896
16896+0 records in
16896+0 records out
16896 bytes (17 kB, 16 KiB) copied, 0.0209905 s, 805 kB/s
Writing primary_gpt partition done
Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Warning: Not all of the space available to /dev/nvme0n1 appears to be used, you can fix the GPT to use all of the space (an extra 380580528 blocks) or continue with the current setting? 
Writing secondary_gpt partition with gpt_secondary_9_0.bin
Offset is not aligned to K Bytes, no optimization is applied
dd if=/mnt/external/gpt_secondary_9_0.bin of=/dev/nvme0n1 bs=1 skip=0  seek=61203267072 count=16896
16896+0 records in
16896+0 records out
16896 bytes (17 kB, 16 KiB) copied, 0.0221465 s, 763 kB/s
Writing secondary_gpt partition done
Fix/Ignore? Fix                                                           
Warning: Not all of the space available to /dev/nvme0n1 appears to be used, you can fix the GPT to use all of the space (an extra 380580528 blocks) or continue with the current setting? 
Model: Thinkplus ST8000 PCI-E M.2 256G (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                Flags
 2      20.5kB  134MB   134MB                A_kernel            msftdata
 3      134MB   135MB   786kB                A_kernel-dtb        msftdata
 4      135MB   168MB   33.2MB               A_reserved_on_user  msftdata
 5      168MB   302MB   134MB                B_kernel            msftdata
 6      302MB   303MB   786kB                B_kernel-dtb        msftdata
 7      303MB   336MB   33.2MB               B_reserved_on_user  msftdata
 8      336MB   420MB   83.9MB               recovery            msftdata
 9      420MB   421MB   524kB                recovery-dtb        msftdata
10      421MB   488MB   67.1MB               esp                 boot, esp
11      488MB   572MB   83.9MB               recovery_alt        msftdata
12      572MB   572MB   524kB                recovery-dtb_alt    msftdata
13      572MB   639MB   67.1MB               esp_alt             msftdata
14      639MB   1059MB  419MB                UDA                 msftdata
15      1059MB  1562MB  503MB                reserved            msftdata
 1      1562MB  61.2GB  59.6GB               APP                 msftdata

[ 2]: l4t_flash_from_kernel: Expanding last partition to fill the storage device
[ 2]: l4t_flash_from_kernel: Successfully create gpt for external device
Flash index file is /mnt/internal/flash.idx
Number of lines is 61
max_index=60
[ 2]: l4t_flash_from_kernel: Starting to flash to qspi
QSPI storage size: 67108864 bytes.
Flash failure
Cleaning up...

以下是串口日志:

[    6.650497] pcieport 0007:00:00.0: Adding to iommu group 6
[    6.650577] pcieport 0007:00:00.0: PME: Signaling with IRQ 193
[    6.651907] pcieport 0007:00:00.0: AER: enabled with IRQ 193
[    6.652322] pci_bus 0007:01: busn_res: [bus 01-ff] is released
[    6.652454] pci 0007:00:00.0: Removing from iommu group 6
[    6.652470] pci_bus 0007:00: busn_res: [bus 00-ff] is released
insmod /lib/modules/5.15.122-tegra/kernel/drivers/nvme/host/nvme-core.ko 
insmod /lib/modules/5.15.122-tegra/kernel/drivers/nvme/host/nvme.ko 
[    6.670244] nvme 0004:01:00.0: Adding to iommu group 5
[    6.670592] nvme nvme0: pci function 0004:01:00.0
[    6.670839] nvme 0004:01:00.0: enabling device (0000 -> 0002)
[    6.706299] nvme nvme0: allocated 128 MiB host memory buffer.
[    6.710143] nvme nvme0: 8/0/0 default/read/poll queues
[    6.716237]  nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15
insmod /lib/modules/5.15.122-tegra/kernel/drivers/thermal/tegra/tegra-bpmp-thermal.ko 
insmod /lib/modules/5.15.122-tegra/kernel/drivers/hwmon/pwm-fan.ko 
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/gadget/libcomposite.ko 
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/typec/typec.ko 
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko 
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/typec/ucsi/ucsi_ccg.ko 
insmod /lib/modules/5.15.122-tegra/kernel/drivers/usb/gadget/udc/tegra-xudc.ko 
ules/5.15.122-tegra/kernel/net/ipv6/ipv6.ko g to ioinsmodmmu /loupib/ 7
insmod /lib/modules/5.15.122-tegra/extra/drivers/staging/platform/tegra/gte/tegra194_gte.ko 
insmod /lib/modules/5.15.122-tegra/extra/drivers/nvpps/nvpps.ko 
[  .768989] NET: Registeinsred /l PFib/mod_INET6 pruleotos/5col fa.12mil2-ta/extr  6riv.76/net/e9601] theSegment/nt Ria/out with theIPv6
rnet/n[    6.769608] .koIn- sit
u OAM (IOAM) with IPv6
[    6.771724] tegra194_gte: module verification failed: insnaturemod an /lr rired kib/ules/5missing -egrinta/k kernedrivers/usb/typec/stusb160x.ko 
insmod /lib/modules/5.15.122-tegra/extra/drivers/platform/tegra/mce/tegra-mce.ko 
[    6.817244] tegra-qspi 3270000.spi: Adding to iommu group 8
[    6.817759] tegra-qspi 3270000.spi: Prod config not found for QSPI: -19
[    6.818772] spi-nor spi0.0: mx25u51279g (65536 Kbytes)
[   67.906922] using random self ethernet address
[   67.906929] using random host ethernet address
Add /dev/nvme0n1
[   67.913248] Mass Storage Function, version: 2009/09/11
[   67.913252] LUN: removable file: (no medium)
[   67.914362] LUN: removable file: (no medium)
[   67.915330] LUN: removable file: (no medium)
[   67.916310] LUN: removable file: (no medium)
[   67.918733] usb0: HOST MAC 6a:5e:3f:cc:f3:88
[   67.918737] usb0: MAC 7e:e9:6b:31:c5:6a
[   67.920661] tegra-xudc 3550000.usb: EP 0 (type: ctrl, dir: out) enabled
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-5.1# [   68.451042] tegra-xudc 3550000.usb: EP 5 (type: intr, dir: in) enabled
[   68.451064] tegra-xudc 3550000.usb: EP 3 (type: bulk, dir: in) enabled
[   68.451077] tegra-xudc 3550000.usb: EP 2 (type: bulk, dir: out) enabled
[   68.451194] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[   68.451348] tegra-xudc 3550000.usb: EP 7 (type: bulk, dir: in) enabled
[   68.451365] tegra-xudc 3550000.usb: EP 4 (type: bulk, dir: out) enabled
[  324.573104] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573283] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573300] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573307] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573313] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573318] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573325] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573330] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573333] nfs: server fc00:1:1:0::1 not responding, timed out
[  324.573337] nfs: server fc00:1:1:0::1 not responding, timed out
[  443.357341] rpc_check_timeout: 25 callbacks suppressed
[  443.357346] nfs: server fc00:1:1:0::1 not responding, timed out
[  504.797328] nfs: server fc00:1:1:0::1 not responding, timed out
[  504.797607] nfs: server fc00:1:1:0::1 not responding, still trying
[  509.917133] nfs: server fc00:1:1:0::1 not responding, timed out

看起來像是你的SSH連線不穩斷掉了 原本有連上的但是中途斷掉了
要不要換一條flashing cable試試看

我换过线,也是一样的问题,试了几次都是这样,还有可能是其他原因吗?我是用的笔记本安装的Ubuntu22.04,没有使用虚拟机

先用

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

把bootloader燒進去
然後試試看這個
https://docs.nvidia.com/jetson/archives/r35.5.0/DeveloperGuide/SD/FlashingSupport.html#flashing-to-an-nvme-drive

這樣flash的時候不接device也可以

这一步已经成功:sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
我看到第二步需要设备从eMMC启动,但是我的设备上没有eMMC怎么办呢

不用eMMC,那只是文件通俗的寫法而已
你確定你的機器現在開機可以進UEFI menu就好

可以把UEFI放在nvme上吗?有没有引脚可以配置从nvme启动UEFI?
因为我们需要修改UEFI,放在nvme上可以方便工厂批量烧录

不行 沒辦法

有没有方法可以创建一个完整的nvme镜像使用dd命令烧录,而不是使用l4t_initrd_flash.sh命令,因为工厂批量烧录时不需要搭建开发环境

你不如直接用硬碟拷貝機比較快

是否可以在系统启动之后更新SPI flash中的UEFI?

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

你要不要不同問題開新的topic問
搞不太懂你現在到底想知道什麼