flashwrite persistence

RE: flashwrite persistence

Edvin — Thu, 13 Dec 2018 13:56:33 GMT

Check out the attached project.

It is a project that uses the softdevice. I recommend that you start directly with this if you intend to use the softdevice in the end. Also because the fstorage_nosd.c is blank in SDK12.3.0. You can probably downport it from a newer SDK version, but if you intend to use the softdevice in the end anyway, I don't see any reason why to not use it from the start.

Note that this example is just initializing the fds. It doesn't write or read anything. It only initializes the FDS module.

Note that I also added the lines:

err_code = softdevice_sys_evt_handler_set(sys_evt_dispatch);
APP_ERROR_CHECK(err_code);

in ble_stack_init() and the sys_evt_dispatch() in order to register the fstorage events.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_fds.zip

Are you able to compile this using armgcc? I tested this makefile, and it worked here. If not, what version of armgcc do you use?

Note that when you initialize, write or delete a record, wait for the corresponding events before you countinue.

example:

volatile bool m_init = false;
volatile bool m_write = false;
volatile bool m_delete = false;

static void fds_evt_handler(fds_evt_t const * p_fds_evt)
{
    switch(p_fds_evt->id)
    {
        case FDS_EVT_INIT:
            if(p_fds_evt->result != FDS_SUCCESS)
            {
                // initialization failed.
            }
            else
            {
                m_init = 1;
            }
            break;
            
        // Add the events for write and delete and set the corresponding m_write m_delete to true in these events.
        
        default:
            break;
    }
}

main()
{
    ...
    //init all other things
    my_fds_init_function();
    while(!m_init){};
    
    my_fds_write_function();
    while(!m_fds_write){};
    m_fds_write = false;
    
    my_fds_delete_function();
    while(!m_delete){};
    m_delete = false;
    // Enter main loop.
    
    for (;;)
    {
        //if (NRF_LOG_PROCESS() == false)
        {
            power_manage();
        }
    }
}

BR,

Edvin

RE: flashwrite persistence

paul_tanner — Thu, 13 Dec 2018 12:26:46 GMT

I used the code from the FDS document you suggested above.

"You can check out the guide in or documentation on how to use the FDS module."

In main()

fds_record_t record;

BR. Paul

RE: flashwrite persistence

Edvin — Thu, 13 Dec 2018 11:35:55 GMT

Where do you declare "record"? and what does it look like?

RE: flashwrite persistence

paul_tanner — Thu, 13 Dec 2018 10:53:47 GMT

Thx Edvin,

Initially without softdevice. Will add that later.

Compiling file: main.c

../../../main.c: In function 'main':

../../../main.c:100:13: error: 'struct <anonymous>' has no member named 'p_data'

record.data.p_data = &m_deadbeef;

../../../main.c:101:13: error: 'struct <anonymous>' has no member named 'length_words'

record.data.length_words = 1; /* one word is four bytes. */

../../../main.c:110:13: error: 'struct <anonymous>' has no member named 'p_data'

record.data.p_data = &m_hello;

../../../main.c:112:13: error: 'struct <anonymous>' has no member named 'length_words'

record.data.length_words = (sizeof(m_hello) + 3) / 4;

make: *** [_build/nrf52832_xxaa_main.c.o] Error 1

I may have misinterpreted the above?

Thx. Paul

RE: flashwrite persistence

Edvin — Thu, 13 Dec 2018 09:55:16 GMT

Hello Paul,

Yes. This is possible in SDK12.3.0

fds_record_t is defined in fds.h, so you must add the folder including this in your INC_FOLDERS in your makefile.

$(SDK_ROOT)/components/libraries/fds \

I see that you have included it in your makefile, but there must be something wrong with it.

Do you intend to use the softdevice in your final appliaction?

Can you please paste the compiler output log?

BR,

Edvin

RE: flashwrite persistence

paul_tanner — Wed, 12 Dec 2018 20:59:36 GMT

Thx Edvin and apologies for forgetting the main()

Now when I try to build this as above I find that fds_record_t is undefined.

I think I have the right stuff in the attached Makefile.

Again, I'm wondering if I can do this on SDK 12.3?

Thx. Pauldevzone.nordicsemi.com/.../8308.Makefile.txt

RE: flashwrite persistence

Edvin — Mon, 10 Dec 2018 11:49:44 GMT

Hello,

The fds module should work without the softdevice as well. Just make sure to include the correct fstorage files (that are used by the fds files).

There are two fstorage.c files. One called fstorage.c, and one called fstorage_nosd.c (no softdevice). Use the last one.

Your compiler error, "initializer element is not constant" is probably because you are trying to add

ret_code_t ret = fds_register(fds_evt_handler);

outside a function.

These instructions can't be copy-pasted into a main.c file. You must have all function calls inside a function, e.g. your main() function, or another function that you create. Something like this:

static void fds_evt_handler(fds_evt_t const * p_fds_evt)
{
    switch(p_fds_evt->id)
    {
        case FDS_EVT_INIT:
            if(p_fds_evt->result != FDS_SUCCESS)
            {
                // initialization failed.
            }
            break;
        
        default:
            break;
    }
}

void my_fds_init_function(void)
{
    ret_code_t ret = fds_register(fds_evt_handler);
    if(ret != FDS_SUCCESS)
    {
        //registering failed. 
    }
    ret = fds_init();
    if(ret != FDS_SUCCESS)
    {
        // Handle error.
    }
}

BR,

Edvin

RE: flashwrite persistence

paul_tanner — Fri, 07 Dec 2018 15:15:34 GMT

straight armgcc

RE: flashwrite persistence

Edvin — Fri, 07 Dec 2018 15:04:15 GMT

What IDE are you using?

RE: flashwrite persistence

paul_tanner — Fri, 07 Dec 2018 09:43:59 GMT

OK Thx Edvin. I guess I saw flashwrite and not fds in the 12.3 examples and jumped to a conclusion. :-(

I see that 12.3 does include the fds library so I made an example using the document you mention.

The example talks about softdevice but I assume it should work without one.

The first error I get is

../../../main.c:77:18: error: initializer element is not constant

ret_code_t ret = fds_register(fds_evt_handler);

.. which seems odd. Is this code viable in 12.3 with the 12.3 fds library?

Thx.

RE: flashwrite persistence

Edvin — Thu, 06 Dec 2018 14:32:50 GMT

Hello,

The flash works in the way that you can only flip bits from 1 to 0. In order to flip them back to 1, you need to delete the entire flash page, unfortunately. This means that you need to somehow work around this, by figuring out where your latest data is written.

One way to work around this is to use the FDS module, which stores records with record IDs, which you can use to update a record, delete records, or write new records.

You can check out the guide in or documentation on how to use the FDS module.

So there you would typically use functions like fds_record_write(), fds_record_delete(), fds_record_update(), and so on. The FDS module will also evenly distribute the flash tear, so it will ensure maximum durance for the flash.

Best regards,

Edvin

RE: flashwrite persistence

paul_tanner — Thu, 06 Dec 2018 12:38:30 GMT

Sorry, something I did not try was to re-instate the call to flash_page_erase(addr);

That makes the sketch work but of course this prevents it from persisting across a reset.