• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 49 subscribers
  • Views 614 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.

osal_CbTimerInit

Hansen Dsouza
Expert 1175 points

Thanks .Is the osal_CbTimerInit(  ); from osal_cbtimer.c  initialized in osalinittasks()  for example purpose and not used? because all profiles use osal_start_timerEx() from OSAL_timer.c

I'm guessing the difference between the two is that the former can be used to call any function which is not a taskevent because CBtimer itself is a task  and the later is used to call a taskevent directly.Any other reason for choosing CBtimer?

 

  • 0
    TI__Genius 17975 points

    From the SW Developer's Guide:

    OSAL_CBTIMER_NUM_TASKS – This symbol defines the number of OSAL callback timers
    that can be used. The BLE protocol stack uses the OSAL callback timer, and therefore this
    value must be defined as either 1 or 2 (there is a maximum of two callback timers allowed).
    For applications that are not using any callback timers, such as the sample application, this
    value should be defined as 1.