Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Use case #2
</pre>
==Use case #2==
This example is based on the partitioning scheme illustrated in the following image.
TBD
In this case, the NOR flash is only used to store U-Boot and its environment. All the other images are stored onto the NAND flash. Specifically, the NAND flash has four partitions that are used to store respectively:
*The <code>uImage</code> binary image, which, in turn, consists of the Linux kernel and a [http://www.linuxfromscratch.org/blfs/view/svn/postlfs/initramfs.html <code>initramfs</code> image].
**By the way, this is the default format used for the root filesystem generated by [[/BELK-TN-006:_Using_PetaLinux_to_Build_BELK/BXELK_Software_Components|PetaLinux]]
**This partition is associated with the device file <code>/dev/mtd0</code>
*The PL bitstream
**This partition is associated with the device file <code>/dev/mtd1</code>
*The Device Tree Blob
**This partition is associated with the device file <code>/dev/mtd2</code>
*An auxiliary read/write filesystem used by the user-space applications for several purposes such as data logging.
**This partition is associated with the device file <code>/dev/mtd3</code>
The resulting bootstrap sequence is like the following:
#U-Boot is retrieved from the NOR flash and copied into the SDRAM memory
#U-boot, in turn, reads from the NAND memory the uImage, the bitstream, the DTB, and copies them into the SDRAM memory
#U-Boot starts the Linux kernel
#Finally, the Linux kernel mounts the root filesystem (<code>initramfs</code>) from the SDRAM memory and starts user-space applications and deamons.
To setup this configuration, several operations need to be carried out. They are detailed in the following sections.
===Storing the images in the first three partitions===
<pre>
found binary data: 5979916
</pre>
===Formatting the fourth partition===
</pre>
===Finalizing the U-Boot environment for the automatic boot===