转自大香瓜的博客。
一、简介
本篇在《CC2541的SimpleBLECentral发现服务与特征值过程》的基础上,进一步讲述主机端如何发现从机的多个特征值句柄。
二、实验平台
协议栈版本:BLE-CC254x-1.3.2
编译软件:IAR 8.20.2
三、思路
主机通过“从机服务的UUID”发现从机相对应的服务,再通过分别发送“特征值的UUID”依次获取到特征值句柄。
由于有些特征值句柄是获取不到的,所以本篇只获取char1、char2、char4(需要修改从机)和char6(从机要有char6)的特征值句柄。
四、实现过程
1、增加多个特征值状态的宏(sImpleBLECentral.c中)
- // Discovery states
- enum
- {
- BLE_DISC_STATE_IDLE, // Idle
- BLE_DISC_STATE_SVC, // Service discovery
- BLE_DISC_STATE_CHAR1, // Characteristic discovery 1
- BLE_DISC_STATE_CHAR2, // Characteristic discovery 2
- BLE_DISC_STATE_CHAR3, // Characteristic discovery 3
- BLE_DISC_STATE_CHAR4, // Characteristic discovery 4
- BLE_DISC_STATE_CHAR5, // Characteristic discovery 5
- BLE_DISC_STATE_CHAR6 // Characteristic discovery 6
- };
2、定义一个自己存放特征句柄的数组(sImpleBLECentral.c中)
- // Discovered characteristic handle
- static uint16 simpleBLECharHdl = 0;
- static uint16 GUA_charHdl[6] = {0}; //6个特征值句柄保存位置
当然也可以直接修改为simpleBLECharHdl[6],但这样需要修改代码中其他用到simpleBLECharHdl的地方。
为了省事,很懒的我自己定义一个GUA_charHdl[6]。
3、修改发现事件的处理函数simpleBLEGATTDiscoveryEvent(sImpleBLECentral.c中)
- /*********************************************************************
- * @fn simpleBLEGATTDiscoveryEvent
- *
- * @brief Process GATT discovery event
- *
- * @return none
- */
- static void simpleBLEGATTDiscoveryEvent( gattMsgEvent_t *pMsg )
- {
- attReadByTypeReq_t req;
- if ( simpleBLEDiscState == BLE_DISC_STATE_SVC )
- {
- // Service found, store handles
- if ( pMsg->method == ATT_FIND_BY_TYPE_VALUE_RSP &&
- pMsg->msg.findByTypeValueRsp.numInfo > 0 )
- {
- simpleBLESvcStartHdl = pMsg->msg.findByTypeValueRsp.handlesInfo[0].handle;
- simpleBLESvcEndHdl = pMsg->msg.findByTypeValueRsp.handlesInfo[0].grpEndHandle;
- }
- // If procedure complete
- if ( ( pMsg->method == ATT_FIND_BY_TYPE_VALUE_RSP &&
- pMsg->hdr.status == bleProcedureComplete ) ||
- ( pMsg->method == ATT_ERROR_RSP ) )
- {
- if ( simpleBLESvcStartHdl != 0 )
- {
- // Discover characteristic
- simpleBLEDiscState = BLE_DISC_STATE_CHAR1;
- req.startHandle = simpleBLESvcStartHdl;
- req.endHandle = simpleBLESvcEndHdl;
- req.type.len = ATT_BT_UUID_SIZE;
- req.type.uuid[0] = LO_UINT16(SIMPLEPROFILE_CHAR1_UUID);
- req.type.uuid[1] = HI_UINT16(SIMPLEPROFILE_CHAR1_UUID);
- GATT_ReadUsingCharUUID( simpleBLEConnHandle, &req, simpleBLETaskId );
- }
- }
- }
- else if ( simpleBLEDiscState == BLE_DISC_STATE_CHAR1 ) //发现char1
- {
- //读出char1的handle并保存到GUA_charHdl
- if ( pMsg->method == ATT_READ_BY_TYPE_RSP &&
- pMsg->msg.readByTypeRsp.numPairs > 0 )
- {
- GUA_charHdl[0] = BUILD_UINT16( pMsg->msg.readByTypeRsp.dataList[0],
- pMsg->msg.readByTypeRsp.dataList[1] );
- simpleBLEProcedureInProgress = TRUE; //此时仍在进程中
- }
- //发送命令读取下一个特征值的句柄
- else{ //注意这里一定要else,当numPairs=0时才能再读下一个,下同
- simpleBLEDiscState = BLE_DISC_STATE_CHAR2;
- req.startHandle = simpleBLESvcStartHdl;
- req.endHandle = simpleBLESvcEndHdl;
- req.type.len = ATT_BT_UUID_SIZE;
- req.type.uuid[0] = LO_UINT16(SIMPLEPROFILE_CHAR2_UUID);
- req.type.uuid[1] = HI_UINT16(SIMPLEPROFILE_CHAR2_UUID);
- GATT_ReadUsingCharUUID( simpleBLEConnHandle, &req, simpleBLETaskId );
- }
- }
- else if ( simpleBLEDiscState == BLE_DISC_STATE_CHAR2 ) //发现char2
- {
- //读出char2的handle并保存到GUA_charHdl
- if ( pMsg->method == ATT_READ_BY_TYPE_RSP &&
- pMsg->msg.readByTypeRsp.numPairs > 0 )
- {
- GUA_charHdl[1] = BUILD_UINT16( pMsg->msg.readByTypeRsp.dataList[0],
- pMsg->msg.readByTypeRsp.dataList[1] );
- simpleBLEProcedureInProgress = TRUE; //此时仍在进程中
- }
- //发送命令读取下一个特征值的句柄
- else{
- simpleBLEDiscState = BLE_DISC_STATE_CHAR4;
- req.startHandle = simpleBLESvcStartHdl;
- req.endHandle = simpleBLESvcEndHdl;
- req.type.len = ATT_BT_UUID_SIZE;
- req.type.uuid[0] = LO_UINT16(SIMPLEPROFILE_CHAR4_UUID);
- req.type.uuid[1] = HI_UINT16(SIMPLEPROFILE_CHAR4_UUID);
- GATT_ReadUsingCharUUID( simpleBLEConnHandle, &req, simpleBLETaskId );
- }
- }
- /*
- else if ( simpleBLEDiscState == BLE_DISC_STATE_CHAR3 ) //发现char3
- {
- //读出char3的handle并保存到GUA_charHdl
- if ( pMsg->method == ATT_READ_BY_TYPE_RSP &&
- pMsg->msg.readByTypeRsp.numPairs > 0 )
- {
- GUA_charHdl[2] = BUILD_UINT16( pMsg->msg.readByTypeRsp.dataList[0],
- pMsg->msg.readByTypeRsp.dataList[1] );
- simpleBLEProcedureInProgress = TRUE; //此时仍在进程中
- }
- //发送命令读取下一个特征值的句柄
- else{
- simpleBLEDiscState = BLE_DISC_STATE_CHAR4;
- req.startHandle = simpleBLESvcStartHdl;
- req.endHandle = simpleBLESvcEndHdl;
- req.type.len = ATT_BT_UUID_SIZE;
- req.type.uuid[0] = LO_UINT16(SIMPLEPROFILE_CHAR4_UUID);
- req.type.uuid[1] = HI_UINT16(SIMPLEPROFILE_CHAR4_UUID);
- GATT_ReadUsingCharUUID( simpleBLEConnHandle, &req, simpleBLETaskId );
- }
- }
- */
- else if ( simpleBLEDiscState == BLE_DISC_STATE_CHAR4 ) //发现char4
- {
- //读出char3的handle并保存到GUA_charHdl
- if ( pMsg->method == ATT_READ_BY_TYPE_RSP &&
- pMsg->msg.readByTypeRsp.numPairs > 0 )
- {
- GUA_charHdl[3] = BUILD_UINT16( pMsg->msg.readByTypeRsp.dataList[0],
- pMsg->msg.readByTypeRsp.dataList[1] );
- simpleBLEProcedureInProgress = TRUE; //此时仍在进程中
- }
- //发送命令读取下一个特征值的句柄
- else{
- simpleBLEDiscState = BLE_DISC_STATE_CHAR6;
- req.startHandle = simpleBLESvcStartHdl;
- req.endHandle = simpleBLESvcEndHdl;
- req.type.len = ATT_BT_UUID_SIZE;
- req.type.uuid[0] = LO_UINT16(SIMPLEPROFILE_CHAR6_UUID);
- req.type.uuid[1] = HI_UINT16(SIMPLEPROFILE_CHAR6_UUID);
- GATT_ReadUsingCharUUID( simpleBLEConnHandle, &req, simpleBLETaskId );
- }
- }
- /*
- else if ( simpleBLEDiscState == BLE_DISC_STATE_CHAR5 ) //发现char5
- {
- //读出char3的handle并保存到GUA_charHdl
- if ( pMsg->method == ATT_READ_BY_TYPE_RSP &&
- pMsg->msg.readByTypeRsp.numPairs > 0 )
- {
- GUA_charHdl[4] = BUILD_UINT16( pMsg->msg.readByTypeRsp.dataList[0],
- pMsg->msg.readByTypeRsp.dataList[1] );
- simpleBLEProcedureInProgress = TRUE; //此时仍在进程中
- }
- //发送命令读取下一个特征值的句柄
- else{
- simpleBLEDiscState = BLE_DISC_STATE_CHAR6;
- req.startHandle = simpleBLESvcStartHdl;
- req.endHandle = simpleBLESvcEndHdl;
- req.type.len = ATT_BT_UUID_SIZE;
- req.type.uuid[0] = LO_UINT16(SIMPLEPROFILE_CHAR6_UUID);
- req.type.uuid[1] = HI_UINT16(SIMPLEPROFILE_CHAR6_UUID);
- GATT_ReadUsingCharUUID( simpleBLEConnHandle, &req, simpleBLETaskId );
- }
- }
- */
- else if ( simpleBLEDiscState == BLE_DISC_STATE_CHAR6 ) //发现char6
- {
- // Characteristic found, store handle
- if ( pMsg->method == ATT_READ_BY_TYPE_RSP &&
- pMsg->msg.readByTypeRsp.numPairs > 0 )
- {
- GUA_charHdl[5] = BUILD_UINT16( pMsg->msg.readByTypeRsp.dataList[0],
- pMsg->msg.readByTypeRsp.dataList[1] );
- LCD_WRITE_STRING( "Char5 Found", HAL_LCD_LINE_6 );
- simpleBLEProcedureInProgress = FALSE; //注意最后一个特征值时需要赋值
- }
- simpleBLEDiscState = BLE_DISC_STATE_IDLE; //读完最后的char6,就可以返回闲置模式了
- }
- }
1)主机端只能获得“特征值属性为读、通知,并且属性表中为可读”的特征值句柄。
说的通俗一点,就是特征值的属性要为GATT_PROP_READ或GATT_PROP_NOTIFY,且属性表中对应的值的属性要为GATT_PERMIT_READ,主机端才能获取到它的特征值句柄。
例子一:
SimpleBLEPeripheral工程的char1的属性是可读可写(满足条件)
- // Simple Profile Characteristic 1 Properties
- static uint8 simpleProfileChar1Props = GATT_PROP_READ | GATT_PROP_WRITE;
- // Characteristic Value 1
- {
- { ATT_BT_UUID_SIZE, simpleProfilechar1UUID },
- GATT_PERMIT_READ | GATT_PERMIT_WRITE,
- 0,
- &simpleProfileChar1
- },
例子二:
SimpleBLEPeripheral工程的char3的属性是可写,不可读(不满足条件)
- // Simple Profile Characteristic 3 Properties
- static uint8 simpleProfileChar3Props = GATT_PROP_WRITE;
并且属性表中的属性也是GATT_PERMIT_WRITE(不满足条件)
- // Characteristic Value 3
- {
- { ATT_BT_UUID_SIZE, simpleProfilechar3UUID },
- GATT_PERMIT_WRITE,
- 0,
- &simpleProfileChar3
- },
例子三:
SimpleBLEPeripheral工程的char4的属性是通知(满足条件)
- // Simple Profile Characteristic 4 Properties
- static uint8 simpleProfileChar4Props = GATT_PROP_NOTIFY;
但是属性表中的属性是0,即不可读不可写(不满足条件)
- // Characteristic Value 4
- {
- { ATT_BT_UUID_SIZE, simpleProfilechar4UUID },
- 0,
- 0,
- &simpleProfileChar4
- },
2)连续读取特征值句柄时,如果中间某个特征值句柄读取失败,则会导致后续的特征值也读取不到。
3)char5的属性表的值的属性是GATT_PERMIT_AUTHEN_READ,似乎是加密的,我不熟,就暂时不考虑啦。会用的朋友可以告诉我。
五、实验结果
注:char3和char5的特征值我没有去读,而char4则是修改了从机的属性表为GATT_PERMIT_READ才可读到。
六、此方法存在的问题
实验中发现:从char1一直读到char6时,由于char3不能读,导致后面几个也读不到了。而屏蔽了char3,后面的就可以读了。
目前的解决办法:屏蔽不能读的char3和char5,跳过问题。
待验证的解决方案:用GATT_DiscCharsByUUID函数获取特征值句柄。