This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Multi advertising non connectable and connectable are blocking CPU on nrf52840

Hello,

In our project there is a problem that we encountered is happening when the Nordic BLE mesh advertising and connectable advertising for GATT connections are enabled in the same time. This problem is behaving by blocking the access to CPU for maximum of 15.3 ms, which is huge. As you can see in the attached images, these blocking issues are sporadic without having a period of happening. This is not happening if there only Nordic Mesh is available or only the GATT advertising is started. We are thinking of using the Radio timeslots but we suppose this will resolve only the transmission part since the reception is asynchronous from a third party device.  

      We are using the TIMER1 interrupt for toggling an GPIO (in project it used to have the clock on the line). The Softdevice used is S140 6.1.0 and nRF5 SDK v.15.0

 

   How can we handle this worst 15.3ms latency? Who needs so much CPU time?

Thank you,

 Catalin

Parents
  • Hi,

    How are you using both Mesh and connectable advertising for GATT connections at the same time? Are you using the timeslot API?

    If TIMESLOT_REQ_EARLIEST_TIMEOUT_US matches the blocked interval, I suspect that the request of the earliest timeslot isn't handled somewhere in your application. Can you see if this is the case?

    Also which Mesh example are you running?

    Best Regards,

    Martin

Reply
  • Hi,

    How are you using both Mesh and connectable advertising for GATT connections at the same time? Are you using the timeslot API?

    If TIMESLOT_REQ_EARLIEST_TIMEOUT_US matches the blocked interval, I suspect that the request of the earliest timeslot isn't handled somewhere in your application. Can you see if this is the case?

    Also which Mesh example are you running?

    Best Regards,

    Martin

Children
No Data
Related