Does your file system support boot images – meaning that the boot images have to be programmed in specific address (exp. 0xFFF00000 in PPC microprocessors) and continuous code?
TargetFFS supports boot images by allowing the flash chip to be shared. You don’t have to turn the whole chip over to TargetFFS. In the driver, you specify the base address that TargetFFS accesses and the number of 512-byte sectors above the base address which it can use, like so: /*—————————————*/ /* Register flash volume with TargetFFS. */ /*—————————————*/ vol.name = “flash”; vol.block_size = BLOCK_SIZE; vol.num_sectors = (BLOCK_SIZE * NUM_BLOCKS) / SECTOR_SIZE; vol.mem_base = STRATA_BASE; vol.write_byte = write_byte; vol.write_sector = write_sector; vol.read_sector = read_sector; vol.erase_block = erase_block; if (FsNorAddVol(&vol)) perror(“FlashAddVol failed: “); There is some more discussion of this in the manual, in Chapter 2.
Related Questions
- Does your file system support boot images - meaning that the boot images have to be programmed in specific address (exp. 0xFFF00000 in PPC microprocessors) and continuous code?
- Does Oracle support using Red Hat Global File System (GFS) with Oracle RAC (Real Application Clusters) software?
- Does DriveCopy 4.0 support Windows XP and the NTFS file system?