Modifying the MEMORY Section of the Config.bib File to Support BinFS
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
To implement the binary ROM image file system (BinFS), you must modify the Config.bib file as follows:
Add the EXT region and set it to NANDIMAGE. This prevents the EXT address space from being allocated to RAM. The EXT region is the location for files not stored in the NK region.
The following example shows the NK, EXT, and CHAIN regions of the MEMORY section of a Config.bib file that supports BinFS:NK 800B8000 00300000 RAMIMAGE EXT 803B8000 01000000 NANDIMAGE CHAIN 813B8000 00001000 RESERVEDSet the NK region to RAMIMAGE. The NK region is where files that must be loaded prior to implementation of BinFS are stored. Because the kernel must reside in RAM and the NK region is RAMIMAGE, the files loaded into the NK region typically include everything needed for the kernel.
The NK region files must include the following:- Nk.exe
- Kernel.dll
- Coredll.dll
- K.coredll.dll
- Oalioctl.dll
- Filesys.dll
- Fsdmgr.dll
- Mspart.dll
- Romfsd.dll
- Binfs.dll
- Default.fdf or boot.hv
- Fpcrt.dll (ARM-only)
- Ceddk.dll (if required by your flash driver)
- Your flash driver
If your flash driver is loaded by the device manager, also add device.dll, devmgr.dll, regenum.dll, busenum.dll, and pm.dll to the NK region.
For kernel independent transport layer (KITL) support, also add kitl.dll to the NK region.
For debugging support, also add hd.dll, osaxst0.dll, and osaxst1.dll to the NK region.
Place the remaining items in the EXT section.
For more information on the MEMORY section of a .bib file, see MEMORY Section.