2.44 Flash Write Control (FCW)

Using The Library

The main Flash memory can not be read while it is being erased or written, the CPU is stalled during the entire operation. All functions that modify the main Flash can be run from RAM memory to avoid CPU stall while main Flash is being erased or written.

FCW APIs are implemented to be non-blocking, the API will return immediately if not stalled by Flash operation. The user application can either poll the status or get callback once the flash operation is completed.

• With polling, the application will need to continuously check if the flash operation is completed

• With callback, the registered callback function will be called once the flash operation is completed. This means the application do not have to poll continuously. The interrupt must be enabled in MCC for callback method

Here is an example code to erase a page and program a row of memory using polling method

#define APP_FLASH_ADDRESS  (FCW_FLASH_START_ADDRESS + (FCW_FLASH_SIZE / 2))

uint8_t CACHE_ALIGN rowBuffer[FCW_FLASH_ROWSIZE] = {0};

void populate_buffer(uint8_t* data)
{
    int i = 0;

    for (i = 0; i < (FCW_FLASH_ROWSIZE); i++)
    {
        *(data + i) = i;
    }
}

int main (void)
{
    /*Populate rowBuffer to programmed*/
    populate_buffer(rowBuffer);

    while(FCW_IsBusy());

    /* Erase the page */
    FCW_PageErase(APP_FLASH_ADDRESS);

    /* Wait for page erase  to complete */
    while(FCW_IsBusy());

    /* Program a row of data */
    FCW_RowWrite((uint32_t *)rowBuffer, APP_FLASH_ADDRESS);

    /* Wait for row program to compete */
    while(FCW_IsBusy());
}

Library Interface

Flash Write Control (FCW) peripheral library provides the following interfaces:

Functions

Data types and constants