• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 916 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HCI_Read_Clock and HCI_Read_Clock_Offset in CC2564 (BLE)

user4396656
Prodigy 10 points
Other Parts Discussed in Thread: CC2564

Hi!

I'm trying to read the Bluetooth Clock via HCI_Read_Clock on the CC2564 (LE Connection). I get valid results when asking for the "Local Clock" (Parameter 0x00 0x00 0x00, see Core Specs *). But as soon as I try to get the "Piconet Clock" by applying a connection handle, an error occurs ("Unknown Connection Identifier").

Same problem with the HCI_Read_Clock_Offset command: Always results in an "Unknown Connection Identifier" error. (And yes: The connection identifier is valid...)

Is this a limitation of the CC2564 or am I missing something?

* Core Spec for the HCI Commands:

Read Clock Command (HCI_Read_Clock)
BLUETOOTH SPECIFICATION Version 4.2 [Vol 2, Part E]
7.5.6 Read Clock Command

Read Clock Offset Command (HCI_Read_Clock_Offset)
BLUETOOTH SPECIFICATION Version 4.2 [Vol 2, Part E]
7.1.24 Read Clock Offset Command

  • 0
    TI__Guru* 85400 points

    Hi,

    I believe those commands are for classic BT, and not for BLE.

    From spec:

    "When the BR/EDR Controller receives the Read_Clock_Offset command, the

    BR/EDR Controller shall send the Command Status event to the Host. If this

    command was requested at the master and the Link Manager has completed

    the LMP messages to obtain the Clock Offset information, the BR/EDR Controller

    on the local BR/EDR Controller shall send a Read Clock Offset Complete

    event to the Host."


    There is no reference to the LE Controller there.


    Regards,
    Gigi Joseph.