RTOS/CC2640R2F: ----[HELP] ble5_simple_peripheral_cc2640r2lp_app

ke fan

Part Number: CC2640R2F

Tool/software: TI-RTOS

in simplelink_cc2640r2_sdk_2_30_00_28, ble5_simple_peripheral_cc2640r2lp_app using a module with cc2640R2F RSM pacakge soc. the board.c is deleted and added RSM board files, another modification is just change of a variable to a suitable value in the simple_peripheral.c as the diff output showed as following. all the SIMPLEPROFILE_CHAR from 1st to 4th worked well, but the 5th always failed read. using the nFR Connect app for android and another app. can any one test the SIMPLEPROFILE_CHAR5 to see if there's any problem?

/mnt/g/ti/workspace_v8/ble5_simple_peripheral_cc2640r2lp_app/Application$ diff -Naur simple_peripheral.c.orig simple_peripheral.c
--- simple_peripheral.c.orig    2018-12-17 00:13:45.370092900 +0800
+++ simple_peripheral.c 2018-12-16 23:44:19.521858500 +0800
@@ -608,7 +608,7 @@
     // This device only has display capabilities. Therefore, it will display the
     // passcode during pairing. However, since the default passcode is being
     // used, there is no need to display anything.
-    uint8_t ioCap = GAPBOND_IO_CAP_DISPLAY_ONLY;
+    uint8_t ioCap = GAPBOND_IO_CAP_NO_INPUT_NO_OUTPUT;//z GAPBOND_IO_CAP_DISPLAY_ONLY;
     // Request bonding (storing long-term keys for re-encryption upon subsequent
     // connections without repairing)
     uint8_t bonding = TRUE;

over 5 years ago

0 ke fan over 5 years ago

Expert 1890 points

same problem with ble_simple_peripheral_cc2640r2lp_app. nRF Connect debug shows: Error 137 (0x89): GATT AUTH FAIL




nRF Connect, 2018-12-17
SimpleBLEPeripheral (B0:91:22:77:4A:2B)
V	14:23:58.664	Connecting to B0:91:22:77:4A:2B...
D	14:23:58.664	gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D	14:23:59.544	[Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
D	14:23:59.544	[Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
I	14:23:59.544	Connected to B0:91:22:77:4A:2B
D	14:23:59.555	wait(1600ms)
V	14:24:01.157	Discovering services...
D	14:24:01.157	gatt.discoverServices()
D	14:24:01.178	[Callback] Services discovered with status: 0
I	14:24:01.178	Services discovered
V	14:24:01.246	Generic Access (0x1800)
- Device Name [R] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
Generic Attribute (0x1801)
Device Information (0x180A)
- System ID [R] (0x2A23)
- Model Number String [R] (0x2A24)
- Serial Number String [R] (0x2A25)
- Firmware Revision String [R] (0x2A26)
- Hardware Revision String [R] (0x2A27)
- Software Revision String [R] (0x2A28)
- Manufacturer Name String [R] (0x2A29)
- IEEE 11073-20601 Regulatory Certification Data List [R] (0x2A2A)
- PnP ID [R] (0x2A50)
Unknown Service (0000fff0-0000-1000-8000-00805f9b34fb)
- Unknown Characteristic [R W] (0000fff1-0000-1000-8000-00805f9b34fb)
 Characteristic User Description (0x2901)
- Unknown Characteristic [R] (0000fff2-0000-1000-8000-00805f9b34fb)
 Characteristic User Description (0x2901)
- Unknown Characteristic [W] (0000fff3-0000-1000-8000-00805f9b34fb)
 Characteristic User Description (0x2901)
- Unknown Characteristic [N] (0000fff4-0000-1000-8000-00805f9b34fb)
 Client Characteristic Configuration (0x2902)
 Characteristic User Description (0x2901)
- Unknown Characteristic [R] (0000fff5-0000-1000-8000-00805f9b34fb)
 Characteristic User Description (0x2901)
D	14:24:01.247	gatt.setCharacteristicNotification(0000fff4-0000-1000-8000-00805f9b34fb, true)
V	14:24:24.975	Reading characteristic 0000fff5-0000-1000-8000-00805f9b34fb
D	14:24:24.975	gatt.readCharacteristic(0000fff5-0000-1000-8000-00805f9b34fb)
E	14:24:25.707	Error 137 (0x89): GATT AUTH FAIL

0 Christin Lee over 5 years ago

TI__Guru 55305 points

Hi,

It's stated in our example readme that

"Characteristic 5 (UUID: FFF5)
This characteristic has read property only. It is 5 bytes, and its default value is 0x0102030405. It differs from the other characteristics in that it requires authentication. This is done by pairing the smartphone with the Simple Peripheral device. The process of doing this varies depending on the smartphone application and the operating system that is being used. Please see documentation on the operating system that you are using for more details. Some documentation for iOS can be found here, and some for android can be found here. If the Simple Peripheral device and the smartphone have not been paired, you will not see anything when you press the read button (this includes reading the characteristic user description). Once the devices are paired, pressing the read button will show the characteristic’s value as shown below:"

0 ke fan over 5 years ago in reply to Christin Lee

Expert 1890 points

thank you for this information. It seem the problem is the passcode is not the same on the app and on the soc.

Bluetooth®︎

Bluetooth forum

RTOS/CC2640R2F: ----[HELP] ble5_simple_peripheral_cc2640r2lp_app