• State TI Thinks Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 3 answers
  • Subscribers 52 subscribers
  • Views 983 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.

CC2340R5: wakeup from standby mode through gpio wakeup.

Rushikesh Aidale
Prodigy 155 points
Other Parts Discussed in Thread: CC2340R5, SYSCONFIG

Hello, 

I'm using CC2340R5 basic_ble example code. 

I've created separate files for gpio interrupt operation. 

Enabled the GPIO interrupt and triggering advertising event in the interrupt callback function. 

But when I'm doing this, the code goes in while loop faultISR(); function. 

Generally the BLEAPPUTIL_EVT_ADV_CB_EVENT case gets called periodically through interval timer.

Through this case advertising event is being generated and whenever the advertising case calls the device goes to run state from standby.

I want the device to wakeup whenever GPIO interrupt occurs and also the periodic wakeup should run in background independently.

Currently GPIO interrupt is generating but the periodic wakeup through interval timer is not happening. 

This case should be called periodically, but when its not happening.

What could be the issue?

Please suggest if any steps to follow or changes to be done.

Regards,

Rushikesh.

  • 0
    TI__Expert 3730 points

    Rushikesh, 

    Thanks for reaching out. We will look into this and get back to you shortly. In the meantime, could you share what version of the SDK you are currently using?

    Can you also share some detail on how you have implemented the GPIO interrupt?

    Best regards,

    Luke

  • 0
    TI__Mastermind 41940 points

    Hi,

    When calling BLE APIs, please ensure that these functions are not called within an interrupt context. The BLEAppUtil_invokeFunctionNoData() function may be used to call a BLE API within an interrupt function by switching the context. Please try to use this API instead of directly calling the advertising enable API.

    Best Regards,

    Jan 

  • 0 in reply to Luke
    Prodigy 155 points

    I'm using SDK 7.20.

    Code: 

    In main thread() I'm enabling the interrupt.

    Callback function: 

    Also check commented code as well I tried to generate other events to broadcast.

    I'm calling main thread into the main function:

  • 0 in reply to Jan
    Prodigy 155 points

    Hello Jan,

    I'm sorry I didn't understand exactly.

    Which API are you referring to? 

    Do you mean I should use  BLEAppUtil_invokeFunctionNoData() to call the GPIO interrupt callback?

    Please can you brief it?

    Regards, 

    Rushikesh.

  • 0 in reply to Rushikesh Aidale
    TI__Mastermind 41940 points

    Hi Rushikesh,

    My apologies, to clarify you are attempting to enable advertising when the GPIO callback occurs correct? If so, then I would recommend using something like the code snippet shown below:

    void enableAdvertising()
{
    BLEAppUtil_advStart(peripheralAdvHandle_1, &advSetStartParamsSet_1);

}

