I have NX production unit with a modified carrier board.
I have created an system.img file with the matching pinmux & device-tree and all the needed changes.
Does the jetpack 4.6.1 support flashing the OS to nvme card and booting straight from it?
or do I still need to boot first from emmc, copy the FS to the nvme and then boot from it?
and in any of the cases - how? what’s the flash.sh commands?
the only thing that currently works for me is flashing to the internal emmc (NX):
sudo ./flash.sh <board-name> mmcblk0p1
then copy the filesystem to the mounted SSD, manually edit the /boot/extlinux/extlinux.conf to load the rootfs from the nvme and then rebooting and then the kernel and filesystem comes both up from the nvme.
I am fairly new to all of this, so… this might not be a good/correct/best answer.
Have you tried using the SDK manager? (I have a NX with a Seeed Studio carrier and I can use SDK manager to install 4.6.1 to either the EMMC/SD or NVMe - and technically I do not have an SD card on my SOC). I have read numerous times (I think?) that the SDK manager is just a wrapper for the flash util.
The SDK manager is a nice solution for a POC.
but for ease of use I need the flash.sh
since as you said - the SDK uses flash.sh, I would like a solution for using it in cmd
Sorry - I should have been more clear about why I mentioned SDK.
I would recommend that you try the activity with the SDK and view the terminal as it proceeds to update your device (or monitor the management system via a “ps” command).
I just checked my system and there is a ${HOME}/.nvsdkm directory and a log for each time I flashed my device.
Does the following help (I am flashing my NX to the NVMe device here)?