we are flashing developer module(SD card) using below command, same will be used for eMMC ?
sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1
Or need to change machine name ( jetson-xavier-nx-devkit )
Actually, these “machine names” are just board config file under Linux_for_Tegra. For example, jetson-xavier-nx-devkit is mapping to jetson-xavier-nx-devkit.conf.
Same rules apply to every jetson platform board config.
Thus, if you want to run emmc version, you have to use jetson-xavier-nx-devkit-emmc.
- Both module(Sd card version and EMMC version) uses QSPI flash, for MB1, MB2, bootloader ?
The board config file will point out one “EMMC_CFG” file. Thus, take emmc board for example, you can check the file bootloader/t186ref/cfg/flash_l4t_t194_spi_emmc_p3668.xml
This file will tell you what partitions are on spi or emmc.
Can we put bootloader to eMMC/SD card ?
Can We flash all images to eMMC/SD card and bypass QSPI flash ?
I think this is not possible. This partition layout is well defined and we don’t reveal the source of nvtboot which uses for flash to public.
What is the difference between development and production module as per flashing terms. ?
Please compare the cfg files of these two and you shall know the difference.