Flash write

RE: Flash write

Peter — Mon, 18 Jul 2016 13:25:27 GMT

Hi Thomas,

Tested your code and works in raw mode for me. Did you try removing the line APP_ERROR_CHECK(result);

from your ota_callback?

RE: Flash write

Krishna Shingala — Wed, 12 Mar 2014 18:39:49 GMT

Thank you for the suggested improvement in documentation Thomas, yes, agreed it should be added here. Will be done in subsequent SDK release.

Thanks again!

Regards, Krishna

RE: Flash write

thomas — Tue, 11 Mar 2014 11:15:58 GMT

Hi,

In fact, i forgot to register for system events....Tanks for help. Maybe this information ca be added to pstorage documentation page : https://devzone.nordicsemi.com/documentation/nrf51/5.1.0/html/a00131.html

RE: Flash write

Krishna Shingala — Mon, 10 Mar 2014 19:49:18 GMT

Hi David,

I would like to mention that pstorage implements a queue as SoftDevice permits only one flash access operation pending at a time. Hence issuing back to back erase is not a problem if you are receiving system events from SoftDevice and passing it on the pstorage module. It is on this event that the module pops next operation (if any) in its queue.

Hence it is important that the procedures in the code snippet above are performed. Hope this helps!

Regards, Krishna

RE: Flash write

David Smoot — Mon, 10 Mar 2014 17:20:54 GMT

I might be wrong but I think maybe you are getting the same issue I was getting.

If I understand correctly, the calls to pstorage_raw_clear() and pstorage_raw_store() simply schedule an erase and a store respectively. So their return value just indicates that you scheduled an erase followed by a write.

In my case, I had to set up an event handler to get the event indicating the erase operation was successful and then call the function to schedule the write in order for the write to succeed. Not sure if this is what you are facing but I did notice you called an erase back to back with a write which was failing for me for the reason above. Hope this helps. David

RE: Flash write

Krishna Shingala — Thu, 06 Mar 2014 13:44:47 GMT

Hi Thomas,

Can you confirm you have registered for system events and are passing it on to pstorage module?

Below the code that may be useful you..!




/**@brief Function for dispatching a system event to interested modules.
 *
 * @details This function is called from the System event interrupt handler after a system
 *          event has been received.
 *
 * @param[in]   sys_evt   System stack event.
 */
static void sys_evt_dispatch(uint32_t sys_evt)
{
    pstorage_sys_event_handler(sys_evt);
}

/**@brief BLE stack initialization.
 *
 * @details Initializes the SoftDevice and the stack event interrupt.
 */
static void ble_ant_stack_init(void)
{
    // Initialize SoftDevice
    SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, false);
    
    // Subscribe for BLE events.
    uint32_t err_code = softdevice_ble_evt_handler_set(ble_evt_dispatch);
    APP_ERROR_CHECK(err_code);
    
    // Register with the SoftDevice handler module for BLE events.
    err_code = softdevice_sys_evt_handler_set(sys_evt_dispatch);
    APP_ERROR_CHECK(err_code);
}

Hope this helps!

Regards, Krishna

RE: Flash write

thomas — Thu, 06 Mar 2014 13:40:10 GMT

any help ?

RE: Flash write

thomas — Wed, 05 Mar 2014 11:50:16 GMT

I've tested with classic pstorage mode ( without raw mode) My pstorage callback is never executed .

RE: Flash write

thomas — Tue, 04 Mar 2014 16:42:18 GMT

Hi,

I'm using finally pstorage Raw mode. My app (bluetooth modules) works fine( no err_code, no crash, no hard fault)... But my pstorage callback is never executed...(debug led 1 never set). Does anyone know were it can come from ?


uint32_t		err_code;
uint8_t		ota_code[4]; 	
		
ota_code[0] = 0x81;
ota_code[1] = 0xAB;
ota_code[2] = 0xAC;
ota_code[3] = 0xAB;
		
		
pstorage_handle_t            handle;
pstorage_module_param_t            param;
uint32_t page_number = NRF_FICR->CODESIZE-30;
uint32_t page_base_address = (uint32_t) (page_number * NRF_FICR->CODEPAGESIZE);
		
