RE: Can't seem to get the fstorage library to work properly.

JosephAzar — Tue, 25 Oct 2022 03:28:42 GMT

Ok we got it sorted.
The problem was the actual memory addresses used, so for anyone who comes across this in the future, the way I solved it was to use this method to adjust the memory used:

static uint32_t nrf5_flash_end_addr_get()
{
    uint32_t const bootloader_addr = BOOTLOADER_ADDRESS;
    uint32_t const page_sz         = NRF_FICR->CODEPAGESIZE;
    uint32_t const code_sz         = NRF_FICR->CODESIZE;
    
    uint32_t returnvalue = 0;
    returnvalue = (bootloader_addr != 0xFFFFFFFF ? bootloader_addr : (code_sz * page_sz));
    return returnvalue;
}

This method is used to return the end of the memory taking into account the bootloader position.
So this method returns the end address and i subtracted the size of memory that I wanted and got the start address like this:

end_addr = nrf5_flash_end_addr_get();
fstorage.end_addr = end_addr;
start_addr = end_addr - 0x400;
fstorage.start_addr = start_addr;

This has to be done before the nrf_fstorage_init command.

After that I used the start address to write the bytes i needed and as mentioned everywhere it has to be 32 bit values so multiples of 4 bytes, anything less would return error 0x09.

RE: Can't seem to get the fstorage library to work properly.

Einar Thorsrud — Mon, 24 Oct 2022 12:07:15 GMT

Hi,

I don't immediately see the problem here. Did you remember to do a full erase before testing this code? That is important in case the address you write to was not erased from before, and a write can only flip bits from '1' to '0'. If that is not the problem, then perhaps you can upload a full failing example so that I can have a closer look?