NRF_FSTORAGE_DEF address defined issue with 14.1.0

[edmond.yun]

Hello,

I have some trouble to use fstorage function with dfu function, please help to let me know the solution in order to solve the following issues,

thankful for your support in advance,

thanks.

1. the method to define the start/end address in NRF_FSTORAGE_DEF,

when checking the memory map with DFU, I can see the memory map with the following link,

infocenter.nordicsemi.com/index.jsp

it means that I need to store data (user data) between the address defined with DFU_APP_DATA_RESERVED and 0x07b000.

in components/libraries/bootloader/dfu/nrf_dfu_types.h,

/** @brief  Size of the flash space reserved for application data.
 */
#ifndef DFU_APP_DATA_RESERVED
#define DFU_APP_DATA_RESERVED               CODE_PAGE_SIZE * 8//love_0130
#endif

CODE_PAGE_SIZE is 0x1000,

so, in this case, I can calculate for start address, it is 0x07b000 - 0x8000, so 0x73000. is it right ?

so I updated the address in my code, please refer it, and help to let me know what problem is, currently, I got the following error,

Error is,

nrf_fstorage_erase => NRF_ERROR_INVALID_ADDR (number : 16) nrf_fstorage_read ==> can't read any data, nrf_fstorage_write => NRF_ERROR_INVALID_LENGTH (number : 9)

what is problem ?

Code is,

please point out the problem with code, I updated the similar issues for many times, really, I need your help to separate correctly issue and to solve in code, thankful for your support in advance,

#include <stdint.h>
#include <stdbool.h>
#include <string.h>

#include "nrf.h"
#include "nrf_soc.h"
#include "nordic_common.h"
#include "boards.h"
#include "app_timer.h"
#include "app_util.h"
#include "nrf_fstorage.h"

#include "nrf_sdh.h"
#include "nrf_sdh_ble.h"
#include "nrf_fstorage_sd.h"

#include "nrf_log.h"
#include "nrf_log_ctrl.h"
#include "nrf_log_default_backends.h"

#define FLASHWRITE_EXAMPLE_MAX_STRING_LEN       (62u)
#define FLASHWRITE_EXAMPLE_BLOCK_VALID          (0xA55A5AA5)
#define FLASHWRITE_EXAMPLE_BLOCK_INVALID        (0xA55A0000)
#define FLASHWRITE_EXAMPLE_BLOCK_NOT_INIT       (0xFFFFFFFF)

//love_1211
//refer to infocenter.nordicsemi.com/index.jsp

static void fstorage_evt_handler(nrf_fstorage_evt_t * p_evt)
{
	if (p_evt->result != NRF_SUCCESS)
	{
		printf("--> Event received: ERROR while executing an fstorage operation. \r\n");
		return;
	}
	
	switch (p_evt->id)
	{
		case NRF_FSTORAGE_EVT_WRITE_RESULT:
		{
			printf("--> Event received: wrote %d bytes at address 0x%x. \r\n",
			 p_evt->len, p_evt->addr);
		} break;
		
		case NRF_FSTORAGE_EVT_ERASE_RESULT:
		{
			printf("--> Event received: erased %d page from address 0x%x. \r\n",
			 p_evt->len, p_evt->addr);
		} break;
		
		default:
		break;
	}
}

NRF_FSTORAGE_DEF(nrf_fstorage_t fstorage) =
{
    /* Set a handler for fstorage events. */
    .evt_handler = fstorage_evt_handler,

    /* These below are the boundaries of the flash space assigned to this instance of fstorage.
     * You must set these manually, even at runtime, before nrf_fstorage_init() is called.
     * The function nrf5_flash_end_addr_get() can be used to retrieve the last address on the
     * last page of flash available to write data. */
    .start_addr = 0x78000, // by 0x800000
    .end_addr   = 0x7F000,
};


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

/**@brief   Helper function to obtain the last address on the last page of the on-chip flash that
 *          can be used to write user data.
 */
static uint32_t nrf5_flash_end_addr_get()
{
    uint32_t const bootloader_addr = NRF_UICR->NRFFW[0];
    uint32_t const page_sz         = NRF_FICR->CODEPAGESIZE;
    uint32_t const code_sz         = NRF_FICR->CODESIZE;

    return (bootloader_addr != 0xFFFFFFFF ?
            bootloader_addr : (code_sz * page_sz));
}

static void print_flash_info(nrf_fstorage_t * p_fstorage)
{
    printf("========| flash info |========\r\n");
    printf("erase unit: \t%d bytes\r\n",      p_fstorage->p_flash_info->erase_unit);
    printf("program unit: \t%d bytes\r\n",    p_fstorage->p_flash_info->program_unit);
    printf("==============================\r\n");
}

