Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Use case #1
This configuration makes use of one of the most common partitioning schemes, that is:
*The NOR flash acts as boot memory; as such, it contains
**bootrom header
**U-Boot SPL
**U-Boot
**U-Boot redundant environment
**Even though these images are not strictly required to boot the system, the NOR flash also contains:***The Linux kernel image***The Linux Device Tree Blob (DTB)***The bitstream file for the Programmable Logic (PL).*The NAND flash contains the a partition devoted to a read/write UBIFS root filesystem (read/write). The resulting flash memory layout is illustrated in the following pictures. [[File:BELK-NOR-flash-partitioning-case1.png|thumb|center|600px|NOR flash partitioning scheme]] [[File:BELK-NAND-flash-partitioning-case1.png|thumb|center|600px|NAND flash partitioning scheme]]
*Once started, the Linux kernel mount the root filesystem from a NAND partition.
====Testbed====
This configuration was tested with the following testbed:
*SOM: DBXF4110D2R
* Boot the system via SD or NFS as described into the [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)|System boot and recovery via microSD card]] and [[Booting_the_system_via_NFS_(BELK/BXELK)|Booting the system via NFS]]
* By default, the NAND is already partitioned to allow booting from NAND-only (see next section) and, thus, some partitions are reserved for FSBL, U-boot and kernel images. Here we won't modify this default configuration. The [[Memory Tecnology Technology Device (MTD)|MTD]] partitions can be dumped with <code>/proc/mtd</code> (the partition's name should be self-explanatory)
