Here is my situation:
I have a Jetson Xavier NX with eMMC, a p3509, and a custom carrier board that we developed.
My co-worker has a Xavier NX with SD card, a p3509, and another custom carrier board, same rev, etc.
I have the Ubuntu 18.04 host, building JP 5.1.1, r35.3.1. I have successfully flashed my eMMC Xavier NX and booted to its Ubuntu desktop, both on p3509 and custom carrier, using flash.sh over USB to my p3668-0001.
I can flash on p3509 and it boots on custom carrier, and vice-versa.
I can also flash on custom carrier and it boots fine.
I have run Linux_for_Tegra/tools/jetson-disk-image-creator.sh to generate an SDcard image for my co-worker to flash onto his SD-card Jetson p3668-0000.
sudo ./jetson-disk-image-creator.sh -o sdImage_xxx.img -b <custom_board_name>+p3668-0000-qspi-sd -d SD
For that to succeed, I had to edit jetson-disk-image-creator to accept the name of our carrier board. I copied the default xavier-nx-devkit name and changed its name to <custom_board_name>, to point to my .conf files. These .conf files work on my computer to flash to my p3668-0001 with flash.sh
Our problem is that my co-worker’s p3668-0000 boots fine when on his p3509 board, but does not boot when moved into his custom carrier board.
We have found some problems that other people had when they corrupted their EEPROM chips on their CVB:
Our carrier boards do not have an EEPROM.
Here is a picture of his boot status. It gets into Linux OS before failing, and sitting forever:
Notice at 27.913261 mmcblk1: mmc1:aaaa SC64G 59.5GB
Notice at 28.007279 it says Root device found: mmcblk0p1
Then at 30.353997 ERROR: mmcblk0p1 not found
(sorry for the blurry image).
Is there some file that jetson-disk-image-creator.sh looks for that flash.sh does not use, that is messing up the image?
I don’t see any posts on the forum regarding this issue, where not having an EEPROM is causing an issue, but that is what I suspect is the problem…