Network Processor GATT

Transcription

1 TEXAS INSTRUMENTS INCORPORATED Network Processor GATT How to setup GATT DB OFF CHIP on CC254X Greg Stewart 7/29/2012 This document describes how to setup a Network Processor implementation with the CC2540X where the GATT database is stored off chip. This requires the external CPU to process read and write request of the GATT database server entries.

2 Contents 1 Overview Network Processor GATT DATABASE OFF CHIP Setup Network Processor This guide used a SmartRF board with 2540 module running HostTestRelease. Compile HostTestRelease Preprocessor Options External MCU Master/Phone Setup GATT Table on Network Processor Send_GATT_AddService 0x2800, Send_GATT_AddAttribute "03:28", 0x Verify GATT Table Advertise and Connect MCU Handle Request... 7

3 1 Overview 1.1 Network Processor GATT DATABASE OFF CHIP This document describes how to setup a Network Processor implementation with the CC2540X where the GATT database is stored off chip. This requires the external CPU to process read and write request of the GATT database server entries. Master (phone) RF Peripheral (CC254x) Network Processor UART/SPI External MCU (MSP430) 2 Setup 2.1 Network Processor This guide used a SmartRF board with 2540 module running HostTestRelease. Compile HostTestRelease The hosttestrelease project is used when the CC254X is used as a network processor. This project default directory is C:\Texas Instruments\BLE-CC254x-1.2.1\Projects\ble\HostTestApp\CC254x\HostTestRelease.eww Preprocessor Options To allow the MCU to receive all the GATT reads/request, it is necessary to build the application with the GATT_DB_OFF_CHIP preprocessor command.

4 2.2 External MCU The PC Tool HCITester.exe communicating with the SmartRF board over a UART simulates the external MCU. Please see wiki guide on setting up and running HCITester.exe. 2.3 Master/Phone The phone is simulated using Btool and a CC2540USB Dongle. 3 Setup GATT Table on Network Processor The following script is an example of GATT Table setup on the NP. This will let the NP lower layers know that there are valid attributes. Without these entries, the NP would reject any read or write request

5 from another BLE device. One the attributes are setup, any valid read/write request(depending on permission setup) will be forwarded to the external MCU. #initialize as peripheral Send_GAP_DeviceInit 0x04, 3, 0, 0, 1 ################################ # Generic Service ################################ #01- Add Primary Service Send_GATT_AddService 0x2800, 3 #02 Add Characteristic Declaration Send_GATT_AddAttribute "03:28", 0x03 #03 DeviceName Send_GATT_AddAttribute "00:2A", 0x03 sleep 100 ################################# # Simple BLE Service ################################# #04- Add Primary Service Send_GATT_AddService 0x2800, 4 #05 Add Characteristic Declaration - SimpleBleChar1 Send_GATT_AddAttribute "03:28", 0x03 #06 - Char 1 Value Send_GATT_AddAttribute "F1:FF", 0x03 #07 - Char1 Description Send_GATT_AddAttribute "01:29", 0x03 sleep 100 Send_ATT_FindInfoReq 0xfffe, 0x0001, 0xFFFF 3.1 Send_GATT_AddService 0x2800, 3 This command tells the NP to add a primary service and reserve space for 3 attributes ( counting itself as one). In the script above, these attributes will be a Characteristic Declaration fro Device Name and the Device Name Value attribute. 3.2 Send_GATT_AddAttribute "03:28", 0x03 This command tells the NP to add a Characteristic Declaration. The permissions are set here. Note, the value is not set, and as with attributes on a NP, any value read write request must be handled by external mcu. 4 Verify GATT Table One way to easily verify the GATT table setup is to use the ATT_FIND_INFO_REQ with the connection handle set to the loopback handle (0xFFFE).

