Difference between revisions of "UBIFS"
From ArmadeusWiki
m (→Setting up) |
m (→Additional informations) |
||
| Line 19: | Line 19: | ||
== Additional informations == | == Additional informations == | ||
| − | A new file 'ubinize.cfg' defining the ubi volumes is located in target/device/armadeus/ | + | A new file 'ubinize.cfg' defining the ubi volumes is located in target/device/armadeus/ |
this file contains the different UBI volumes of the UBI image: | this file contains the different UBI volumes of the UBI image: | ||
* [ubifs] | * [ubifs] | ||
* mode=ubi | * mode=ubi | ||
| − | |||
* vol_id=0 | * vol_id=0 | ||
| − | |||
* vol_type=dynamic | * vol_type=dynamic | ||
* vol_name=rootfs | * vol_name=rootfs | ||
Revision as of 23:20, 16 September 2009
Page under construction...
Informations on this page are not guaranteed !!
This is a preliminary page dealing with the installation of UBIFS on the APF boards. UBIFS will replace JFFS2 file system on NAND based board because JFFS2 induces a big overhead when parsing, reading and writing on NAND devices UBISFS scalability
Introduction
Setting up
- host system: add mtd-utils uuid uuid-dev packages:
sudo apt-get install uuid-dev
- buildroot: target filesystem -> ubifs root filesystem (0x1F800, 0x800, 2047)
- linux: file systems -> Miscellanous -> ubifs support and disable debugging !!
- linux: device driver -> mtd -> ubi unsorted block image -> Enable UBI (4096) and disable debugging !!
- uboot: setenv bootcmd run ubifsboot
- uboot: setenv download_rootfs tftpboot ${loadaddr} ${serverpath}${board_name}-rootfs.arm.ubifs
Additional informations
A new file 'ubinize.cfg' defining the ubi volumes is located in target/device/armadeus/ this file contains the different UBI volumes of the UBI image:
- [ubifs]
- mode=ubi
- vol_id=0
- vol_type=dynamic
- vol_name=rootfs
- vol_alignment=1
- vol_flags=autoresize
This file is processed by the ubinize utility after mkfs.ubifs.
