Combine BLE_UART and flash fstorage code

RE: Combine BLE_UART and flash fstorage code

Susheel Nuguru — Sat, 29 Jul 2023 08:47:18 GMT

closing this as the rest of the questions will be answered in your other ticket

RE: Combine BLE_UART and flash fstorage code

DG — Tue, 25 Jul 2023 12:48:36 GMT

Hi Terje,

I am writting data on flash using this function nrf_fstorage_write(&fstorage,start_address,name,len_data,NULL) and reading data from flash using
this function nrf_fstorage_read(&fstorage,start_address,&newname,read_data_len) and Erase data using this function nrf_fstorage_erase(&fstorage,strat_add,1, NULL) where 1 is page number ,

uint8_t flash_buff[100]="6B9591A39B3B35118C6F9754EDD1C0309073";

1. i am writting flash_buffer data 160 times using write function
2. i am readding data 160 time using read function
3. i erase data 160 times using erase function
4 after erase data i read again no data found in this address

my problem is i write 200 times same and read 200 times and erase 200 times after erasing data. i read again data so i got some data but how its possible because i erase data

my start_address is 0x3e000 and last address is 0x6ffff.

uint32_t result_erase = nrf_fstorage_erase(&fstorage,strat_add,1, NULL); // erase 1 page
uint32_t result_erase1 = nrf_fstorage_erase(&fstorage,strat_add,2, NULL);
uint32_t result_erase2 = nrf_fstorage_erase(&fstorage,strat_add,3, NULL);
uint32_t result_erase3 = nrf_fstorage_erase(&fstorage,strat_add,4, NULL);
uint32_t result_erase4 = nrf_fstorage_erase(&fstorage,strat_add,5, NULL);

can you guide me why i am getting data after erase ?

RE: Combine BLE_UART and flash fstorage code

tesc — Wed, 19 Jul 2023 16:17:07 GMT

Hi,

I have provided an answer for the fstorage related question. For these UART related questions, that are completely different from the original question in this thread, please create a new ticket. That way the question will be directly related to the subject, which is better for helping others with similar questions in the future, as well as the case will be assigned to an application engineer with better knowledge of UART, for following up. The opening question in this thread was directly related to fstorage, and general UART operation deserves to be its own topic.

Regards,
Terje

RE: Combine BLE_UART and flash fstorage code

tesc — Wed, 19 Jul 2023 16:14:45 GMT

Hi,

The maximum end address depend on the amount of flash on the SoC, which in case of the nRF52832 is 256 kB or 512 kB (depending on function variant). For nRF52840 it is 1 MB. To get the last address on the last page of writable flash, you can use nrf5_flash_end_addr_get().

Please note that depending on the flash layout on your device, the last pages may be used for other purposes and the end address should be adjusted accordingly. Also, if you use Flash Data Storage this will typically use a number of flash pages at the end of flash, and other uses of fstorage should then stay away from that area. There is a good overview of typical flash usage patterns in the Memory layout section of the Bootloader documentation.

To get more flash space for fstorage, you should typically change the start address, and not the end address, since the free free flash space is typically before the existing allocation, and not after.

Regards,
Terje

RE: Combine BLE_UART and flash fstorage code

DG — Wed, 12 Jul 2023 09:49:22 GMT

Hi Terje ,

if i will use cli_init(), cli_start(),cli_process() , API in BLE_UART code to print data on putty terminal but getting error can you guide me why i am getting this error .error show in below picture and i change uart pin also but getting same error.

void cli_init(void)
{
nrf_drv_uart_config_t uart_config = NRF_DRV_UART_DEFAULT_CONFIG;
//uart_config.pseltxd = TX_PIN_NUMBER;
uart_config.pseltxd = ARDUINO_SCL_PIN;
//uart_config.pselrxd = RX_PIN_NUMBER;
uart_config.pselrxd = ARDUINO_SDA_PIN;
uart_config.hwfc = NRF_UART_HWFC_DISABLED;

ret_code_t rc = nrf_cli_init(&m_cli_uart, &uart_config, true, true, NRF_LOG_SEVERITY_INFO);
APP_ERROR_CHECK(rc);
}

void cli_start(void)
{
ret_code_t rc = nrf_cli_start(&m_cli_uart);
APP_ERROR_CHECK(rc);
}

void cli_process(void)
{
nrf_cli_process(&m_cli_uart);
}

RE: Combine BLE_UART and flash fstorage code

DG — Wed, 12 Jul 2023 06:18:03 GMT

Hi Terje ,

Can you tell me what is the max.value of end_addr so i can write and read more data .

NRF_FSTORAGE_DEF(nrf_fstorage_t fstorage) =
{
/* Set a handler for fstorage events. */
.evt_handler = fstorage_evt_handler,
.start_addr = 0x3e000,
.end_addr = 0x3ffff,
};

RE: Combine BLE_UART and flash fstorage code

tesc — Tue, 11 Jul 2023 11:27:18 GMT

Hi,

The error message in the terminal output indicates that the source address is not word aligned. This is not clear from the documentation for nrf_fstorage_write(), which only states the alignment requirement for dest. I see from the implementation in nrf_fstorage.c that also p_src is checked for word alignment.

The variables used in the fstorage example are not necessarily word aligned for all toolchians. In order to ensure they are word aligned, add __ALIGN(4) in front of the declarations. For the fstorage example, this means changing from:

/* Dummy data to write to flash. */
static uint32_t m_data = 0xBADC0FFE;
static char m_hello_world[] = "hello world";

To:

/* Dummy data to write to flash. */
__ALIGN(4) static uint32_t m_data = 0xBADC0FFE;
__ALIGN(4) static char m_hello_world[] = "hello world";

Please note also that for writing to flash, the values written must be in static variables. This is because flash writes are asynchronous; the operation is put in a queue, and will be executed at a later point in time. This means the source for the data to be written must stay in memory (and not be overwritten or changed) until the write operation is finished.

If the above does not solve the issue, please note you should also make sure to use the correct backend for fstorage, depending on whether or not the SoftDevice is used. The flash_fstorage example uses the following code for initializing with the correct backend:

    nrf_fstorage_api_t * p_fs_api;

#ifdef SOFTDEVICE_PRESENT
    NRF_LOG_INFO("SoftDevice is present.");
    NRF_LOG_INFO("Initializing nrf_fstorage_sd implementation...");
    /* Initialize an fstorage instance using the nrf_fstorage_sd backend.
     * nrf_fstorage_sd uses the SoftDevice to write to flash. This implementation can safely be
     * used whenever there is a SoftDevice, regardless of its status (enabled/disabled). */
    p_fs_api = &nrf_fstorage_sd;
#else
    NRF_LOG_INFO("SoftDevice not present.");
    NRF_LOG_INFO("Initializing nrf_fstorage_nvmc implementation...");
    /* Initialize an fstorage instance using the nrf_fstorage_nvmc backend.
     * nrf_fstorage_nvmc uses the NVMC peripheral. This implementation can be used when the
     * SoftDevice is disabled or not present.
     *
     * Using this implementation when the SoftDevice is enabled results in a hardfault. */
    p_fs_api = &nrf_fstorage_nvmc;
#endif

    rc = nrf_fstorage_init(&fstorage, p_fs_api, NULL);
    APP_ERROR_CHECK(rc);

Regards,
Terje