I’m afraid that didn’t help. I’ve attached the log for this command (flash_log02.txt below).
I got a USB-TTL cable, and the failure when doing the SDK Manager approach seems to occur after the following output on the debug console:
insmod /lib/modules/5.15.148-tegra/updates/drivers/net/ethernet/nvidia/nvethernet/nvethernet.ko ^M^M
insmod /lib/modules/5.15.148-tegra/kernel/drivers/usb/typec/stusb160x.ko ^M^M
insmod /lib/modules/5.15.148-tegra/updates/drivers/platform/tegra/mce/tegra-mce.ko ^M^M
insmod /lib/modules/5.15.148-tegra/updates/drivers/spi/spi-tegra210-quad.ko ^M^M
[ 6.934386] tegra-qspi 3270000.spi: Adding to iommu group 9^M
[ 6.934992] tegra-qspi 3270000.spi: Prod config not found for QSPI: -19^M
[ 6.936074] spi-nor spi0.0: mx25u51279g (65536 Kbytes)^M
[ 7.954625] using random self ethernet address^M
[ 7.954629] using random host ethernet address^M
[ 7.982331] usb0: HOST MAC 22:cd:59:fa:ac:6e^M
[ 7.982336] usb0: MAC 62:97:57:48:18:6d^M
[ 7.983465] tegra-xudc 3550000.usb: EP 0 (type: ctrl, dir: out) enabled^M
bash: cannot set terminal process group (-1): Inappropriate ioctl for device^M^M
bash: no job control in this shell^M^M
bash-5.1#
(for full output see log01.txt, attached
log01.txt (91.4 KB))
I’ve seen this error elsewhere (e.g. here and here), but neither of these issues seems to have had a helpful resolution. The first link suggests that the issue is that the OS is “not able to find your rootfs (file system) on the pre-set location”. Since the whole point of this setup is to put the root fs on the nvme SSD drive, it seems like that hasn’t worked somehow.
The debug output shows the bash-5.1 prompt while the SDK Manager is waiting for the initrd boot to finish, so I’m guessing that whatever script on the JONS that failed hadn’t sent the boot confirmation to the host yet. It seems like the next thing to do is figure out exactly what is failing in the JONS flash script so it can be fixed.
flash_log02.txt (285.5 KB)