ESB - BLE uart timeslot problem - Timeslots stops being called

[MStampe]

Hi

I have implemented (heavily base on the found examples) an application which uses both ESB and BLE.
For now I focus on developing the ESB part of the SW.

I am using the SDK 15.2.0 and developing for a NRF52832 using Segger.
The softdevice is the newest S132.

It actually works quite well, but my main problem is that my timeslot-interrups only occurs as long as the BLE is advertising or if there is an ongoing connection.
So the default advertisement timeout is 180 seconds, after this the interrupts-doesn't occur anymore.

I have found others with this problem, but either their solution is just to restart advertisement, or else they didn't write you back here at the forum.
https://devzone.nordicsemi.com/f/nordic-q-a/21458/sleep-mode-during-multiprotocol-timeslot-api

Sometimes I need to use ESB without using the BLE part.
In general I cannot find very much documentaion about how the ESB and BLE are related regarding the timeslots?

Hope you can help figure this out.

Best regards

[haakonsh]

You're probably going into SystemOFF after the advertisements time out, and that's why your Timeslots are no longer availlable. 

See the advertising event handler in main.c. 

[MStampe]

Hi Haakonsh

No, unfortunately this is not the case. All the software is running just fine, only the timeslot interrupts are not happening. As you see in link provided, I have the same problem.

It's very clear that is stops as soon as the advertising stops. I have in the event handler tried to remove the SystemOFF call. That don't make a difference. The only think keeps the timeslot IRQs trigging is to restart the advertisement again.

I need to say that is our own software running, but a very boiled down version, with only ESB usage and the BLE uart running. Where the BLE uart is almost taken directly from the examples found here.

[haakonsh]

Can you share your project?

[MStampe]

Unfortunately I cannot.

I can create an example project, that shows the problem with the setup we have, but it will take a couple of days before I got that.

I was hoping that you knew what the problem was related to