void gpioButtonFxn0(uint_least8_t index)
{
    BLEAppUtil_invokeFunctionNoData(enableAdvertising);
}

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 155 points

    Hello Jan,

    I have called the function BLEAppUtil_invokeFunctionData() in callback function of GPIO interrupt.

    And written function enableAdvertising() in app_broadcaster.c.

    Now, the broadcasting is happening periodically, but the GPIO wakeup is not occuring. 

    Am I missing something here?

    Regards,

    Rushikesh.

  • 0 in reply to Rushikesh Aidale
    TI__Mastermind 41940 points

    Hi Rushikesh,

    Can you clarify what you mean by the GPIO wakeup not occurring? If the advertising is being enabled by the button press, then the interrupt should be waking the device.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 155 points

    Hello Jan,

    Thanks for your help!

    I've written code as below, now the GPIO interrupt is being generated and also it is broadcasting as well. 

    I have further query. 

    I want to wakeup BLE by only GPIO interrupt periodically(30s) by the sensor and broadcast the data. 

    Because it is consuming less average current. 

    But here, the problem is, interval timer of BLE is still running in the background it causes to wakeup BLE and broadcast the data. 

    How can I stop the interval timer here? 

    Please suggest. 

    I have tried to below option of disabling timers by doing below setting but its generating build errors. 

    Regards,

    Rushikesh.

  • 0 in reply to Rushikesh Aidale
    TI__Mastermind 41940 points

    Hi,

    I am glad to hear you were able to resolve the issue! Thank you for sharing the solution with the community! :)

    If you want to only advertise on GPIO wakeup, then I would recommend enabling the advertisement on the GPIO wakeup interrupt and then shortly thereafter disabling the advertisements (either through a follow up timer interrupt or by monitoring the BLE task events and disabling the advertisements when the events that signal that an advertisement has been sent is received).

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 155 points

    Hello Jan,

    I understood. 

    So, you mean to say is that whenever an advertising event occurs through interval timer I need to disable the advertisement calls, right?

    Can you please brief it with an example?

    Because I've tried it and it works as well, but still BLE goes in run state whenever that event is triggered.

    Regards,

    Rushikesh.

  • 0 in reply to Rushikesh Aidale
    TI__Mastermind 41940 points

    Hi Rushikesh,

    That is correct. When advertisements are enabled in the BLE5-Stack, then the device will wake up from standby ever so often to send a single advertisement while advertisements are enabled. The time between these advertisements is the advertising interval which is configured through SysConfig. In between advertisements, the BLE5-Stack will not be active and if the device is not doing anything else, then the device should go into standby.

    If you want to send a single advertisement and go back to standby without the ble5-stack waking up to send another, then you should disable the advertisements after the first advertisement has been sent. Within the app_broadcaster.c file, you may find the broadcasterAdvHandler. The broadcasterAdvHandler allows you to add additional events to your event mask so that when these additional events occur, they are communicated to the application task. In this case, I would recommend adding BLEAPPUTIL_ADV_END

    BLEAppUtil_EventHandler_t broadcasterAdvHandler =
{
    .handlerType    = BLEAPPUTIL_GAP_ADV_TYPE,
    .pEventHandler  = Broadcaster_AdvEventHandler,
    .eventMask      = BLEAPPUTIL_ADV_START_AFTER_ENABLE |
                      BLEAPPUTIL_ADV_END_AFTER_DISABLE | BLEAPPUTIL_ADV_END
};

    This addition to the event will make it such that right after an advertisement is sent an BLEAPPUTIL_ADV_END event will be received by the Broadcaster_AdvEventHandler(). You can modify this function as shown below to disable the advertisements:

    void Broadcaster_AdvEventHandler(uint32 event, BLEAppUtil_msgHdr_t *pMsgData)
{
    switch(event)
    {
        case BLEAPPUTIL_ADV_START_AFTER_ENABLE:
        {
            MenuModule_printf(APP_MENU_ADV_EVENT, 0, "Adv status: Started - handle: "
                              MENU_MODULE_COLOR_YELLOW "%d" MENU_MODULE_COLOR_RESET,
                              ((BLEAppUtil_AdvEventData_t *)pMsgData)->pBuf->advHandle);
            break;
        }

        case BLEAPPUTIL_ADV_END_AFTER_DISABLE:
        {
            MenuModule_printf(APP_MENU_ADV_EVENT, 0, "Adv status: Ended - handle: "
                              MENU_MODULE_COLOR_YELLOW "%d" MENU_MODULE_COLOR_RESET,
                              ((BLEAppUtil_AdvEventData_t *)pMsgData)->pBuf->advHandle);
            break;
        }

        case BLEAPPUTIL_ADV_END:
        {
            MenuModule_printf(APP_MENU_ADV_EVENT, 0, "Adv just ssent: - handle: "
                              MENU_MODULE_COLOR_YELLOW "%d" MENU_MODULE_COLOR_RESET,
                              ((BLEAppUtil_AdvEventData_t *)pMsgData)->pBuf->advHandle);

            // Disable advertisement
            BLEAppUtil_advStop(broadcasterAdvHandle_1);
            break;


        }

        default:
        {
            break;
        }
    }
}

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 155 points

    Hello Jan,

    Thank you for your solution and quick response!

    I have tried a different method to disable the event here. I'm commenting the part which adds the advertising event into the queue. Please let me know it its correct or not.

    Because, its working well. I'm getting interrupt as well as the broadcasting through the interval timer has stopped. 

    I'm getting low standby current and average current as well. 

    Will try above solution as well. 

    And please provide your feedback as well on above.

    Thanks and regards,

    Rushikesh.

  • 0 in reply to Rushikesh Aidale
    TI__Mastermind 41940 points

    Hi Rushikesh,

    I am glad to hear the method you have implemented seems to work well! Based on your code snippet, I would suggest removing the dynamic memory allocation entirely. You are currently allocating memory, but not freeing it which will cause issues further down the line. Besides that, my only concern would be that you are having an empty advertising callback. If you don't have any plans to use any of the advertising callback features, then this should be okay to leave as is, but if you do plan to use the callback down the line then I would suggest trying to see if the solution i provided earlier works as expected.

    Best Regards,

    Jan