Is there a way to use either SDK Manager or command line (CLI) to create an image with a modified pinmux? Then instead of using the dev kit, use another tool like Etcher to flash to the NVMe drive for use with the Orin NX?
Here is our situation - We have production NX SoMs with external M.2 NVMe SSDs connected to them. When we apply our custom pinmux and try to flash using the dev kit, it locks up and fails. If we use a baseline image, it flashes and works fine. So, we are wondering if we can create a custom image and save it to an .img file (for example) and then use a tool like Etcher to flash the image onto a NVME/SD card, place the drive into the NX SoM and boot it up (basically create the image without the hardware - Prod SoM or dev kit)?
The way you are doing the development sounds a little weird.
Why you are not able to use your board to do the flash work?
Not sure why you are still asking about sdkmanager? A custom board work should be directly using BSP package to implement. SDKM is just for NV devkit.
NVMe or sdcard is just a image for rootfs/kernel, they do not have bootloader software. But a product should have bootloader version aligned with rootfs/kernel in case there is anything wrong. Which means your product shall have all the software flashed by flash tool (not Ethcer) to align their version.
The board does not have a direct serial connection to flash it.
I just mentioned SDK Manager to see if that was possible. We are doing our flashing via command line.
So I have to use the flash tool files to flash the SoM? I know the flash procedure updates 2 components, the onboard QSPI and the NVMe. So I’m guessing I have to connect to the SoM to flash it, either via the dev kit as the carrier board or directly with our custom carrier board (which doesn’t have a serial input atm).