param.block_size = 0x0010 ;
param.block_count = 1;
param.cb = ota_cb_handler;
		
handle.block_id = page_base_address; //bloc address
		
//registration
err_code = pstorage_raw_register(¶m, &handle);
APP_ERROR_CHECK(err_code);

handle.block_id = page_base_address; //definition de l'adresse du bloc

//clear
err_code = pstorage_raw_clear(&handle,0x0010);
APP_ERROR_CHECK(err_code);
				
//store
err_code = pstorage_raw_store(&handle,ota_code,4,0);
APP_ERROR_CHECK(err_code);

nrf_gpio_pin_set(LED_0); // debug led



static void ota_cb_handler(pstorage_handle_t  * handle,
                             uint8_t          	op_code,
                             uint32_t         	result,
                             uint8_t         		* p_data,
                             uint32_t         	data_len)
{
		
	APP_ERROR_CHECK(result);
	nrf_gpio_pin_set(LED_1);	//debug led													 
 }

RE: Flash write

thomas — Mon, 03 Mar 2014 17:58:02 GMT

Thanks

RE: Flash write

Krishna Shingala — Mon, 03 Mar 2014 17:53:34 GMT

Hi Thomas,

To give you an example, lets say you want to share bond information from application to boot-loader. Then this is what can be done:

a. Ensure that pstorage_platform file has been provided with same start address. Number of applications and end address could be adjusted if you need more persistent memory in boot-loader mode. b. Register bond related blocks in same order as in application mode once pstorage has been initialized.

If this is done, and your bootloader is not overriding or clearing any of flash pages reserved for storing data persistently, you should be able to share information from application to bootloader.

Regards, Krishna

RE: Flash write

thomas — Mon, 03 Mar 2014 17:46:18 GMT

Thanks for response ,

And for you , what is the best solution to share values between the main app and the bootloader (like a flag) ? The Raw mode ?

Regards,

Thomas

RE: Flash write

Krishna Shingala — Mon, 03 Mar 2014 17:03:59 GMT

Hi Thomas,

You should know that ble_flash module cannot be used when SoftDevice is enabled. This was done post SoftDevice 6.0.0 release, when flash access was offered as a part of SoftDevice functionality.

Also, in case you need the address, in pstorage block_id of pstorage_handle_t contains actual flash access. Accessing the flash access yourself is not recommended for typical use cases.

In case you do want to access all flash yourself, raw mode is appropriate. In this case, you need follow the following steps: a. Initilaize pstorage using pstorage_init(); b. Register the application in raw mode using the pstorage_raw_register() with appropriate parameters. You will provided a handle here. The module id in this handle identifies your application. Block id of the handle can be manipulated to any flash access to desire to access subsequently. c. Assign block_id field of the handle to an appropriate word aligned flash address (not page number). And call pstorage_raw_store. Do ensure that your source data lies in resident memory as flash access is no longer blocking.

For an example usage of raw mode, you can look at the boot-loader included in the SDK. This is the only application using raw mode.

Hope this helps!

Regards, Krishna

RE: Flash write

thomas — Mon, 03 Mar 2014 11:58:16 GMT

i'm calling ble_flash_page_write() just after the ble disconnect event and before to start advertisment.

I tried to use pstorage manager, but don't understand how to specify exactly were i want to write (i need to read this value from the bootloader or an external flasher..). Raw mode seems to be appropriate but i don't find documentation about this, just last lines of the pstorage lib documentation. https://devzone.nordicsemi.com/documentation/nrf51/5.1.0/html/a00131.html

RE: Flash write

Balaji Srinivasan — Mon, 03 Mar 2014 11:38:38 GMT

Hi Thomas,

Are you calling ble_flash_page_write() when you are in a connection (connected to a peer)? That could be a reason for hardfault. You can either call this API when not in a connection (if that suits your usecase). Or you can use the API ble_flash_word_write instead. (This assumes that the Flash location to be written has been erased previously)

It is recommended that you use the 'Persistent Storage Interface' (pstorage.h) instead of the 'Flash Manager' (ble_flash.h) to perform flash related operations. It has been added to the nRF51 SDK sicne version 5.0.0. It helps in handling asynchronous flash memory access without the application needing to know whether the radio is active (connected to the peer).

Cheers, Balaji