|
|||||||||||
Technical Support On-Line Manuals RL-ARM User's Guide (MDK v4) RL-RTX RL-FlashFS Technical Data NAND Flash Translation Layer Embedded File System Memory Organization Allocation Information File Data Fragments Limitations Configuring RL-FlashFS Source Files Configuration Options File System Flash Drive SPI Flash Drive RAM Drive Memory Card Drive USB Flash Drive NAND Flash Drive Using RL-FlashFS Using Flash Devices Flash Driver Sector Layout Converting FlashPrg.c Converting FlashDev.c Limitations When Using Internal Flash Using SPI Flash Devices SPI Flash Driver SPI Sector Layout Using RAM Devices Using Memory Card Devices MCI Driver SPI Driver Using FlashFS with USB Devices FAT Driver Using NAND Devices NAND Driver NAND Page Data Layout Function Overview File I/O Routines File Maintenance Routines File Time Support Routines Flash Driver Routines FAT Driver Routines MCI Driver Routines SPI Driver Routines NAND Driver Routines IOC Interface Routines System Routines RL-TCPnet RL-CAN RL-USB Example Programs Library Reference Appendix |
Memory OrganizationThe Memory Organization of a Flash Device is divided into Flash sectors. Flash sectors are named blocks in RL-FlashFS. Typically, a blocks is a 64 KB memory page. Blocks can be devided into memory cells, which are written sequencially. The memory cell size depends on the device architecture and is 8- (byte), 16- (half word) or 32-bit wide (word). Each Block contains its own allocation information written to the file allocation table located on top of memory. The file name and file content are stored in lower memory regions. If the file size exceeds a single block, then the file is stored across several blocks. Several smaller files are stored into a single block. When the file content is modified, the old file content is invalidated and a new memory block is allocated. The Flash Block is erased when all the data stored in the Flash Block have been invalidated. | ||||||||||
|
Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.