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.

LAUNCHXL-CC26X2R1: About IDLE Task

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSBIOS

Hi

Regarding the default ble5stack example, could you help check if ti_sysbios_knl_idle_loop__E is the ICall Enabled Task?

Thanks.

BR

Trevor

  • Hi Trevor,

    ti_sysbios_knl_idle_loop__E is not an ICall enabled task, it is the kernel IDLE task/loop that is run when no other tasks runs. May I ask what ithe reason for the question is, what are you looking for? :)

  • Hi M-W,

    Regarding the default ble5stack example, it is set to :

    ICALL_MAX_NUM_TASKS = 3
    ICALL_MAX_NUM_ENTITIES = 6

    We added the additional "ICall Enabled Tasks", called QRM001TaskFxn and retained the original configure(ICALL_MAX_NUM_TASKS = 3 & ICALL_MAX_NUM_ENTITIES = 6 ), the system looks properly.

    Our question is whether we need to increase the number of ICall entities and tasks as follows:

    ICALL_MAX_NUM_TASKS = 4
    ICALL_MAX_NUM_ENTITIES = 7

    We also check the ROV, the total number of tasks is 4, if the ti_sysbios_knl_idle_loop__E is is not an ICall enabled task.

    We think we don't need to increase the number for ICALL_MAX_NUM_TASKS and ICALL_MAX_NUM_ENTITIES. Right?

    Thanks.

    BR

    Trevor

  • Hi Trevor,

    It looks like you are fine in that case yes. As the Idle task has no ICall interaction is is never registered with ICall which means it does not take up one of predefined number of slots.