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.

CC2651R3: Bluetooth forum

Part Number: CC2651R3
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Dear TI Support Team,

I am currently working on a BLE project using the CC2651R3 microcontroller and facing challenges integrating AES encryption/decryption via the AESECB driver. Below are the details of my development environment:

  • Microcontroller: CC2651R3
  • SDK Version: simplelink_cc13xx_cc26xx_sdk_7_41_00_17
  • Development Environment: Code Composer Studio (CCS) Version 12.7
  • Base Code: Project Zero example

Issue Description:

I am implementing secure communication using the AESECB driver for encryption and decryption in my BLE application. While I have successfully initialized the AESECB driver and set up encryption/decryption operations, I am facing the following challenges:

  1. Ensuring that encryption starts only after BLE initialization is fully complete.
  2. Properly integrating BLE and AESECB operations so that both can run concurrently without interference. Currently, it appears that only one function (either BLE or AES) can execute at a time.

Assistance Required:

  • Best practices for configuring BLE alongside AESECB encryption/decryption.
  • The recommended method to trigger encryption only after BLE initialization.
  • Debugging tips if encryption does not execute as expected.
  • Any existing TI examples or documentation demonstrating BLE with AESECB encryption.

I would appreciate any guidance, documentation, or example projects that could help me successfully integrate BLE and AES encryption in my project.

Thank you

Best regards,
Aarohi Shirbavikar

  • Hi,

    Thank you for reaching out. As a quick test, can you try adding a second instance of the AESECB driver to your SysConfig and using the second instance's name (CONFIG_AESECB_0 by default), for the desired operations? Does that allow the BLE operations to work as well?

    Best Regards,

    Jan