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.

CC2640: The API to know the internal status of the stack on CC2640

Guru 16800 points
Part Number: CC2640
Other Parts Discussed in Thread: BLE-STACK,

Hello,

Is there any method to know the internal status of the stack on CC2640?
For example, my customers want to know that the stack is in active, the stack is in hung-up and so on.
If you have API having the function, please let me know.

Best Regards,
Nomo

  • Hi Nomo,

    When you say stack, do you mean you want to know the status of the stack in RAM (e.g. if you are nearing stack overflow?) Or are you wanting to know some sort of status on the BLE-STACK software itself?

    Regards,
    Katie
  • Hello Katie-san,

    Thank you for your reply.
    I want to know some sort of status on the BLE-STACK software itself.

    Best Regards,
    Nomo

  • Hi Nomo,

    There are a lot of different things that you could do depending on the configuration that you want to use the CC2640 and what particular information you want to know. If you use CC2640R2F there is an API guide here: dev.ti.com/.../index.html
    If you are using some sort of solution where the CC2640R2F is acting as the Network Processor and something else is acting as the Application Processor, you could look at the Simple Network Processor (SNP) APIs section of that guide.

    Could you provide more information on specifically what the customer is trying to do or if there is a particular problem that they are trying to troubleshoot, and what BLE example project they are working from so we will know more about configuration?

    Regards,
    Katie
  • Hello Katie-san,

    Thank you for your reply.

    They want to achieve the multirole application based on the combination of simple_broadcaster and simple_observer sample codes.
    They are targeting on CC2640.
    For some settings of a scan interval, the stack seems to be hang up and the advertise packet isn't output.
    So, they try to know the status of the BLE stack and recover from the hang up.

    Best Regards,
    Nomo
  • Hi Nomo,

    The BLE Developer's Guide for the 2.2.x BLE Stack has a section on debugging that could be quite helpful: www.ti.com/.../swru393 In particular, section 9.6 Profiling the ICall Heap Manager and section 9.11 Debugging Memory Problems can help you determine if you are having memory issues. The section 9.10 also talks about Assert Handling and it's potential use in debugging the stack. Now, because you say there is a scan interval component, that could mean an issue of not enough resources or not being able to make real-time because other tasks are taking too long. The section 9.5 TI-RTOS Object Viewer can be useful for finding the status of different tasks.

    I hope that these debugging techniques may be helpful for finding root cause of their issue.

    Regards,
    Katie
  • Hello Katie-san,

    Thank you for you reply.
    I'll refer the documents you proposed.

    Best Regards,
    Nomo