About your question)
I am not sure if I understood correctly, but you probably ask if/how to create three “files” where you will write by flashX. Correct?
Yes, you can do that.
Physical description of chip flash is in _flashx_kinetisN_block_map[] in flash_frfe.c file.
Note from MQX_IO_User_Guide: The blocks do not have to follow each other, so a space between blocks is acceptable. It is required that the blocks do not intersect and that they are listed in ascending order in the array by their starting address.
In your case you should edit _bsp_flashx_file_blocks[] in init_flashx.c file and specify there your “banks”/ “files” are.
This level is pure software solution and translation to hardware level is made by flashX driver. Also name of “bank” or “file” is free…
So, you can create file structure your way.
For example:
const FLASHX_FILE_BLOCK _bsp_flashx_file_blocks[] = {
{ "file1", BSP_INTERNAL_FLASH_BASE, BSP_INTERNAL_FLASH_BASE + 0x00000FFF},
{ "file2", BSP_INTERNAL_FLASH_BASE + 0x00001000, BSP_INTERNAL_FLASH_BASE + 0x0000CFFF },
{ "file3", BSP_INTERNAL_FLASH_BASE + 0x0000D000, BSP_INTERNAL_FLASH_BASE + 0x000FFFFF},
{ NULL, 0, 0 }
};
For open this bank/file you can use command like:
flash_file = fopen(FLASH_NAME, NULL);
where FLASH_NAME could be defined for example as "flashx:file1"
Note: frdmk64f.h file contains definition __FLASHX_START_ADDR as ((void *)Image$USEDFLASH_END$Base).
This special definition causes, that __FLASHX_START_ADDR will points to place in flash where your code ends and when you will write data from this location, you don’t need care about size of your code. It is recalculated every when you build your application.
Have a great day,
RadekS
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