void wait_for_flash_ready(nrf_fstorage_t const * p_fstorage)
{
    /* While fstorage is busy, sleep and wait for an event. */
    while (nrf_fstorage_is_busy(p_fstorage))
    {

    }
}

void flash_test(void)
{//nrfjprog --memrd 0x0007F000 --n 0x70  nrfjprog --memrd 0x10000010 --n 0x10
	ret_code_t rc;
	
	nrf_fstorage_api_t * p_fs_api;
//	static uint32_t pages_to_erase = 1;
	
	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;
	
	rc = nrf_fstorage_init(&fstorage, p_fs_api, NULL);
	APP_ERROR_CHECK(rc);
	
	print_flash_info(&fstorage);
	
	/* It is possible to set the start and end addresses of an fstorage instance at runtime.
	* They can be set multiple times, should it be needed. The helper function below can
	* be used to determine the last address on the last page of flash memory available to
	* store data. */
	(void) nrf5_flash_end_addr_get();
	
	rc = nrf_fstorage_erase(
		&fstorage,   /* The instance to use. */
		fstorage.start_addr,     /* The address of the flash pages to erase. */
		pages_to_erase, /* The number of pages to erase. */
		NULL            /* Optional parameter, backend-dependent. */
	);
	APP_ERROR_CHECK(rc);

	wait_for_flash_ready(&fstorage);
	NRF_LOG_INFO("Done.");
    
	uint8_t    flash_data2[4] = {0};
	rc = nrf_fstorage_read(&fstorage, 0x78100, flash_data2, sizeof(flash_data2));
	APP_ERROR_CHECK(rc);
        printf("\r\nread %s \r\n", flash_data2);
        	    
	/* Let's write to flash. */
	printf("Writing \"%x\" to flash.", m_data);
	rc = nrf_fstorage_write(&fstorage, 0x78100, &m_data, sizeof(m_data), NULL);
	APP_ERROR_CHECK(rc);
	
	wait_for_flash_ready(&fstorage);
	NRF_LOG_INFO("Done.");
                   
}

thanks.

[edmond.yun]

and there is a question : if using fds module, the user data can be preserved after doing dfu, is it right ? the data is stored in app data region of memory map.... where is located(saved) the data in memory map ? is app data ? I would like to preserve the user data after doing dfu, if so, need to use app data ? is it right ? please help to let me know the method...

[edmond.yun]

hi, Sigurd,

I am very thankful for your concern and propose....

I check DFU_APP_DATA_RESERVED  and I can modify and test the region of app data with fstorage function : start address is under 0x7b000 - 0x1000(4k byte) * the number of DFU_APP_DATA_RESERVED page... is it right ?

if right, but the result is failed, please help to provide the example and guide with detailed instruction and description,

I already provided my code,...

thanks.

[Sigurd]

edmond.yun said:

start address is under 0x7b000 - 0x1000(4k byte) * the number of DFU_APP_DATA_RESERVED page... is it right ?

Yes, that should be right. The end address should be 0x78000 for the regular bootloader_secure_ble example, but for the debug version it should be  0x73000. Note that in the code you posted, you have start at 0x78000 and end at 0x7F000.

[edmond.yun]

Hello, Sigurd,

thankful for detailed information, I will experiment by referring your opinion, and then I will update the result... maybe in early next week, because Korea has New year's day...

and Could you please kindly review the similar issue in other posts ?

https://devzone.nordicsemi.com/f/nordic-q-a/30324/the-inquiry-for-the-usage-of-fds-function-fstorage

I updated all things that I should know in order to use fds and fstorage normally for mass-production,

please help me..kindly, need to get confirmation and usage with detailed guide or code.

thankful for your support in advance,

thanks.

[edmond.yun]

Hello, Sigurd,

I tried to experiment your opinion today, but the result is not good, I can't see normal output as to read/writing data in flash with fstorage function, and I would like to double-check the memory map with you... please refer the following link,

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v14.2.0%2Flib_bootloader_dfu_banks.html&cp=4_0_0_3_5_1_2_2&anchor=lib_bootloader_dfu_appdata

I can't understand why the end address should be 0x78000 in dfu case, when checking above link, it seems to be 0x7d000, is it right ? and if possible, Could you please kindly provide the detailed guide to check it ? I need to know the method to experiment all cases (dfu/ no-dfu) with detailed information ...

thankful for your support in advance,

thanks.