Identification of connected APP in NRF52840 devices.

RE: Identification of connected APP in NRF52840 devices.

run_ar — Thu, 25 Nov 2021 08:30:10 GMT

Hi,

If you are trying to advertise two 128 bit UUID's in the advertisement packet you are probably overflowing the maximum allowed size of the packet. Try moving one of them to the scan response packet. In addition you should look at the error message you are getting to see what is failing.

RE: Identification of connected APP in NRF52840 devices.

sne_333 — Wed, 24 Nov 2021 12:10:10 GMT

I am going step by step. I created 2 services: -

Service 1

#define BLE_UUID_RCBR_SERVICE 0xD6E2 /**< The UUID of the R3charge Borrower Service. */

#define RCBR_SERVICE_UUID_TYPE BLE_UUID_TYPE_VENDOR_BEGIN /**< UUID type for the RCBR Service (vendor specific). */

#define BLE_UUID_RCBR_NOTIF_CHARACTERISTIC 0xD7E2 //0xD7E2 /**< The UUID of the Notification Characteristic. */
#define BLE_UUID_RCBR_SETTING_CHARACTERISTIC 0xD7E4 //0xD7E4 /**< The UUID of the Setting Characteristic. */

#define BLE_RCBR_MAX_NOTIF_CHAR_LEN BLE_RCBR_MAX_DATA_LEN /**< Maximum length of the RX Characteristic (in bytes). */
#define BLE_RCBR_MAX_SETTING_CHAR_LEN BLE_RCBR_MAX_DATA_LEN /**< Maximum length of the TX Characteristic (in bytes). */

#define RCBR_BASE_UUID {{0x77, 0x9a, 0x0c, 0x20, 0x00, 0x08, 0x6e, 0xaa, 0xe3, 0x11, 0x76, 0x34, 0xe1, 0xd6, 0x48, 0x75}} /**< Used vendor specific UUID. */

#define OPCODE_LENGTH 1
#define HANDLE_LENGTH 2

service 2:

#define BLE_UUID_RCLR_SERVICE 0xD6E3 /**< The UUID of the R3charge Lender Service. */

#define RCLR_SERVICE_UUID_TYPE BLE_UUID_TYPE_VENDOR_BEGIN /**< UUID type for the RCLR Service (vendor specific). */

#define BLE_UUID_RCLR_NOTIF_CHARACTERISTIC 0xD7E3 /**< The UUID of the Notification Characteristic. */
#define BLE_UUID_RCLR_SETTING_CHARACTERISTIC 0xD7E5 /**< The UUID of the Setting Characteristic. */

#define BLE_RCLR_MAX_NOTIF_CHAR_LEN BLE_RCLR_MAX_DATA_LEN /**< Maximum length of the RX Characteristic (in bytes). */
#define BLE_RCLR_MAX_SETTING_CHAR_LEN BLE_RCLR_MAX_DATA_LEN /**< Maximum length of the TX Characteristic (in bytes). */

#define RCLR_BASE_UUID {{0x66, 0x9a, 0x0c, 0x20, 0x00, 0x08, 0x6e, 0xaa, 0xe3, 0x11, 0x76, 0x34, 0xe1, 0xd6, 0x48, 0x75}} /**< Used vendor specific UUID. */

#define OPCODE_LENGTH 1
#define HANDLE_LENGTH 2

MY memory settings are as follows:-

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0x27000

FLASH_SIZE=0xd9000

RAM_START=0x200059A4

RAM_SIZE=0x3a65C

===========================

FLASH RX 0x0 0x100000;RAM1 RWX 0x20000000 0x40000

I am getting error at ble_advertising_init function. I have set NRF_SDH_BLE_VS_UUID_COUNT = 2 but still i am getting error. What might be the issue?

RE: Identification of connected APP in NRF52840 devices.

run_ar — Fri, 19 Nov 2021 09:15:56 GMT

You can configure different security levels for different services. So it can be possible to require Authentication for only one service. But if you are planning to require bonding for the other service as well, you need to remember that the security level is "negotiated" between the devices, so after they exchange capabilities they will use the highest possible security level based on those capabilities. If you control both ends of the link I guess you could have an open characteristic that you use to tell the peer which capabilities it should use during bonding, but not sure why you would want that...

RE: Identification of connected APP in NRF52840 devices.

sne_333 — Fri, 19 Nov 2021 06:26:32 GMT

Yes Thank you so much. I was able to test the Glucose application in sdk15. Sdk 17 I got compilation errors. I understand how the authentication works. I have 2 services for 2 respective apps in my project. So can I add the authentication only for one service in the code?

RE: Identification of connected APP in NRF52840 devices.

run_ar — Tue, 16 Nov 2021 14:42:09 GMT

Hi,

Since our DK doesn't have a display or keyboard most example does not enable the Authentication feature. but you could look at the nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_gls example. and remember to connect to the comport to see the passkey. See Glucose Application for additional details.

RE: Identification of connected APP in NRF52840 devices.

sne_333 — Tue, 16 Nov 2021 05:50:35 GMT

Hi I tried to test the example you shared. The NRF connect app still gets connected without any authentication. Please help me on this.

I was not able to compile the sdk17 version ble_app_hrs. It gave me some errors.

tried testing with sdk15 version code. Still no authentication.

RE: Identification of connected APP in NRF52840 devices.

fhfs — Thu, 28 Oct 2021 13:35:57 GMT

The hrs example has multiple services enabled and uses bonding and encryption.
nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_hrs

So lets say App A Connects to the device without bonding and encryption and reads/writes from an unprotected service/characteristic.

App B connects and bonds to the device and reads/writes to a protected service/characteristic.

App B bonding to the device will cause a "BLE_GAP_EVT_AUTH_STATUS" event with status success. Here you will know that App B is connected and bonded.

Maybe it might be better to actually tell the device what App is connecting to the device, through writing to a characteristic. To avoid the confusion if App A also bonds.

RE: Identification of connected APP in NRF52840 devices.

sne_333 — Thu, 28 Oct 2021 10:41:12 GMT

okay.. Thanks..

for ble authentication can you suggest me some code examples to see?

RE: Identification of connected APP in NRF52840 devices.

fhfs — Thu, 28 Oct 2021 10:26:30 GMT

Ofcourse

RE: Identification of connected APP in NRF52840 devices.

sne_333 — Thu, 28 Oct 2021 10:09:38 GMT

Okay but can a peripheral device connect to two apps at a time?

RE: Identification of connected APP in NRF52840 devices.

fhfs — Thu, 28 Oct 2021 08:05:56 GMT

You kind of already answered your own question.

Identify by BLE authentication or identify by service. Both solutions seem ok