• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 556 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2564B: HCI_COMM_Protocol_t definition

Koichiro Tashiro
Mastermind 22945 points


Hi,

This is additional questions to below E2E.
https://e2e.ti.com/support/wireless_connectivity/bluetooth_cc256x/f/660/t/534589

Q1) What is exact difference in UART function between cpHCILL and cpHCILL_RTS_CTS ?

Q2) Are other definitions (cpBCSP, cpBCSP_Muzzled, cpH4DS, … etc.) used somewhere ?
Or they are just defined, but never used ?

Thanks and regards,

Koichiro

  • 0
    TI__Mastermind 35795 points

    hi, your query has been assigned to BT expert. We will get back to you shortly
    Saurabh

  • 0
    TI__Mastermind 29311 points
    Hi Koichiro-san,

    As the above post mentions there is no difference between the cpHCILL and cpHCILL_RTS_CTS implementation on the stack side.

    BCSP(Bluetooth Core Serial Protocol) is the same thing as the 3-wire UART. Since the HCI drivers of the ti bluetooth stack are generic for any transport protocol, it has compatibility built-in all these protocols. However, the HAL in all the ti bluetooth stack releases only has the implementation of the HCILL options which has the proprietary sleep mode with the standard H4. So the other definitions are defined for compatibility but only the HCILL is used.

    Best regards,
    Vihang