S120 Persistent storage initial clear command never executes

RE: S120 Persistent storage initial clear command never executes

Hung Bui — Wed, 25 Feb 2015 10:06:25 GMT

Hi Leon,

I would suggest you to go through some steps for debugging:

For S120 v1.0 that you got a disconnection after 1 minute:

Get a sniffer trace to see what happens over the air.
Add a break point when the disconnected event occurs and check what the reason of the disconnection.

For the S120 v2.0:

Try to avoid device manager to erase the bond information, so you don't have the queue for pstorage, or you can manually remove the check for count in pstorage_access_status_get(&count); in scan_start().

You can also test pstorage by creating a fresh project and only test pstorage if you can erase & write something to flash.

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Tue, 24 Feb 2015 12:22:35 GMT

I can understand that you have not tested it on older hardware. However I would like to gain some insight about what can be done because as it happens we have that hardware. We are inquiring with RF Digital if they have more recent hardware in the models sold at the moment. Until then I must do with what I have. I have a working application on the same hardware with softdevice 1.01. That would be the end of it if not for the fact that this version breaks the connection after 1 minute. So if you can help get that resolved, I am happy too. Still there must be something you can tell me why the same code (except for the necessary changes) would make it possible to scan for devices on s120 v1 and not on v2. It looks like I am not getting any events from the softdevice. I suspect something with the vector table but I cannot find what I should add or change to get it working.

RE: S120 Persistent storage initial clear command never executes

Hung Bui — Thu, 19 Feb 2015 16:17:38 GMT

@Leon: For the differences between S120 v2.0 vs S110 v1.0 you can have a look at the release note in the S120 v2.0 zip file.

We haven't tested the S120 on XLR1 so we actually don't know about the behaviour when you run S120 on the chip. Some functions may work some may not, and glitch may occurs at some point when running.

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Wed, 18 Feb 2015 15:45:43 GMT

Tried setting clear_persistent_data = false to no avail. It seems I am not getting any callbacks from the softdevice. Can that be?

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Wed, 18 Feb 2015 14:58:40 GMT

Still I would like answers to the questions above. If possible I will move to newer versions of the chip, but for now I am just interested in getting the job done. My most pressing question is where do s120v1.01 and s120 v2.0 differ because I can get scanning to work with s120 v1.01.

RE: S120 Persistent storage initial clear command never executes

Hung Bui — Wed, 18 Feb 2015 14:54:43 GMT

Hi Leon,

