Studio Bluetooth Forum Discussions

What is the maximum data length we can use for one I2C transaction?

We are using CYW20721B2 module.

Information for function uint8_t wiced_hal_i2c_write(uint8_t* data, uint16_t length, uint8_t slave); mentions this:

/// ....Though any arbitrary length of data may be

/// written to the slave, atomic transactions greater than HW's capability

/// are not possible - they will be split into multiple transactions....

hi  Cypress:

  if cyw20706 need to set the i2s to slave mode? if  A2DP sink is mean ,the cyw20706 is in slave mode?? so the host should set in mast mode fo i2s?

Hello,

I am using WICED Studio 6.2 with CYBT-343026-01. I have around 400 CYBT-343026-01 modules and I want to flash my firmware into it. how can I flash my firmware in all CYBT-343026-01 without connecting to the computer? Is there any external device for OTA? or can I use 1 CYBT-343026-01 as a host device to flash all other modules?

How can I do this please help me.

Thanks in advance

Regards,

Neeraj

Hello,

I was able to write in the following communities.

[EZ-Serial Firmware for CYW2070x-based Modules] In Custom Local GATT, Write properties

This time, let me check how to create multiple Characteristics for one Service.

[SERVICE]                            /CAC,T=00,P=02,L=0012,D=002800B10C2000089A9EE21115A133333365

[Characteristics of READ]     /CAC,T=00,P=02,L=0015,D=032802180001B10C2000089A9EE21115A133333365

[Attribute]                              /CAC,T=01,P=86,L=0001,D=01

[Characteristics of WRITE]   /CAC,T=00,P=02,L=0015,D=032808180002B10C2000089A9EE21115A133333365

[Attribute]                              /CAC,T=01,P=8A,L=0001,D=00

After the above settings, I checked the /DLD command.

--------

:

:

@E,0024,DL,H=0016,R=001A,T=2800,P=00,U=0028

@E,0024,DL,H=0017,R=0018,T=2803,P=02,U=0328

@E,0040,DL,H=0018,R=0000,T=0000,P=02,U=01B10C2000089A9EE21115A133333365

@E,0024,DL,H=0019,R=0018,T=2803,P=08,U=0328

@E,0040,DL,H=001A,R=0000,T=0000,P=08,U=02B10C2000089A9EE21115A133333365

--------

[Question]

Shouldn't the part written in red be "R = 001A"?

When I executed Write from the Central (iPhone) app, the Handler of Write Event was "001A".

Best regards

上記の設定の後、/DLDコマンドを確認しました。

Hello,

I am using the EZ-Serial Firmware written in CYBT-343026.

If you execute the command (/ BTI) that starts the inquiry process, you should be able to check the information of peripheral devices.

What is the maximum number of this peripheral device list?

[Reference]

User Guide

[3.3.3 Connecting SPP Service of a WICED Module to Another BT Device]

Best regards

Hello guys,

I have a custom board with cyw20719b2, with a build setup using modus toolboox and wiced bt sdk v2.7.1 fdb3982.

We have 32khz crystal connected, I tired to initialize the rtc like this:

rtcConfig.rtcRefClock = RTC_REF_CLOCK_SRC_32KHZ;
rtcConfig.oscillatorFrequencykHz = RTC_REF_CLOCK_SRC_32KHZ;
rtc_init();

But with this I was getting a compilation error: undefined reference for rtcConfg

I'm able to resolve this issue following instructions from answer to this query on the forum:

RTC in CYBT-413055-02

The answer suggests this:

However to avoid undefined reference error, please include the below line to C:\Users\anpm\ModusToolbox_2.1\wiced_btsdk\dev-kit\baselib\20719B2\internal\20719B2\patches\patch.sym rtcConfig = 0x201b21;

With this change I'm able to successfully compile and able to set and get accurate rtc time using provided apis (rtc_setRTCTime & rtc_getRTCTime).

But now I need to use this api "rtc_getRTCRawClock" to get raw rtc time, but now again I'm getting this compilation error:

