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.

CC1352R: macSymbolTimerICallTimerCback - Why does this get called every 90s even with BLE and 15.4 stacks idle?

Part Number: CC1352R
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

I'm looking at power consumption, and have noted that macSymbolTimerICallTimerCback is called every 90 seconds, even when the BLE and 15.4 stacks are idle. It appears that it may contribute multiple uA of average current to the idle power consumption.

Why would this be happening, and is there a way to shut it off when neither stack is active?

  • I forgot to mention the app is on 8.30 SDK, based off of the dmm_154sensor_remote_display_oad_app.

  • Hi Joshua,

    this example uses a version of TI 15.4-Stack that uses ICall. 

    My recommendation in this case would be to start from a TI 15.4 Stack example and to add dmm using SysConfig. You can then copy the application logic from the dmm example.

    This should project should then not have any macICall calls.

    I will check if I can find the source of the API call in this older version in TI 15.4-Stack but as stated above I would recommend you to start with our updated version.

    Kind regards,
    Theo

  • Why aren't the examples in SDK 8.30 using the latest stuff? This seems like a serious problem! We trust that the examples will be implementing the latest and best versions of everything, and adhering to TI best practices. This is pretty disappointing to say the least!

  • Theo,

    I tried to do this, but appears that when you enable the 15.4 stack, BLE and the DMM, sysconfig generates includes for icall.h.

    Is there a pre-configured project that has 15.4, DMM and BLE enabled, it appears that it will be a long difficult slog to figure out how to get the sysconfig tool to do this.

    Josh

  • Hi Joshua,

    thank you for the test. I also see the include but using the latest TI 15.4-Stack examples I've not seen any periodic call to macSymbolTimerICallTimerCback(),
    I will debug the dmm example and compare it to the TI 15.4-Stack examples to see where this call originates from.

    For BLE it will always use iCall but the latest TI 15.4-Stack does not have this layer anymore.

    I will update you about my findings.

    Kind regards,
    Theo 

  • Okay, so does the dmm example from the 8.30 sdk use the latest 15.4 stack? I would presume that what you're finding is that the call to macSymbolTimerICallTimerCback is originating from the BLE stack, and not the 15.4 stack?

    Josh