CC2541之回撥函式程式碼解析
阿新 • • 發佈:2019-02-18
轉自:香瓜部落格
回撥函式,解析程式碼: 一 、定義一個 “ 成員為函式指標 ” 的結構體 1 )定義一個函式指標 /** * Central Event Callback Function */ typedef void (*pfnGapCentralRoleEventCB_t) ( gapCentralRoleEvent_t *pEvent //!< Pointer to event structure. ); 它的引數是一個 gapCentralRoleEvent_t 型別的訊息指標 *pEvent 。 其中, gapCentralRoleEvent_t 的型別如下 /** * Central Event Structure */ typedef union { gapEventHdr_t gap; //!< GAP_MSG_EVENT and status. gapDeviceInitDoneEvent_t initDone; //!< GAP initialization done. gapDeviceInfoEvent_t deviceInfo; //!< Discovery device information event structure. gapDevDiscEvent_t discCmpl; //!< Discovery complete event structure. gapEstLinkReqEvent_t linkCmpl; //!< Link complete event structure. gapLinkUpdateEvent_t linkUpdate; //!< Link update event structure. gapTerminateLinkEvent_t linkTerminate; //!< Link terminated event structure. } gapCentralRoleEvent_t; 2 )定義一個結構體 /** * Central Callback Structure */ typedef struct { pfnGapCentralRoleRssiCB_t rssiCB; //!< RSSI callback. pfnGapCentralRoleEventCB_t eventCB; //!< Event callback. } gapCentralRoleCB_t; gapCentralRoleCB_t 結構體有兩個成員,一個是 pfnGapCentralRoleRssiCB_t 型別的成員,一個是 pfnGapCentralRoleEventCB_t 類 型的成員。 二 、寫一個回撥函式,並完成註冊 1 )定義一個函式 simpleBLECentralEventCB /********************************************************************* * @fn simpleBLECentralEventCB * * @brief Central event callback function. * * @param pEvent - pointer to event structure * * @return none */ static void simpleBLECentralEventCB( gapCentralRoleEvent_t *pEvent ) { switch ( pEvent->gap.opcode ) { case GAP_DEVICE_INIT_DONE_EVENT: { LCD_WRITE_STRING( "BLE Central", HAL_LCD_LINE_1 ); LCD_WRITE_STRING( bdAddr2Str( pEvent->initDone.devAddr ), HAL_LCD_LINE_2 ); } break; case GAP_DEVICE_INFO_EVENT: { // if filtering device discovery results based on service UUID if ( DEFAULT_DEV_DISC_BY_SVC_UUID == TRUE ) { if ( simpleBLEFindSvcUuid( SIMPLEPROFILE_SERV_UUID, pEvent->deviceInfo.pEvtData, pEvent->deviceInfo.dataLen ) ) { simpleBLEAddDeviceInfo( pEvent->deviceInfo.addr, pEvent->deviceInfo.addrType ); } } } break; case GAP_DEVICE_DISCOVERY_EVENT: { // discovery complete simpleBLEScanning = FALSE; // if not filtering device discovery results based on service UUID if ( DEFAULT_DEV_DISC_BY_SVC_UUID == FALSE ) { // Copy results simpleBLEScanRes = pEvent->discCmpl.numDevs; osal_memcpy( simpleBLEDevList, pEvent->discCmpl.pDevList, (sizeof( gapDevRec_t ) * pEvent->discCmpl.numDevs) ); } LCD_WRITE_STRING_VALUE( "Devices Found", simpleBLEScanRes, 10, HAL_LCD_LINE_1 ); if ( simpleBLEScanRes > 0 ) { LCD_WRITE_STRING( "<- To Select", HAL_LCD_LINE_2 ); } // initialize scan index to last device simpleBLEScanIdx = simpleBLEScanRes; } break; case GAP_LINK_ESTABLISHED_EVENT: { if ( pEvent->gap.hdr.status == SUCCESS ) { simpleBLEState = BLE_STATE_CONNECTED; simpleBLEConnHandle = pEvent->linkCmpl.connectionHandle; simpleBLEProcedureInProgress = TRUE; // If service discovery not performed initiate service discovery if ( simpleBLECharHdl == 0 ) { osal_start_timerEx( simpleBLETaskId, START_DISCOVERY_EVT, DEFAULT_SVC_DISCOVERY_DELAY ); } LCD_WRITE_STRING( "Connected", HAL_LCD_LINE_1 ); LCD_WRITE_STRING( bdAddr2Str( pEvent->linkCmpl.devAddr ), HAL_LCD_LINE_2 ); } else { simpleBLEState = BLE_STATE_IDLE; simpleBLEConnHandle = GAP_CONNHANDLE_INIT; simpleBLERssi = FALSE; simpleBLEDiscState = BLE_DISC_STATE_IDLE; LCD_WRITE_STRING( "Connect Failed", HAL_LCD_LINE_1 ); LCD_WRITE_STRING_VALUE( "Reason:", pEvent->gap.hdr.status, 10, HAL_LCD_LINE_2 ); } } break; case GAP_LINK_TERMINATED_EVENT: { simpleBLEState = BLE_STATE_IDLE; simpleBLEConnHandle = GAP_CONNHANDLE_INIT; simpleBLERssi = FALSE; simpleBLEDiscState = BLE_DISC_STATE_IDLE; simpleBLECharHdl = 0; simpleBLEProcedureInProgress = FALSE; LCD_WRITE_STRING( "Disconnected", HAL_LCD_LINE_1 ); LCD_WRITE_STRING_VALUE( "Reason:", pEvent->linkTerminate.reason, 10, HAL_LCD_LINE_2 ); } break; case GAP_LINK_PARAM_UPDATE_EVENT: { LCD_WRITE_STRING( "Param Update", HAL_LCD_LINE_1 ); } break; default: break; } } 2 )宣告函式 static void simpleBLECentralEventCB( gapCentralRoleEvent_t *pEvent ); 3 )使 simpleBLECentralEventCB 成為回撥函式 // GAP Role Callbacks static const gapCentralRoleCB_t simpleBLERoleCB = { simpleBLECentralRssiCB, // RSSI callback simpleBLECentralEventCB // Event callback }; 三 、呼叫回撥函式 1 )定義一個新的函式指標變數 pGapCentralRoleCB ( central.c ) // App callbacks static gapCentralRoleCB_t *pGapCentralRoleCB; 2 )將 pGapCentralRoleCB 指向回撥函式 simpleBLECentralEventCB ,也就是註冊回撥函式。 /** * @brief Start the device in Central role. This function is typically * called once during system startup. * * Public function defined in central.h. */ bStatus_t GAPCentralRole_StartDevice( gapCentralRoleCB_t *pAppCallbacks ) { if ( pAppCallbacks ) { pGapCentralRoleCB = pAppCallbacks; } return GAP_DeviceInit( gapCentralRoleTaskId, GAP_PROFILE_CENTRAL, gapCentralRoleMaxScanRes, gapCentralRoleIRK, gapCentralRoleSRK, &gapCentralRoleSignCounter ); } 3 )呼叫回撥函式 // Pass event to app if ( pGapCentralRoleCB && pGapCentralRoleCB->eventCB ) { pGapCentralRoleCB->eventCB( (gapCentralRoleEvent_t *) pMsg ); } } 注:實際上此時 simpleBLECentralEventCB 在第二步結束時,即可直接通過操作結構體來呼叫這個回撥函數了。 但是之所以要將結構體中的 simpleBLECentralEventCB 函式首地址再傳給 simpleBLECentralEventCB (即第三點的 1 、 2 兩個步驟) ,我認為是出於底層的 profiles——central 分層的考慮。