Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Use case #2
*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:
#Finally, the Linux kernel mounts the root filesystem from the SDRAM memory and starts user-space applications and daemons.
It is worth remembering that <code>mtd0</code>,<code>mtd1</code>, and <code>mtd2</code> are used as raw partitions while <code>mtd3</code> is associated with a block device in order to mount a filesystem, specifically ''UBIFS''. To handle such filesystem, the Linux kernel must be built with the UBI/UBIFS support enabled and the root filesystem must include the <code>mtd-utils-ubifs</code> package (see the following image).
[[File:TBD.png|thumb|center|600px|Selcting the <code>mtd-utils-ubifs</code> package in PataLinux root filesystem configuration]] To setup this the desired standalone configuration, several operations need to be carried out. They are detailed in the following sections. It is assumed that the SOM can boot from the NOR flash. If not, please see [[Restoring_U-Boot_on_SPI_NOR_flash_(BELK/BXELK)|this page]].
===Storing the images onto the raw partitions of the NAND memory===
