|
Could someone please clear up a misunderstanding I may have here?
I understand that the Orange Pi Plus has 8GB eMMC, not NAND. The difference is that NAND is managed by OS drivers that take care of the wear leveling and block erasure (such as MTD and JFFS under linux), whereas eMMC is embedded MMC where the flash controller is part of the module and takes care of the wear leveling and block erasure. This leaves a much simpler task for the OS to manage, and it should appear almost identical to SD cards.
Is this correct? If so, I assume that the binary-only libnand in the SDK is not relevant to this board, and that it would only be relevant to an H3 board that had NAND flash controlled directly by the SoC.
If my understanding of NAND vs eMMC is correct, does this mean that addressing the eMMC from u-boot and the linux kernel should be very similar to addressing the SD card? The implementation should be similar?
Thanks. |
|