RE: understanding app_timer functionality

Ole Bauck — Mon, 03 Oct 2016 09:37:23 GMT

Error code 0x3202 is BLE_ERROR_GAP_INVALID_BLE_ADDR (NRF_GAP_ERR_BASE + 0x0002 = NRF_ERROR_STK_BASE_NUM + 0x0200 + 0x002 = 0x3000 + 0x0200 + 0x0002). And as the description says: "The upper two bits of the address do not correspond to the specified address type."

RE: understanding app_timer functionality

Amit Chahar — Sat, 01 Oct 2016 13:16:46 GMT

Regarding 4th point, I tried to debug and I am getting error code : 0x00003202 I get this error while setting the RPA : sd_ble_gap_address_set() I mentioned in this post, how I am setting the RPA : setting RPA

RE: understanding app_timer functionality

Ole Bauck — Wed, 28 Sep 2016 14:33:22 GMT

Hi,

The app_timer library will not check if the LFCLK is running. You will be able to initialize and create a timer without having started the LFCLK. You are also able to call the start and stop functions also, but the RTC will not start counting as it has no clock source running.
If you call timers_init() after buttons_leds_init(..), then bsp_init(..) inside buttons_leds_init(..) will return NRF_ERROR_INVALID_STATE as app_timer module is not initialized. Since you have not defined DEBUG globally, your application will restart when calling APP_ERROR_CHECK(err_code). See here for more info about why your application is resetting.
The minimum advertising interval is 20ms (see BLE_GAP_ADV_INTERVAL_MIN and here), so you will get an error (and reset) if you try to set it lower than that.
This output also indicates that you reset. Probably you get an error when you try to set the address. Define DEBUG in your preprocessor symbols, go into debug and see where the error come from and which error code it is (here is a list of SoftDevice global error codes). You can put a breakpoint in the while loop in app_error_save_and_stop(..) in app_error.c to get this information (after the code hits the breakpoint).

Ole