6 09:00: Packet "ATT_FindInfoReq", Opcode 0xfd04 09:00: Parameters: 09:00: connectionhandle : 0xfffe 09:00: starthandle : 0x :00: endhandle : 0xFFFF 09:00: :00: Outgoing Dump: 09:00: : fd 06 fe ff ff ff... 09:00: Incoming Dump: 09:00: : 04 ff 06 7f fd :00: :00: Packet "HCI_Vendor_Specific_Event", Opcode 0x00ff 09:00: Parameters: 09:00: Event Opcode : 0x067f (CommandStatus) 09:00: Status : 0x00 (SUCCESS) 09:00: opcode : 0xfd04 (ATT_FindInfoReq) 09:00: datalen : 0x00 09:00: :00: Incoming Dump: 09:00: : 04 ff 1b... 09:00: Incoming Dump: 09:00: : fe ff (...(. 09:00: : a *...(...( 09:00: :00: Packet "HCI_Vendor_Specific_Event", Opcode 0x00ff 09:00: Parameters: 09:00: Event Opcode : 0x0505 (ATT_FindInfoRsp) 09:00: Status : 0x00 (SUCCESS) 09:00: connectionhandle : 0xfffe 09:00: pdulen : 0x15 09:00: format : 0x01 (HANDLE_BT_UUID_TYPE - handle(s) and 16-bit Bluetooth UUID(s)) 09:00: handle : 0x :00: uuid : "00:28" 09:00: handle : 0x :00: uuid : "03:28" 09:00: handle : 0x :00: uuid : "00:2A" 09:00: handle : 0x :00: uuid : "00:28" 09:00: handle : 0x :00: uuid : "03:28" 09:00: :00: Incoming Dump: 09:00: : 04 ff 0f fe ff f1 ff :00: : ) 09:00: :00: Packet "HCI_Vendor_Specific_Event", Opcode 0x00ff 09:00: Parameters: 09:00: Event Opcode : 0x0505 (ATT_FindInfoRsp) 09:00: Status : 0x00 (SUCCESS) 09:00: connectionhandle : 0xfffe 09:00: pdulen : 0x09 09:00: format : 0x01 (HANDLE_BT_UUID_TYPE - handle(s) and 16-bit Bluetooth UUID(s)) 09:00: handle : 0x :00: uuid : "F1:FF" 09:00: handle : 0x :00: uuid : "01:29" 09:00: :00: Incoming Dump: 09:00: : 04 ff a fe ff :00: :00: Packet "HCI_Vendor_Specific_Event", Opcode 0x00ff 09:00: Parameters:

7 09:00: Event Opcode : 0x0505 (ATT_FindInfoRsp) 09:00: Status : 0x1a (bleprocedurecomplete) 09:00: connectionhandle : 0xfffe 09:00: pdulen : 0x00 09:00: Advertise and Connect Use the following script to put the NP in discoverable mode. #Update advertising data Send_GAP_UpdateAdvertisingData 1, "02:01:04:05:05:05:07:07" #Update scan respon Send_GAP_UpdateAdvertisingData 0x00, "02:01:04:05:02:02:02:02" sleep 100 #Make discoverable: GAP_ADTYPE_ADV_IND Send_GAP_MakeDiscoverable 0x00, 0, 0, 0x07, 0x00 From BTool, initiate a connection. 6 MCU Handle Request The external mcu must handle reads and writes. Request Response Btool (OTA) NP HciTester Btool (OTA) NP HciTester From BTool.exe initiate a read request. From discovery, we know that handle 6 is the char1 value UUID (0xfff1). [56] : <Tx> - 09:16: Type : 0x01 (Command) -Opcode : 0xFD8A (GATT_ReadCharValue) -Data Length : 0x04 (4) byte(s) ConnHandle : 0x0000 (0) Handle : 0x0006 (6) Dump(Tx): 01 8A FD The NP will forward the request to the external mcu (HCITester.exe). From HCI tester, send a response for the value requested. 21:16: Incoming Dump: 21:16: : 04 ff 08 0a :16:

8 21:16: Packet "HCI_Vendor_Specific_Event", Opcode 0x00ff 21:16: Parameters: 21:16: Event Opcode : 0x050a (ATT_ReadReq) 21:16: Status : 0x00 (SUCCESS) 21:16: connectionhandle : 0x :16: pdulen : 0x02 21:16: handle : 0x :16: Packet "ATT_ReadRsp", Opcode 0xfd0b 21:16: Parameters: 21:16: connectionhandle : 0 21:16: value : "123" 21:16: :16: Outgoing Dump: 21:16: : 01 0b fd :16: :16: *** Script End *** 21:16: :16: Incoming Dump: 21:16: : 04 ff 06 7f b fd :16: :16: Packet "HCI_Vendor_Specific_Event", Opcode 0x00ff 21:16: Parameters: 21:16: Event Opcode : 0x067f (CommandStatus) 21:16: Status : 0x00 (SUCCESS) 21:16: opcode : 0xfd0b (ATT_ReadRsp) 21:16: datalen : 0x00 21:16: