Connection loss immediately if timer 2 capture value is changed

RE: Connection loss immediately if timer 2 capture value is changed

Petter Myhre — Tue, 23 Jun 2015 11:24:13 GMT

You can create a case in the MyPage support portal, top right corner of our website, and share the project there. This will be private and secure. Or you can edit your question to include some more code. I'm interested in when you are calling this timer init function.

RE: Connection loss immediately if timer 2 capture value is changed

asma — Tue, 23 Jun 2015 04:57:50 GMT

No its confidential.but i can add some files if you want from which u can try to understand the code.

RE: Connection loss immediately if timer 2 capture value is changed

Petter Myhre — Mon, 22 Jun 2015 15:09:46 GMT

Sounds strange. Do you think you can upload your complete project so we can try to reproduce it here?

RE: Connection loss immediately if timer 2 capture value is changed

asma — Thu, 18 Jun 2015 04:30:43 GMT

but when i try with sd_nvic_* functions it is not working properly . it is getting disconnected 5 to 7 minutes every time . with normal function it is working properly .

RE: Connection loss immediately if timer 2 capture value is changed

Ulrich Myhre — Mon, 15 Jun 2015 12:26:59 GMT

Please use the sd_nvic_* functions. They validate the inputs you give, disallowing reserved interrupt priorities that could lead to problems like you had :)

RE: Connection loss immediately if timer 2 capture value is changed

asma — Mon, 15 Jun 2015 12:24:40 GMT

thanks petter and Ulrich for your reply... it was not working with the above solution.. now i just add NVIC_SetPriority(TIMER2_IRQn,NRF_APP_PRIORITY_LOW) after timer interrupt enable and its working.

RE: Connection loss immediately if timer 2 capture value is changed

Petter Myhre — Thu, 11 Jun 2015 12:40:17 GMT

It could have something to do with the interrupt priorities, please see this.

The default interrupt priority is 0, but when the SoftDevice is enabled the application should use Application High(1) or Application Low(3). Please see Appendix A SoftDevice architecture, Section "Exception (interrupt) management with a SoftDevice" in the S110 SoftDevice specification v2.0.

Try doing a sd_nvic_SetPriority(TIMER2_IRQn, NRF_APP_PRIORITY_LOW); after sd_nvic_EnableIRQ(TIMER2_IRQn);

If it doesn't help please edit your question to include the code where you start the timer, the interrupt request handler.