As I mentioned earlier, if you avoid the button 1 (Bond erase button) being set, you should be able to skip the pstorage bond erasing (this part of the code in device_manager_init() // Clear all bonded devices if user requests to. init_param.clear_persistent_data = ((nrf_gpio_pin_read(BOND_DELETE_ALL_BUTTON_ID) == 0)? true: false);

Then you can try to use the S120 to scan, connect, read attribute as you want. But there is no guarantee that the S120 stack would work properly on your XLR1 chip. I would suggest you to get hold of new development kit, such as the nRF51 DK which has XLR3+.

XLR1 is discontinuted and for production you will need to use XLR3 anyway.

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Wed, 18 Feb 2015 10:50:15 GMT

On second thought, with s120 v1.01 scanning works and in v1.01 pstorage and device manager are already used. So what makes it different s120 v2.0?

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Tue, 17 Feb 2015 15:09:39 GMT

nrfjprog.exe --memrd 0x1000005c, returns FFFF001D which suggests it is a revision 1 chip. So if I understand you correctly, I will not be able to get this to work correctly. I would be happy if you could help me get things working correctly with either s120 v1.01 or v2.0. I do not require much, just be able to scan and connect and read/write 2 attributes. As I already mentioned, everything works fine on s120 v1.01 except that the connection resets after 1 minute (connection parameters negotiation ??) Could I do without pstorage?

RE: S120 Persistent storage initial clear command never executes

Hung Bui — Tue, 17 Feb 2015 14:56:01 GMT

Hi Leon,

I would suggest you to also post the question on http://forum.rfduino.com/

If the chip inside the module 's the first version of the chip (XLR1) it won't work properly with S120. You can have a look at this matrix table. To be able to know which chip version the board is you can use nrfjprog with this command: nrfjprog.exe --memrd 0x1000005c It will readout the HWID that you can find at Table 2 in the matrix table pdf file.

Do you have any problem running the S120 without holding the bond erase button (no page erasing will be queued) ?

I would suggest you to make some simple test with pstorage to see if you can write & erase a page.

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Tue, 17 Feb 2015 14:18:38 GMT

In my application a RFDigital 22301module is used. I cannot read the markings unless I open one. With S120 v1.01 everything works except that the connection is dropped after 1 minute. So I thought it best to move to v2.0. I have not tested pstorage with s110.

RE: S120 Persistent storage initial clear command never executes

Hung Bui — Tue, 17 Feb 2015 14:07:24 GMT

@Leon: Which board are you testing on ? Could you read the laser marking on top of the chip ? Would the S120 run if you don't press button 1 (no flash erasing) when booting up ? Have you experience any issue with the examples for S110 ?

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Mon, 16 Feb 2015 15:45:43 GMT

I made an error in the build. I can flash now and debug. It turns out that this results in exact the same error!

In scan_start, pstorage_access_status_get(&count) returns count=1. And also no sys_evt NRF_EVT_FLASH_OPERATION_SUCCESS or NRF_EVT_FLASH_OPERATION_ERROR occurs

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Mon, 16 Feb 2015 15:38:12 GMT

Thank you for looking into this.

I have copied the ble_app_hrs_c project from the SDK I copied the include files from S120 include folder to the project include folder for s120 I changed device_manager_central because the interface for sd_ble_gatts_sys_attr_set /get has changed. I have added value 0 as last parameter. I have added call to sd_ble_enable in main\ble_stack_init and changed the SOFTDEVICE_HANDLER_INIT to use my clock I have also added app_scheduler to the project (was missing).

I cannot flash this project from Keil. Using NrfGo shows why

I made no other changes than the ones mentioned above. The same holds for my actual project. I just added my application code.

Hope you can help me

RE: S120 Persistent storage initial clear command never executes

Hung Bui — Mon, 16 Feb 2015 13:37:07 GMT

@Leon: Do you have the same issue when testing with our stock example (ble_app_hrs_c project for example) ?

When holding button 1 when start up, we will try to clear the bond information page. There should be an system event after the page is erased. As I'm testing here I got an system event back (pstorage_sys_event_handler()) with NRF_EVT_FLASH_OPERATION_SUCCESS code and op_code = 0x04 means PSTORAGE_CLEAR_OP_CODE.

And the nRF51 continued to scan and report the advertising packet back.

Please make sure you have update the API header files for S120 v2.0 to the SDK. Because SDK v6.x came with the API for the S120 v1.0.

RE: S120 Persistent storage initial clear command never executes

Leon Schmetz — Mon, 16 Feb 2015 10:06:17 GMT

static void scan_start(void) { uint32_t err_code; uint32_t count; // Verify if there is any flash access pending, if yes delay starting scanning until // it's complete.

  err_code = pstorage_access_status_get(&count);
  APP_ERROR_CHECK(err_code);

if (count != 0)
{
    m_memory_access_in_progress = true;
    return;
}
	
err_code = sd_ble_gap_scan_start(&m_scan_param);
APP_ERROR_CHECK(err_code);

}

/**@brief Function for initializing the BLE stack. *

@details Initializes the SoftDevice and the BLE event interrupt. */ static void ble_stack_init(void) { uint32_t err_code; ble_enable_params_t ble_enable_params;

// Initialize the SoftDevice handler module. //SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, false); //SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, false); SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, true);

// Enable BLE stack memset(&ble_enable_params, 0, sizeof(ble_enable_params)); ble_enable_params.gap_enable_params.role = BLE_GAP_ROLE_CENTRAL; ble_enable_params.gatts_enable_params.service_changed = 0; err_code = sd_ble_enable(&ble_enable_params); APP_ERROR_CHECK(err_code);

// Register with the SoftDevice handler module for BLE events. err_code = softdevice_ble_evt_handler_set(ble_evt_dispatch); APP_ERROR_CHECK(err_code);

// Register with the SoftDevice handler module for System events. err_code = softdevice_sys_evt_handler_set(sys_evt_dispatch); APP_ERROR_CHECK(err_code); }

/**@brief Function for initializing the Device Manager. *

@details Device manager is initialized here. */ static void device_manager_init(void) { dm_application_param_t param; dm_init_param_t init_param;

uint32_t err_code;

err_code = pstorage_init(); APP_ERROR_CHECK(err_code);

// Clear all bonded devices if user requests to. init_param.clear_persistent_data = true; // ((nrf_gpio_pin_read(BOND_DELETE_ALL_BUTTON_ID) == 0)? true: false);

err_code = dm_init(&init_param); APP_ERROR_CHECK(err_code);

memset(&param.sec_param, 0, sizeof (ble_gap_sec_params_t));

// Event handler to be registered with the module. param.evt_handler = device_manager_event_handler;

// Service or protocol context for device manager to load, store and apply on behalf of application. // Here set to client as application is a GATT client. param.service_type = DM_PROTOCOL_CNTXT_GATT_CLI_ID;

// Secuirty parameters to be used for security procedures. param.sec_param.bond = SEC_PARAM_BOND; param.sec_param.mitm = SEC_PARAM_MITM; param.sec_param.io_caps = SEC_PARAM_IO_CAPABILITIES; param.sec_param.oob = SEC_PARAM_OOB; param.sec_param.min_key_size = SEC_PARAM_MIN_KEY_SIZE; param.sec_param.max_key_size = SEC_PARAM_MAX_KEY_SIZE; param.sec_param.kdist_periph.enc = 1; param.sec_param.kdist_periph.id = 1;

err_code = dm_register(&m_dm_app_id,&param); APP_ERROR_CHECK(err_code); }

/**@brief Initialize the scheduler. */

static void scheduler_init(void) { APP_SCHED_INIT(SCHED_MAX_EVENT_DATA_SIZE, SCHED_QUEUE_SIZE); }

/**@brief Function for application main entry. */ int main(void) { uint32_t err_code; memset(m_dlt_list, 0, sizeof(m_dlt_list));

// Initialization of various modules.
scheduler_init();

ble_stack_init();
client_handling_init();
device_manager_init();

	err_code = serial_port_init(on_serial_message);

  for (;;)
{
    app_sched_execute();
			err_code = sd_app_evt_wait();
    APP_ERROR_CHECK(err_code);
}

}