User's Guide

© Copyright LM Technologies Ltd Page 68 of 70
www.lm-technologies.com
LM074 SPP with GAP Central Application v1.1
5. uuid[0] = 0x00112233, uuid[1] = 0x44556677, uuid[2] =
0x8899aabb, and uuid[3] = 0xccddeeff.
6. If the service-UUID is 128-bit, it is completely mentioned in the report
of FindServ e.g. “00005500-d102-11e1-9b23-00025b00a5a5”
7. If the characteristic has 128-bit UUID then only first 32 bits are shown
e.g.
8. “00005501” is shown whereas the actual 128-bit UUID is “00005501-
D10211E1-9B230002-5B00a5a5” here the remaining bits are same as
that of the 128-bit Service UUID shown above.
8.4 GATT_Status_code
The BLE stack outputs an error if the required operation fails. The table below
lists the possible error codes with a description.
Sr No
Error code
Error description
1
0x0
gatt_status_success
2
0x1
gatt_status_invalid_handle
3
0x2
gatt_status_read_not_permitted
4
0x3
gatt_status_write_not_permitted
5
0x4
gatt_status_invalid_pdu
6
0x5
gatt_status_insufficient_authentication
7
0x6
gatt_status_request_not_supported
8
0x7
gatt_status_invalid_offset
9
0x8
gatt_status_insufficient_authorization
10
0x9
gatt_status_prepare_queue_full
11
0xa
gatt_status_attr_not_found
12
0xb
gatt_status_not_long
13
0xc
gatt_status_insufficient_encr_key_size
14
0xd
gatt_status_invalid_length
15
0xe
gatt_status_unlikely_error
16
0xf
gatt_status_insufficient_encryption
17
0x10
gatt_status_unsupported_group_type
18
0x11
gatt_status_insufficient_resources
19
0x12
gatt_status_application_error
20
0x13
gatt_status_initialising