Can't flash different NVMe

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
,
1

Hi there,

I have been successfully flashing my Jetson NX with an NVMe SSD using this command:

sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh \
                --external-device nvme0n1 \
                -c tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml \
                -S 8GiB \
                --showlogs \
                jetson-xavier-nx-devkit-emmc external

In preparing the SSDs for flashing, I reformat them following the steps in these tutorials:

Recently I’ve had to update the brand of SSD, and using the same setup procedure, the flashing appears to fail at this stage:

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 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 target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Timeout
Cleaning up...

The SSD that works is:
https://www.mouser.dk/datasheet/2/612/660p_series_brief-1387234.pdf

The SSD that does NOT work is:

The only difference between the two SSDs that I am using that I can tell is that the micron uses gen 4 PCIe, whereas the old one is gen 3 PCIe. Would that be the cause of the problem? Is there any way around this? Or could it be something else I’ve missed?

Thanks for your help,
Chris

2

I can’t tell you the cause, but the PCIe v4 and PCIe v3 won’t be related to the issue. Each generation can fall back to the next lower speed standard if there are issues. Both of those drives should work even on an old PCIe v1 bus.

Incidentally, I can’t answer the question, but whoever does answer it will want the full serial console boot log if that “Waiting for target…” message is from boot after flash; if that message is from actual flash, then whoever answers will want the full flash log (in the case of sdkmanager there is a button to export logs; those logs can be attached to the forum; just ask if you need to know how to save logs for a command line flash).

3

Thanks for your input.

flash_logs.txt (17.7 KB)

Somehow I was able to get the SSH to be exposed, but seeing this error now:

Error flashing non-qspi storage

Any idea as to why? Seems like some kind of hardware incompatibility in the l4t_flash_from_kernel.sh script

4

Someone else will need to answer since I don’t have external boot devices to test. Basically though, you probably need to perform some sort of initrd flash instead of the standard eMMC flash. This in turn might require you to set up the NVMe separately from the flash (I’m not sure if the NVMe is just a target during the initrd flash or if flash actually populates the NVMe…in one case flash is setting up a pointer to rootfs, and in the other case flash is also adding content to the rootfs…I have no external media so I’ve never done this on a Jetson).

5

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