Problem with fds: Flash read, write, delete calling that function using android phone.

[vishal]

Hello to all,

I am using nRF52832 DK with sd132, v6.0.0 and sdk 15.0.0, segger embedded studio. We want to achieve change application timer time (APP_TIMER_TICKS(update_time)) using android phone. We have a sensor devices it will wake up as per app timer time defined, we want to change this wake up time using Noridc UART tool box app. For that we are using fds example as referred in given sdk 15.0 and other nRF5-flash-storage-examples .

We are able to flash write read and delete but problem is:

1.  When i call fds_test_find_and_delete(), fds_test_write(), fds_read() whenever received command from nordic UART app it not able to read and write at this time.
2. I want to change update_time variable of app timer ticks using android phone and store this time in flash. Whenever want to user need to change this time first delete previous and update latest send time. 
3. Will you please provide me program snippet for How i call flash fds API through android phone and store received time in that app_timer ticks. Confused regarding this.

I am currently using this following functions for FDS read, write, and delete:

static ret_code_t fds_test_write(void)
{
		
    //static uint32_t const m_deadbeef[2] = {0xDEADBEEF,0xBAADF00D};
    static uint8_t const m_deadbeef[1] = {0x14};
//    memcpy(m_deadbeef, write_data, sizeof(m_deadbeef));
    fds_record_t        record;
    fds_record_desc_t   record_desc;

    // Set up data.
    
    // Set up record.
    record.file_id        = FILE_ID_FDS_TEST;
    record.key            = REC_KEY_FDS_TEST;
    record.data.p_data    = &m_deadbeef;
    //record.data.length_words   = sizeof(m_deadbeef)/sizeof(uint32_t);
    record.data.length_words   = sizeof(m_deadbeef)/sizeof(uint8_t);
                    
    ret_code_t ret = fds_record_write(&record_desc, &record);
    if (ret != FDS_SUCCESS)
    {
                    return ret;
    }
     NRF_LOG_INFO("Writing Record ID = %d \r\n",record_desc.record_id);
    return NRF_SUCCESS;
}

static ret_code_t fds_read(void)
{

    fds_flash_record_t  flash_record;
    fds_record_desc_t   record_desc;
    fds_find_token_t    ftok ={0};//Important, make sure you zero init the ftok token
    //uint32_t *data;
    uint8_t *data;
    uint32_t err_code;
    
    NRF_LOG_INFO("Start searching... \r\n");
    // Loop until all records with the given key and file ID have been found.
    while (fds_record_find(FILE_ID_FDS_TEST, REC_KEY_FDS_TEST, &record_desc, &ftok) == FDS_SUCCESS)
    {
                    err_code = fds_record_open(&record_desc, &flash_record);
                    if ( err_code != FDS_SUCCESS)
                    {
                            return err_code;		
                    }
                    
                    NRF_LOG_INFO("Found Record ID = %d\r\n",record_desc.record_id);
                    NRF_LOG_INFO("Data = ");
                    //data = (uint32_t *) flash_record.p_data;
                    data = (uint8_t *) flash_record.p_data;
                    for (uint8_t i=0;i<flash_record.p_header->length_words;i++)
                    {
                            NRF_LOG_INFO("0x%8x ",data[i]);
                    }
                    NRF_LOG_INFO("\r\n");
                    // Access the record through the flash_record structure.
                    // Close the record when done.
                    err_code = fds_record_close(&record_desc);
                    if (err_code != FDS_SUCCESS)
                    {
                            return err_code;	
                    }
    }
    return NRF_SUCCESS;
		
}


