• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 329 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BLE Stack 1.3 - Shortest and safe OSAL event timer time_out

Alex B
Intellectual 260 points

Hi,

I'm modifying the SimpleBLEPeripheral application and would like to include a periodic event in the function "SimpleBLEPeripheral_ProcessEvent()"  using the "osal_start_timerEx()" function and repeatly check for this event (as currently done in the code).

So what is the shortest "time out" I can use as argument in "osal_start_timerEx()" so the program and OSAL keep reliably working ?

Thank you.

Alex

  • 0
    TI__Mastermind 23440 points

    Hi Alex,

    Feel free to use 1ms as the shortest. However, if other tasks have events, these have higher priority and will cause your event to experience jitter with regards to the timing.

    Also, make sure your task doesn't run for such a long time that the lower layers don't have time to do post-processing before the next event after the radio module reports that an event is complete. As a rule, the LL task gets an event every conn interval after the radio transmission is complete. LL in turn will send messages to the other modules, with for instance received data, GAP role changes, Security Manager stuff etc.

    Best regards,
    Aslak 

  • 0 in reply to Aslak N.
    Intellectual 260 points

    Thank you very much, Aslak.