Restarted Timer is not executed for long time(S132)

RE: Restarted Timer is not executed for long time(S132)

FormerMember — Wed, 29 Mar 2017 11:17:30 GMT

Yes, I agree. In ble_app_template, services_init() should be placed before advertising_init() to take into account the cases where custom UUIDs are being used. In ble_app_uart, it is done like that. I will report it for improvement internally.

I don't know why the explicit setting for vendor specific UUIDs is removed in SDK 13, since almost all the other settings are kept. It could have been mentioned in the migration note..

RE: Restarted Timer is not executed for long time(S132)

Moritz — Tue, 28 Mar 2017 12:10:19 GMT

Thanks. Everyting works now. But I have one question and one suggestion.In your main you do advertising_init(); and then services_init(); If you have custom uuids you adv. the other way around is better. devzone.nordicsemi.com/.../ mentioned here. Maybe you can include that in the SDK13 examples. Or is there an explicit reason why you did it the other way around?

The other part is regarding the ble_stack_init(); Took me some time, to figure out I had to explicitely set ble_cfg.common_cfg.vs_uuid_cfg.vs_uuid_count = 1; otherwise I get a NRF_ERROR_NO_MEM In sd_ble_uuid_vs_add. In the SDK 12 example you didnt have to do that, and the code looks quite different. Is the only difference you dont get the default parameters and configure everything yourself?

Thanks a lot for your help!

RE: Restarted Timer is not executed for long time(S132)

Moritz — Thu, 23 Mar 2017 12:59:27 GMT

Ok I edited my post. Thanks for your help!

drive.google.com/open

RE: Restarted Timer is not executed for long time(S132)

Moritz — Thu, 23 Mar 2017 12:58:04 GMT

doesnt work one moment please Im uploading it to google drive

RE: Restarted Timer is not executed for long time(S132)

FormerMember — Thu, 23 Mar 2017 12:57:30 GMT

The project is not uploaded..

RE: Restarted Timer is not executed for long time(S132)

Moritz — Thu, 23 Mar 2017 12:55:57 GMT

Hey, thanks for your answer. I ported my project to Keil, since I use Segger. Everything worked so far, but I couldn't test the NRF_LOG part, because of the code Limitations. I already activated it and saved so you should be good to go. I use S132 V3.0.

All I do in my code at the moment is, increase an uint32_t by one everytime the handler is called and send that as a notification. If you disconnect and connect again it should instantly send the notifications again, sometimes it does. Today I waited over a minute one time till I got my notifications again.

drive.google.com/open

RE: Restarted Timer is not executed for long time(S132)

FormerMember — Thu, 23 Mar 2017 07:43:24 GMT

It should be perfectly possible to start and stop a timer upon a connect and disconnect, respectively?

It would be very nice if I can see/test the code, could you upload it? Also, which version of S132 do you use?

Update 24.03.2017: I think the problem is related to app_timer, calling the app_timer a BLE interrupt context.To call the app_timer a BLE interrupt context, the scheduler should be used. The ble_app_hids_mouse example uses the the scheduler for the battery level update, I would recommend you to take a look at it.

For reference, I have attached a version of ble_app_template (SDK 13, S132 v.4.0.2), that uses the scheduler and calls app_timer in a BLE interrupt context (BLE_GAP_EVT_CONNECTED and BLE_GAP_EVT_DISCONNECTED), similar to your project: ble_app_template_122411_devzone.zip