CC2640R2F: AES encryption in CC2640R2F

- "What I understood is -AES_ECB_EncryptData- API does not work in CC2640r2f.": Based on?
- Why do you want to use ECB: crypto.stackexchange.com/.../can-someone-explain-the-ecb-penguin
- See this: e2e.ti.com/.../654599 for some examples on implementation.

Based on ?: I read it over TI E2E only.I am not sure though.Will it work ?
Why do you want to use ECB : I dont know which one is efficient AES technique.Could you please suggest which one to use.

It's up to the user to select a AES mode that the user want to use and give the required security. As the link I posted shows, ECB is not the most secure mode. 

As far as I know it's no issues with the ECB API. If you find information that suggest otherwise, please post the link. 

e2e.ti.com/.../2125452

check out here about the API use in CC2640r2f

I see that I misunderstood some. I thought about ECB API described in the doxygen documentation, not AES_ECB_EncryptData()

As JXS writes in the post you are referring to you should look at the code snippets in the doxygen documentation.

I have understood the AEC CCM example from simplelink_cc2640r2_sdk_1_50_00_58/docs/tidrivers/doxygen/html/_crypto_c_c26_x_x_8h.html

but I want to encrypt original advertisement data given in Simple Peripheral code.How to encrypt that data,any example ?

Any reason why you want to use crypto on to of the security built in in the stack: dev.ti.com/.../gapbondmngr.html

Any reason why you want to use crypto on to of the security built in in the stack: Privacy concern.

Will you please tell how to encrypt advertData[]

Hi Joakim,

Could you please tell.
Which field of the below lines have the encrypted data in it ? I want to send it as advertisement(instead of advertData[]).(OR how to check encrypted data.)

trans.msgIn = (char *) &(ccmSetup.clearAndCipherText[0]); // Message is encrypted in place
trans.msgOut = (char *) &(ccmSetup.clearAndCipherText[clearTextLength]); // MAC will be written to this position
status = CryptoCC26XX_transact(handle, (CryptoCC26XX_Transaction *) &trans);