undefined reference for rtc_getRTCRawClock.

I tried to check if this (rtc_getRTCRawClock) symbol is present in the file:

\wiced_btsdk\dev-kit\baselib\20719B2\internal\20719B2\patches\patch.sym

But the symbol is not present in the above file.

Can you please let me know how do I fix this issue without updating the sdk ?

Do I need to add a symbol into this patch.sym for rtc_getRTCRawClock also ? if yes please provide the details.

thanks,

aniket

Hello,

I would like to confirm the following description in the CYBT-483056-02 datasheet.

https://www.cypress.com/file/511686/download

■ Certified up to +20 dBm for FCC and ISED

■ Certified up to +10 dBm for MIC and CE standards

Checking the Test report, the maximum output power of CE and MIC (Japan) is as follows.

RF Regulatory Certifications for CYBT-483039-02 EZ-BT™ XR Module - KBA224516

[CE]

-BT: 20dBm (Limit)

  * 1972087R-RF-CE-EN300328-BT3.0-EZ-BT WICED XR Module with Mesh-CYBT-483039-02, CYBT-483056-02, CYBT-483062-02-V1.0.pdf

-BLE: 20dBm (Limit)

  * 1972087R-RF-CE-EN300328-BLE-EZ-BT WICED XR Module with Mesh-CYBT-483039-02, CYBT-483056-02, CYBT-483062-02-V1.0.pdf

[MIC]

-BT: 20dBm [3mW / MHz] (Limit)

  * 1972087R-RF-MIC (BT 3.0)-EZ-BT WICED XR Module with Mesh-CYBT-483039-02, CYBT-483056-02, CYBT-483062-02-V1.0.pdf

-BLE: 10dBm (Limit)

  * 1972087R-RF-MIC (BT 4.0) -EZ-BT WICED XR Module with Mesh-CYBT-483039-02, CYBT-483056-02, CYBT-483062-02-V1.0.pdf

  * 1972087R-RF-MIC (BT 5.0)-EZ-BT WICED XR Module with Mesh-CYBT-483039-02, CYBT-483056-02, CYBT-483062-02-V1.0.pdf

Why does the datasheet limit CE and MIC to 10 dBm?

Can CE and MIC be used with the output Power as per the test report?

Best regards,

Takahashi

I am trying to create an event to send a Mesh message, but the wiced_bt_mesh_create_event function always seems to return NULL. Does anyone have an idea why this might be or how to fix this?

    wiced_bt_mesh_event_t *p_event = wiced_bt_mesh_create_event(
            0,
            0x0131, // MESH_COMPANY_ID_CYPRESS
            0x1000, // WICED_BT_MESH_CORE_MODEL_ID_GENERIC_ONOFF_SRV
            0,
            0);

