I do Android development on many Tegra devices, including the Jetsons. As the cboot source for t210 has not been released, even though it’s been promised for almost 2 years now, I have to make due with the prebuilt l4t copy for p3448. As of l4t r32.4.4, Cboot on the nano 2gb/4gb dev modules would read LNX from the sd as expected. As of l4t r32.5.0, Cboot will only read LNX from qspi. Nvtboot will also only read many other boot partitions from qspi and not the sd. While a small u-boot image fits into the small space allocated to LNX on qspi, a Linux kernel as needed to boot android cannot fit. Please advise if cboot source will be released soon, so such options can be configured as needed, or if support for reading boot partitions from the sd can be re-enabled on official l4t builds.
Sorry that there is still no plan to release cboot src for t210.
Could you give more detail about why this does not work after we move the uboot to qspi?
The android boot sequence does not involve u-boot. The boot image is created with the kernel and optionally a ramdisk and flashed to LNX.
It is possible to move the production to emmc based module?
The sdcard module is not targeting to be made as a product. It can only be used on nv devkit.
If you move to emmc based module, then all the partitions will be on emmc so it may have larger size.
The main target for my work is hobbiests. And the devkits are the more used devices there. Yes, the emmc based devices such as the tx1 devkit, the tx2 devkit, and agx xavier work as expected. The nx devkit also still works as expected, loading LNX from the sd. However for t186 and t194 targets, cboot source is available, allowing proper android support in the bootloader, or re-enabling sd support if necessary. My intent is to support all available Tegra hardware, t210+.