I’ve suspected this for some time now, I had initially flashed an A02 r32.3.1 image to an A02 board and used it for 2 months. Then when I got my hands on a B01 board I had tried to boot the same sd card on the B01 (I’m pretty sure the SOM boards are compatible) there was no signs of life. An etcher flashed official r32 image (not through the SDK manager) booted fine on both boards.
I had initially dismissed this as some B01, A02 OS compatibility issues
Now that I have another B01 board, I tried both the SDK and etcher flashed images and the result is the same - an r32 image flashed via the SDK manager (Jetson Nano Devkit P3448, no extra SDKs) will work on the same device it was flashed on but not on another. Are the images somehow tied to the hardware UUIDs? I need to know this because I do own quite a number of boards now and do swap SD cards frequently - to test firmware etc.
We have found similar issue before, and the workaround is the fresh new module must be flashed by SDKM first to get the initial bootrom info updated, afterward there should be no issue to swap to another SD card, or reduce the chance. We will fix this issue at the next release.
Well just to be clear, are you trying to say that flashing via the SDKM always yields images that will work on multiple boards?
There seems to be some contradiction on another thread (Not able to run jetson-io.py). What would be great is if nvidia states the steps for us to reproduce flashing of images that are able to work on multiple devices, e.g.
Format SD card
Flash on SDKM (which add-ons to skip/include)
…
For right now I would like to state that the only way for an sd card to work on multiple boards in my experience is to flash it with the official r32 images using etcher or dd, and not the SDK manager.
Hi all! I can confirm that images devices (not sd cards) flashed with the sdkm are able to swap sd cards after updating the QSPI. I haven’t tested compatibility with etcher flashed images but I’d expect them to work as well.