CC2652P: CC2652P: rfDriverCallback issue

Hi Shilpa,

In your case I don't think you need to modify the files generated by SysConfig (but you can follow this guide to disable SysConfig)

If I am correct, the compilation failure should provide you a good hint :) If not, you can review the code generated inside the file ti_drivers_config.c :

/*
 *  ======== RF_globalCallbackFunction ========
 *  This function is called by the driver on global driver events.
 *  It will call specific callback functions to further handle the triggering events.
 */
static void RF_globalCallbackFunction(RF_Handle client, RF_GlobalEvent events, void *arg)
{
    rfDriverCallback(client, events, arg);
}

/*
 *  ======== rfDriverCallback ========
 *  Handle events triggered by the RF driver for custom / application specific behavior.
 */
void __attribute__((weak)) rfDriverCallback(RF_Handle client, RF_GlobalEvent events, void *arg)
{
    /* ======== PLEASE READ THIS ========
    *
    * This function is declared weak for the application to override it.
    * A new definition of 'rfDriverCallback' is required if you want to
    * handle the events listed in '.globalEventMask'.
    *
    * Please copy this function definition to create your own, but make
    * sure to remove '__attribute__((weak))' for your definition.
    *
    * According to '.globalEventMask', this function will be triggered by:
    *   - RF_GlobalEventRadioPowerDown
    * 
    * An example of how to handle these events would be:
    * 
    *   --- Code snippet begin ---
    * 
    *   if(events & RF_GlobalEventRadioPowerDown) {
    *       // Perform action for this event
    *   }
    * 
    *   --- Code snippet end ---
    */
}

I hope this will help,

Kind regards,