Hard timing dependent feature fails

[Konrad Traczyk]

Hi,

I'm currently working on the project with some hard-timing dependent features. As I've mentioned in another topic, it fails if I have advertising turned on. Turning advertising off results in improved reliability of the feature, however, sometimes it still crashes. Can it be caused because the Softdevice still does something in the background and the main context timings are interrupted?

[run_ar]

How much time does your hard-timing dependent task require?

[Konrad Traczyk]

It varies from 3 seconds up to 12 seconds. It's completely independent from us.

[run_ar]

hmm, I checked with the stack team and they say the softdevice should only do stuff if there are radio operations in progress. Have you tried running your timing dependent features in the timeslot api?

[Konrad Traczyk]

Thanks for your help. Actually so far we thought that softdevice messes around with the code no matter if the advertising is enabled or not. The timeslot would be ok if it wasn't so short - we are afraid that softdevice will not grant the application the adjacent timeslots if we extend it, so our feature would be interrupted by previously enqued softdevice timeslot.

[run_ar]

And disabling the softdevice during the timing dependent feature is impossible?