I'm reopening this discussion after a long time of giving up on Mesh on this device, here is the older one. I was advised by DheerajP_41 to set the element_idx to 0(from 0x00) and to check if MESH_COMPANY_ID_CYPRESS and the model ID were defined correctly. I have tried those but wiced_bt_mesh_create_event still only returns NULL. I'm attaching my code where I marked my code with comments(// MY CODE BEGIN and // MY CODE END), the rest is just the mesh_onoff_client from snip/mesh/ in the SDK.

The device(CYBT-423028-02) is in a Mesh network containing another CYBT-423028-02 programmed with the mesh_onoff_server example from 20719-B1_Bluetooth/apps/snip/mesh/. I'm provisioning both devices, then I give the Generic OnOff Server and the Generic OnOff Client models the same app key, set both their publish addresses and subscription addresses to the same group(0xC000) but I also tried setting the publish address of the client to 0xFFFF and the unicast address of the server, it didn't change anything and wiced_bt_mesh_create_event() keeps returning NULL.

In case it's relevant, I'm reading the WICED_BT_TRACE outputs using PuTTY and a USB-UART bridge.

I'm just trying to send a set message from the client to the server and change the onoff state right now to keep things as simple as possible. If I should be using another function or go about this a different way, I would be glad if anyone could help me out. I'm also wondering if anyone else can recreate the issue or not.

Hello,

I have flashed the battery server example code from WICED studio 6.4 to CYBT 423028 Eval board, and battery client code to another board.

Not getting response from server.

I want to get the battery status periodically from battery server.

I have created periodic timer (5 Sec ) in Battery Client  and in that timer I am calling wiced_bt_mesh_create_event by passing the element index as 0, default Vendor Compony ID and Vendor Model ID, dst as 0, and app_key_idx as 0xffff. Event is getting created I believe, as  wiced_bt_mesh_create_event not returning NULL.

Once the event is created I am passing this event to wiced_bt_mesh_battery_client_send_get as an argument, it returns 8019 code.

On server side could not see request is getting received.

Both battery client and server are provisioned through Mehs_Lighting android Mobile application.

Is there any thing I am missing or doing wrong ?

This might be a lengthy post an i apologize in advance

I am trying to run a BLE server that transmits around 35-40KBytes/sec through notifications. I have the server and notifications up and running with BlueZ-5.54 interfacing over HCI with BT860 Laird bluetooth module that leverages CYW20704 A2 Chipset.

The problem is with HCI Event: Number of Completed Packets. From what I understand the bluetooth controller will send this event once it has transmitted buffered packets to indicate available capacity. Also it is manufacture specific and cannot be controlled.
The chipset can buffer up to 15 packets of length 251 each. I confirmed that by sending raw command using hcitool.

All good so far, here is the problem description:
     1. The applications sends 15 packets to the controller

     2. *After 2 x connection_interval_ms* Controller replies with HCI Event: Number of Completed Packets = 2

     3. This continues until all packets are sent. At the end, controller sends 8 HCI Event: Number of Completed Packets = 2/1, all 2 x connection_interval_ms apart

I am pasting output from "btmon" here for a better understanding of the situation(the important sections are separated by /*********break-lines******/).

From the output it is clear that the controller only transmits 2 ACL packet at a time and then waits 2xconnection_interval_ms. This really is the bottleneck of my BLE server, please let me know how I can improve it!

I have tried different connection intervals, mtu sizes and even different client apps(nRF connect and RaspberryPi gatt client) all give me the same results. As well as gone through documentation for BT860 and CYW20704.
Can someone please help me understand how I can fix this? Essentially,
1. Why are the packets buffered and not transmitted?
2. If they are being transmitted, why is it not reported by the controller? How do I know if this is a bug in the controller?

3. Why are "Number of Completed Packets" HCI event always 2 x connection intervals apart? How can I control its frequency?

/********************************************Initiate Connection and GATT Service discovery*****************************************/
> HCI Event: LE Meta Event (0x3e) plen 19                                     #289 [hci0] 1767.983447
      LE Connection Complete (0x01)
        Status: Success (0x00)
        Handle: 64
        Role: Slave (0x01)
        Peer address type: Random (0x01)
        Peer address: F5:2F:BD:4D:B4:A1 (Static)
        Connection interval: 7.50 msec (0x0006)
        Connection latency: 0 (0x0000)
        Supervision timeout: 4000 msec (0x0190)
        Master clock accuracy: 0x07
@ MGMT Event: Device Connected (0x000b) plen 13                           {0x0002} [hci0] 1767.983514
        LE Address: F5:2F:BD:4D:B4:A1 (Static)
        Flags: 0x00000000
        Data length: 0
@ MGMT Event: Device Connected (0x000b) plen 13                           {0x0001} [hci0] 1767.983514
        LE Address: F5:2F:BD:4D:B4:A1 (Static)
        Flags: 0x00000000
        Data length: 0
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2              #290 [hci0] 1767.983782
        Handle: 64
> HCI Event: Command Status (0x0f) plen 4                                     #291 [hci0] 1767.985754
      LE Read Remote Used Features (0x08|0x0016) ncmd 1
        Status: Success (0x00)
> ACL Data RX: Handle 64 flags 0x02 dlen 11                                   #292 [hci0] 1768.003893
      ATT: Read By Group Type Request (0x10) len 6
        Handle range: 0x0001-0xffff
        Attribute group type: Primary Service (0x2800)
> HCI Event: LE Meta Event (0x3e) plen 12                                     #293 [hci0] 1768.020620
      LE Read Remote Used Features (0x04)
        Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
        Handle: 64
        Features: 0xff 0x00 0x00 0x00 0x00 0x00 0x00 0x00
          LE Encryption
          Connection Parameter Request Procedure
          Extended Reject Indication
          Slave-initiated Features Exchange
          LE Ping
          LE Data Packet Length Extension
          LL Privacy
          Extended Scanner Filter Policies
< ACL Data TX: Handle 64 flags 0x00 dlen 16                                   #294 [hci0] 1768.020769
      LE L2CAP: Connection Parameter Update Request (0x12) ident 1 len 8
        Min interval: 24
        Max interval: 40
        Slave latency: 0
        Timeout multiplier: 400
< ACL Data TX: Handle 64 flags 0x00 dlen 18                                   #295 [hci0] 1768.034943
      ATT: Read By Group Type Response (0x11) len 13
        Attribute data length: 6
        Attribute group list: 2 entries
        Handle range: 0x0001-0x0006
        UUID: Generic Access Profile (0x1800)
        Handle range: 0x0007-0x000a
        UUID: Generic Attribute Profile (0x1801)
> HCI Event: LE Meta Event (0x3e) plen 11                                     #296 [hci0] 1768.043019
      LE Data Length Change (0x07)
        Handle: 64
        Max TX octets: 251
        Max TX time: 2120
        Max RX octets: 251
        Max RX time: 2120
> ACL Data RX: Handle 64 flags 0x02 dlen 10                                   #297 [hci0] 1768.050522
      LE L2CAP: Connection Parameter Update Response (0x13) ident 1 len 2
        Result: Connection Parameters accepted (0x0000)
> HCI Event: Number of Completed Packets (0x13) plen 5                        #298 [hci0] 1768.058490
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 11                                   #299 [hci0] 1768.065527
      ATT: Read By Group Type Request (0x10) len 6
        Handle range: 0x000b-0xffff
        Attribute group type: Primary Service (0x2800)
< ACL Data TX: Handle 64 flags 0x00 dlen 26                                   #300 [hci0] 1768.065867
      ATT: Read By Group Type Response (0x11) len 21
        Attribute data length: 20
        Attribute group list: 1 entry
        Handle range: 0x000b-0x0012
        UUID: Vendor specific (a79ef145-bde1-4bbd-8fbd-28d5dad70a97)
> ACL Data RX: Handle 64 flags 0x02 dlen 11                                   #301 [hci0] 1768.081234
      ATT: Read By Group Type Request (0x10) len 6
        Handle range: 0x0013-0xffff
        Attribute group type: Primary Service (0x2800)
< ACL Data TX: Handle 64 flags 0x00 dlen 9                                    #302 [hci0] 1768.081687
      ATT: Error Response (0x01) len 4
        Read By Group Type Request (0x10)
        Handle: 0x0013
        Error: Attribute Not Found (0x0a)
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #303 [hci0] 1768.095555
      ATT: Read Request (0x0a) len 2
        Handle: 0x000b
< ACL Data TX: Handle 64 flags 0x00 dlen 21                                   #304 [hci0] 1768.095684
      ATT: Read Response (0x0b) len 16
        Value: 970ad7dad528bd8fbd4be1bd45f19ea7
> HCI Event: Number of Completed Packets (0x13) plen 5                        #305 [hci0] 1768.096516
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: LE Meta Event (0x3e) plen 10                                     #306 [hci0] 1768.103986
      LE Connection Update Complete (0x03)
        Status: Success (0x00)
        Handle: 64
        Connection interval: 30.00 msec (0x0018)
        Connection latency: 0 (0x0000)
        Supervision timeout: 4000 msec (0x0190)
> ACL Data RX: Handle 64 flags 0x02 dlen 11                                   #307 [hci0] 1768.163413
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0001-0x0006
        Attribute type: Characteristic (0x2803)
< ACL Data TX: Handle 64 flags 0x00 dlen 20                                   #308 [hci0] 1768.163731
      ATT: Read By Type Response (0x09) len 15
        Attribute data length: 7
        Attribute data list: 2 entries
        Handle: 0x0002
        Value: 820300002a
        Handle: 0x0005
        Value: 020600012a
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #309 [hci0] 1768.223048
      ATT: Read Request (0x0a) len 2
        Handle: 0x0003
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #310 [hci0] 1768.223324
      ATT: Read Response (0x0b) len 22
        Value: 427261696e436f205261737062657272795069205374
> HCI Event: Number of Completed Packets (0x13) plen 5                        #311 [hci0] 1768.223995
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #312 [hci0] 1768.313032
      ATT: Read Request (0x0a) len 2
        Handle: 0x0006
< ACL Data TX: Handle 64 flags 0x00 dlen 7                                    #313 [hci0] 1768.313294
      ATT: Read Response (0x0b) len 2
        Value: 8000
> ACL Data RX: Handle 64 flags 0x02 dlen 9                                    #314 [hci0] 1768.373681
      ATT: Find Information Request (0x04) len 4
        Handle range: 0x0004-0x0006
< ACL Data TX: Handle 64 flags 0x00 dlen 18                                   #315 [hci0] 1768.373818
      ATT: Find Information Response (0x05) len 13
        Format: UUID-16 (0x01)
        Handle: 0x0004
        UUID: Characteristic Extended Properties (0x2900)
        Handle: 0x0005
        UUID: Characteristic (0x2803)
        Handle: 0x0006
        UUID: Appearance (0x2a01)
> HCI Event: Number of Completed Packets (0x13) plen 5                        #316 [hci0] 1768.373932
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #317 [hci0] 1768.433025
      ATT: Read Request (0x0a) len 2
        Handle: 0x0004
< ACL Data TX: Handle 64 flags 0x00 dlen 7                                    #318 [hci0] 1768.433350
      ATT: Read Response (0x0b) len 2
        Value: 0100
> ACL Data RX: Handle 64 flags 0x02 dlen 9                                    #319 [hci0] 1768.493683
      ATT: Find Information Request (0x04) len 4
        Handle range: 0x0007-0x0006
< ACL Data TX: Handle 64 flags 0x00 dlen 9                                    #320 [hci0] 1768.493961
      ATT: Error Response (0x01) len 4
        Find Information Request (0x04)
        Handle: 0x0007
        Error: Invalid Handle (0x01)
> HCI Event: Number of Completed Packets (0x13) plen 5                        #321 [hci0] 1768.493965
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #322 [hci0] 1768.553023
      ATT: Read Request (0x0a) len 2
        Handle: 0x0003
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #323 [hci0] 1768.553275
      ATT: Read Response (0x0b) len 22
        Value: 427261696e436f205261737062657272795069205374
> ACL Data RX: Handle 64 flags 0x02 dlen 9                                    #324 [hci0] 1768.613688
      ATT: Read Blob Request (0x0c) len 4
        Handle: 0x0003
        Offset: 0x0016
< ACL Data TX: Handle 64 flags 0x00 dlen 21                                   #325 [hci0] 1768.614021
      ATT: Read Blob Response (0x0d) len 16
        61 72 6b 20 47 41 54 54 20 53 65 72 76 65 72 00  ark GATT Server.
> HCI Event: Number of Completed Packets (0x13) plen 5                        #326 [hci0] 1768.614029
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #327 [hci0] 1768.904932
        Num handles: 1
        Handle: 64
        Count: 1
> HCI Event: LE Meta Event (0x3e) plen 10                                     #328 [hci0] 1776.593921
      LE Connection Update Complete (0x03)
        Status: Success (0x00)
        Handle: 64
        Connection interval: 7.50 msec (0x0006)
        Connection latency: 0 (0x0000)
        Supervision timeout: 4000 msec (0x0190)
> ACL Data RX: Handle 64 flags 0x02 dlen 11                                   #329 [hci0] 1788.592219
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x000b-0x0012
        Attribute type: Characteristic (0x2803)
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #330 [hci0] 1788.592438
      ATT: Read By Type Response (0x09) len 22
        Attribute data length: 21
        Attribute data list: 1 entry
        Handle: 0x000c
        Value: 100d00072c6b8a1e1aeda86b47cec24ebcd4e8
> ACL Data RX: Handle 64 flags 0x02 dlen 11                                   #331 [hci0] 1788.607574
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x000d-0x0012
        Attribute type: Characteristic (0x2803)
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #332 [hci0] 1788.607721
      ATT: Read By Type Response (0x09) len 22
        Attribute data length: 21
        Attribute data list: 1 entry
        Handle: 0x0010
        Value: 0c110008c6a6034ef06baf8549343533924732
> ACL Data RX: Handle 64 flags 0x02 dlen 11                                   #333 [hci0] 1788.622590
      ATT: Read By Type Request (0x08) len 6
        Handle range: 0x0011-0x0012
        Attribute type: Characteristic (0x2803)
< ACL Data TX: Handle 64 flags 0x00 dlen 9                                    #334 [hci0] 1788.622708
      ATT: Error Response (0x01) len 4
        Read By Type Request (0x08)
        Handle: 0x0011
        Error: Attribute Not Found (0x0a)
> HCI Event: Number of Completed Packets (0x13) plen 5                        #335 [hci0] 1788.623156
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #336 [hci0] 1788.637230
      ATT: Read Request (0x0a) len 2
        Handle: 0x000c
< ACL Data TX: Handle 64 flags 0x00 dlen 24                                   #337 [hci0] 1788.637352
      ATT: Read Response (0x0b) len 19
        Value: 100d00072c6b8a1e1aeda86b47cec24ebcd4e8
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #338 [hci0] 1788.652248
      ATT: Read Request (0x0a) len 2
        Handle: 0x0010
< ACL Data TX: Handle 64 flags 0x00 dlen 24                                   #339 [hci0] 1788.652361
      ATT: Read Response (0x0b) len 19
        Value: 0c110008c6a6034ef06baf8549343533924732
> HCI Event: Number of Completed Packets (0x13) plen 5                        #340 [hci0] 1788.653195
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 9                                    #341 [hci0] 1788.697157
      ATT: Find Information Request (0x04) len 4
        Handle range: 0x000e-0x0012
< ACL Data TX: Handle 64 flags 0x00 dlen 18                                   #342 [hci0] 1788.697287
      ATT: Find Information Response (0x05) len 13
        Format: UUID-16 (0x01)
        Handle: 0x000e
        UUID: Characteristic User Description (0x2901)
        Handle: 0x000f
        UUID: Client Characteristic Configuration (0x2902)
        Handle: 0x0010
        UUID: Characteristic (0x2803)
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #343 [hci0] 1788.712242
      ATT: Read Request (0x0a) len 2
        Handle: 0x000e
< ACL Data TX: Handle 64 flags 0x00 dlen 18                                   #344 [hci0] 1788.712447
      ATT: Read Response (0x0b) len 13
        Value: 4545472052656164696e677300
> HCI Event: Number of Completed Packets (0x13) plen 5                        #345 [hci0] 1788.712787
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #346 [hci0] 1788.727224
      ATT: Read Request (0x0a) len 2
        Handle: 0x000f
< ACL Data TX: Handle 64 flags 0x00 dlen 5                                    #347 [hci0] 1788.727405
      ATT: Read Response (0x0b) len 0
        Value: 
> HCI Event: Number of Completed Packets (0x13) plen 5                        #348 [hci0] 1788.749650
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 9                                    #349 [hci0] 1788.764653
      ATT: Find Information Request (0x04) len 4
        Handle range: 0x0012-0x0012
< ACL Data TX: Handle 64 flags 0x00 dlen 10                                   #350 [hci0] 1788.764773
      ATT: Find Information Response (0x05) len 5
        Format: UUID-16 (0x01)
        Handle: 0x0012
        UUID: Characteristic User Description (0x2901)
> ACL Data RX: Handle 64 flags 0x02 dlen 7                                    #351 [hci0] 1788.779703
      ATT: Read Request (0x0a) len 2
        Handle: 0x0012
< ACL Data TX: Handle 64 flags 0x00 dlen 18                                   #352 [hci0] 1788.779898
      ATT: Read Response (0x0b) len 13
        Value: 4545472052656164696e677300
> HCI Event: Number of Completed Packets (0x13) plen 5                        #353 [hci0] 1788.794650
        Num handles: 1
        Handle: 64
        Count: 2
> ACL Data RX: Handle 64 flags 0x02 dlen 9                                    #354 [hci0] 1790.062100
      ATT: Write Request (0x12) len 4
        Handle: 0x000f
          Data: 0100
/************************************************** START THE NOTIFICATIONS **********************************************************/
> ACL Data RX: Handle 64 flags 0x02 dlen 9                                    #354 [hci0] 1790.062100
      ATT: Write Request (0x12) len 4
        Handle: 0x000f
          Data: 0100
< ACL Data TX: Handle 64 flags 0x00 dlen 5                                    #355 [hci0] 1790.062426
      ATT: Write Response (0x13) len 0
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #356 [hci0] 1790.063602
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 54f003008bce915f8bce915f8bce915f5483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #357 [hci0] 1790.064609
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #358 [hci0] 1790.065696
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #359 [hci0] 1790.066768
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #360 [hci0] 1790.067887
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #361 [hci0] 1790.068955
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #362 [hci0] 1790.070077
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #363 [hci0] 1790.071196
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #364 [hci0] 1790.072277
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #365 [hci0] 1790.073346
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #366 [hci0] 1790.074458
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #367 [hci0] 1790.075560
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #368 [hci0] 1790.076665
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #369 [hci0] 1790.077775
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
> HCI Event: Number of Completed Packets (0x13) plen 5                        #370 [hci0] 1790.084497
        Num handles: 1
        Handle: 64
        Count: 2
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #371 [hci0] 1790.084532
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #372 [hci0] 1790.084546
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
> HCI Event: Number of Completed Packets (0x13) plen 5                        #373 [hci0] 1790.099497
        Num handles: 1
        Handle: 64
        Count: 2
/*******************************************BREAK: SKIP TO END OF TRANSFER ************************************************/
> HCI Event: Number of Completed Packets (0x13) plen 5                        #493 [hci0] 1790.736984
        Num handles: 1
        Handle: 64
        Count: 2
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #494 [hci0] 1790.737022
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #495 [hci0] 1790.737037
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
> HCI Event: Number of Completed Packets (0x13) plen 5                        #496 [hci0] 1790.751975
        Num handles: 1
        Handle: 64
        Count: 2
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #497 [hci0] 1790.752012
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
< ACL Data TX: Handle 64 flags 0x00 dlen 27                                   #498 [hci0] 1790.752027
      ATT: Handle Value Notification (0x1b) len 22
        Handle: 0x000d
          Data: 0000000030b6510100000000e8b651015483ac7e
> HCI Event: Number of Completed Packets (0x13) plen 5                        #499 [hci0] 1790.766970
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #500 [hci0] 1790.782000
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #501 [hci0] 1790.796968
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #502 [hci0] 1790.811970
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #503 [hci0] 1790.826973
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #504 [hci0] 1790.841972
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #505 [hci0] 1790.856964
        Num handles: 1
        Handle: 64
        Count: 2
> HCI Event: Number of Completed Packets (0x13) plen 5                        #506 [hci0] 1791.031954
        Num handles: 1
        Handle: 64
        Count: 1