static ret_code_t fds_test_find_and_delete (void)
{
    fds_record_desc_t   record_desc;
    fds_find_token_t    ftok;

    ftok.page=0;
    ftok.p_addr=NULL;
    // Loop and find records with same ID and rec key and mark them as deleted. 
    while (fds_record_find(FILE_ID_FDS_TEST, REC_KEY_FDS_TEST, &record_desc, &ftok) == FDS_SUCCESS)
    {
        fds_record_delete(&record_desc);
        NRF_LOG_INFO("Deleted record ID: %d \r\n",record_desc.record_id);
    }
    // call the garbage collector to empty them, don't need to do this all the time, this is just for demonstration
    ret_code_t ret = fds_gc();
    if (ret != FDS_SUCCESS)
    {
        return ret;
    }
    return NRF_SUCCESS;
}

[Edvin]

awneil is correct. The FDS is the easiest to use, as it will manage the flash wear leveling.

You need to set up a ble link, like the ble_app_uart example. Then, when you receive a message, instead of forwarding it to the UART, you do the flash operations that you want to do instead. 

The protocol that you use, you must implement  yourself, and use in the application.

 

Best regards,

Edvin

[vishal]

Thanks Edvin,

I have used FDS library and able to flash write and delete data when message received from ble_app_uart.

But problem getting for read function: I am write this data  const m_deadbeef = 0xDEADBEEF;

When i call read function after write event generated got this data in read function: "0x      EF"

Why not getting all write hex data?

Also will you please tell me how i can write integer value instead of this hex data? 

Thanks in advanced,....!!!

[Edvin]

Hello,

 

The issue is that you cast the flash_record.p_data to a uint8_t, while it is really a uint32_t pointer.

Try the fds_read function looking something like this:

void fds_test_read(void)
{
    ret_code_t err_code = FDS_SUCCESS;
    fds_flash_record_t  flash_record;
    fds_record_desc_t   record_desc;
    fds_find_token_t    ftok;
    memset(&ftok, 0x00, sizeof(fds_find_token_t));
    
    while (fds_record_find(FILE_ID, RECORD_KEY_1, &record_desc, &ftok) == FDS_SUCCESS)
    {
        err_code = fds_record_open(&record_desc, &flash_record);
        if (err_code != FDS_SUCCESS)
        {
            // Handle error
            printf("fds_record_open error %d\r\n", err_code);
        }
        // Access the record through the flash_record structure
        // Close the record when done.
        err_code = fds_record_close(&record_desc);
        if(err_code != FDS_SUCCESS)
        {
            // Handle error
            printf("fds_record_close err_code %d\r\n", err_code);
        }
        uint32_t *data = (uint32_t *) (flash_record.p_data);
        printf("record found:\r\n");
        printf("%08x\r\n", *data);
        
    }
}

Of course, use the NRF_LOG_INFO instead of printf. I just started implementing this to the SDK15\examples\peripheral\uart example, so printf was already set up.

 

You can write int values instead of hex values. Just create an int variable when you write, which you pass the pointer to into the fds_write function:

record.data.p_data = &m_my_variable;

The same goes when you read out the variable. Remember that all you read is a register in flash. If I stored an int (int32_t) instead hexadecimal, I would write something like this:

 

int32_t *data = (int32_t *)(flash_record.data);

NRF_LOG_INFO("%d", *data);

And the data will be printed as a number instead of hexadecimal values.

 

Best regards,

Edvin

[vishal]

Sorry for late response...!!

We were explored other thing to get more advanced features in our current application. So now i have tested this as you provided above program snippet and it is working able to read proper value as flash on this address. But still got one problem which is

When i connect my phone to DK and send read command like "r" to DK and call "fds_test_read()" but it stuck and when i disconnect BLE connection then got read data LOG on terminal as write last time.

Is any problem with BLE activity connected to device and call flash read function. Because i got read data log after disconnect BLE connection. As i read here he said It is fully possible to read/write to flash when you are in a BLE connection. But i got problem with read function while connected BLE, Is any other configuration to need to enable in sdk_config.h file.

Thank you so much....!!

[awneil]

are you suffering from this bug:

https://devzone.nordicsemi.com/f/nordic-q-a/34666/nrf5-sdk-v15-0-0-bug-report-incorrect-use-of-nrf_log_process-in-ble_app_uart-peripheral-example-among-others