• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 51 subscribers
  • Views 471 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.

SIMPLELINK-CC2640R2-SDK: v2.30: Bluetooth Erratum 10734: Secure Pairing Code Implementation?

Markel Robregado
Guru 86785 points
Part Number: SIMPLELINK-CC2640R2-SDK
Other Parts Discussed in Thread: CC2640R2F, BLE-STACK

Hi,

   I have seen the Secure OAD code. But where is the Secure Pairing Code that will address the Bluetooth Erratum 10734. It is not implemented at Simple Peripheral. Do you have document that explains this Secure Pairing to address the Bluetooth Erratum 10734?

-kel

  • 0
    TI__Guru* 83011 points
    Hi Markel,

    You are mixing concepts. Secure OAD is a TI implementation of OAD over BLE, it has noting to do with the Bluetooth Core Spec.

    Pairing and Bonding are concepts in the Bluetooth Core Spec (that you can add to your Secure OAD application). Information about Bluetooth Erratum 10734 and the TI devices can be found in this sticky post: e2e.ti.com/.../713044
  • 0 in reply to Marie H
    Guru 86785 points

    Marie H said:
    You are mixing concepts. Secure OAD is a TI implementation of OAD over BLE, it has noting to do with the Bluetooth Core Spec.

    Your assumption not mine. I said "I have seen the Secure OAD code".

    Here is the exact scenario:

    Markel: Team, I will move our firmware from CC2640R2F SDKv1.50 to use CC2640R2F SDKv2.20, because of Bluetooth Erratrum 10734. There is sticky post about it. See, link.

    Team: Okay, you have moved or firmware to use CC2640R2F SDK v2.20. But, I see we still use the same method in pairing by using a public key or random key. What is the code to address Bluetooth Erratum 10734?

    Markel: Let me ask at TI E2E Forum . . .

    -kel

  • 0 in reply to Markel Robregado
    TI__Guru* 83011 points
    Hi Markel,

    The public key validation is BLE-Stack code, provided as part of the libraries in the BLE-Stack and thus not provided as source code. If you are using the CC2640R2F 2.20 SDK you are using the updated BLE-Stack.
  • 0 in reply to Marie H
    Guru 86785 points
    Okay, If someone ask me why we using SDKv2.20 I will refer to your reply.
  • 0 in reply to Markel Robregado
    TI__Guru* 83011 points
    Hi Markel,

    I made a mistake. The errata fix was implemented in the ECCROM driver (ECCROMCC26XX.c), not in a BLE-Stack library.