• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 94 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

LP-CC2652R7: SECURE_BIM

LP-CC2652R7: SECURE BOOT

Gayathri GP
Prodigy 50 points
Part Number: LP-CC2652R7
Other Parts Discussed in Thread: CC2652R7

Hi team,

Had this development board and the Project Zero worked as intended; the on-board led and button service functions properly.(Default : Unsecure build configuration)

Requirement is I want to change the current BIM to Secure_BIM. The following changes were made to enable Secure Boot :

  1. Imported the ccs bim_onchip_LP_CC2652R7_nortos_ticlang project and changed the build configuration to Release.
  2. Using the key_generate.py script, I generated a new key pair and edited the bim_onchip_main.c file to change the public keys and signer information.
  3. Imported the project_zero_LP_CC2652R7_tirtos7_ticlang project (Release:Active) and changed the SYS_Config to enable OAD BLE Security. Used the Ti private key to generate the signature.

When I load this bim and project zero application to launchpad, it works well. What I expected was that the projectzero application would get rejected because the private key used to generate the signature of the application was one that Ti provided and the public key used in bim was a newly generated key.

Is this procedure to enable secure boot correct?

One more query is Why is the signature value different for each build ( project_zero_LP_CC2652R7_tirtos_ticlang(Active-Release)), even though the private-public key pair and application are the same?

Could you help?

Thanks & Regards