 RL-ARM User's Guide | |
| Home Products Events Support | |
Technical Support
On-Line Manuals
RL-ARM User's Guide
RL-RTX 
RL-FlashFS Flash Memory Management 
Memory Organization File Allocation Information File Data Blocks Technical Data Configuring Flash File System Configuration Flash Device Sector Memory Map FS_FlashDev.h Converting FlashDev.c Program and Erase Code FS_FlashPrg.c Converting FlashPrg.c SPI Flash Device FS_SPI_FlashDev.h Programming Code FS_SPI_FlashPrg.c RAM Device Memory Card Device MCI Interface SPI Interface File Time Support System Configuration Library Files Using Flash File System Using Flash Devices Using Dedicated Flash Devices Using One Large Flash Device Using Internal Flash Devices Using RAM Devices RAM Configuration Example Using Memory Card Devices Hot Insertion Root Directory Limitation Debugging Function Overview File I/O Routines File Maintenance Routines File Time Support Routines Low-Level Routines SPI Interface Routines System Functions RL-TCPnet RL-CAN Example Programs Library Reference AppendixUsing One Large Flash Device
A special configuration is required when a single Flash Device is used for storing files and application code. The code can not be executed from a Flash device while it is being programmed. For this reason, programming routines are relocated to RAM and executed within RAM while Flash is being programmed or erased. The programming routines located in module FS_FlashPrg.c are relocated at runtime and copied to RAM for execution.
In addition to a standard Flash Device configuration, the programming functions must:
- relocate to RAM using the function attribute __ram,
- be protected from interrupts for IRQ and FIQ interrupts. This is possible by using the function attribute __swi or relocating your IRQ interrupt handler function to RAM also. You should be careful if you are using FIQ interrupts as well.
| Contact Site Map Press Privacy | Copyright © 2010 Keil™, An ARM® Company. All rights reserved. |
