orin nano flashing errors

[AlistairKeiller]

I am trying to flash tegra-demo-distro to my orin nano devkit with an nvme drive. I ran the following code to generate the image:

git clone https://github.com/OE4T/tegra-demo-distro.git --branch kirkstone
cd tegra-demo-distro
git submodule update --init
. ./setup-env --machine jetson-orin-nano-devkit-nvme
bitbake demo-image-weston

Then I unpacked demo-image-weston-jetson-orin-nano-devkit-nvme.tegraflash, and ran sudo ./initrd-flash with my orin nano plugged in and in recovery mode (it shows up in lsusb as NVIDIA Corp. APX).

However, I get the error ERR: could not retrieve EEPROM board information or could not retrieve chip ID(different errors, same operating conditions). When flashing with SDKmanager (which works successfully), it appears to be unclear about the chip ID as well (not sure if that is a result of faulty EEPROM, or just a artifact of orin nano devkits):

So, I manually fed in the chip info: sudo BOARDID=3767 BOARDSKU=0005 FAB=000 ./initrd-flash. This resulted in getting stuck

== Step 3: Sending flash sequence commands at 24-07-28T11:39:52-07:00 ==
Waiting for USB storage device flashpkg from 6f280a08......

Then it gets stuck. I have searched threads for similar issues, and the only ones I have found were a conflict with the tlp package, or people with custom boards or unsupported configurations. However, I am using a stock orin nano devkit, and jetson-orin-nano-devkit-nvme should be a supported configuration. I ordered a serial console to get further debug information, however I have seen few similar issues resolved using serial console output.

I'm confident it's possible to flash, and board is working, since SDKmanager works. I'm just unclear what I am doing wrong on the yocto side.

Any advice for how to successfully flash?

[AlistairKeiller]

Update: I downgraded the version of jetpack on the Orin Nano to the latest 5.x instead of 6.x, and kept SDK manager open in the background, selecting p3737-0005 module whenever the prompt came up. This resolved the issue. For others debugging, I'm not sure which step was the solution, but by looking at various Nvidia threads, it seems like having the correct version of jetpack initially, and therefore the correct EPROM (because it seems like EPROM is flashed by SDK manager???), is important.