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.

CC2745R10-Q1: Image encryption support

Part Number: CC2745R10-Q1

Tool/software:

Hello all,

I'm currently testing the basic_ble_dual_oad project from the simplelink_lowpower_f3_sdk_9_10_00_83.

After building the project in Code Composer Studio (CCS), I noticed that the output files (sb.bin and sb.hex) appear to be signed. Are these images also encrypted, or are they only signed?

If encryption is not applied by default, what steps are required to enable encryption for these images?

Additionally, does TI plan to support image encryption in future SDK releases?

Regards,

Aslam

  • Hello Mohammed, 

    The images are not encrypted or signed as the .hex or .bin files. To apply a signature, you will need to use the sbtool.exe for ROM Secure Boot, or imgtool.exe for MCUboot. 

    The customer is responsible for encrypting the binary/hex file. I know we have a plan to decrypt using MCUBoot. I am not sure if we will update the signature executable (imgtool.exe) to allow for encryption as well. I will double check and respond if I find any important timelines. 

    Thanks,
    Isaac 

  • Hello Mohammed, 

    The team let me know the CC2642 device supports image decryption for MCUBoot and encryption with an executable in the SDK. Unfortunately, the CC2745R10-Q1 MCUBoot does not support image decryption. There is a plan to add this to a future SDK, but I do not have a timeline. 

    Thanks, 
    Isaac