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.

CC2340R5: PEM Key Problem in code

Part Number: CC2340R5
Other Parts Discussed in Thread: UNIFLASH,

Tool/software:

I have used these two resources to have a security feature in my basic_ble_oad_onchip application i.e. https://software-dl.ti.com/simplelink/esd/simplelink_cc13x2_26x2_sdk/4.30.00.54/exports/docs/ble5stack/ble_user_guide/html/oad-secure/oad-types.html#:~:text=There%20are%20two%20methods%20of,installed%20and%20executed%20on%2Dchip. & https://software-dl.ti.com/simplelink/esd/simplelink_lowpower_f3_sdk/7.20.01.10/exports/docs/ble5stack/ble_user_guide/html/oad-mcuboot/imgtool.html .According to these resources , I have changed the PEM key in ti sdk(C:\ti\simplelink_lowpower_f3_sdk_8_10_01_02\source\third_party\mcuboot). But after changing the PEM key in the ti sdk using the PEM key generator(https://8gwifi.org/sshfunctions.jsp).The application code has stopped advertising in my mobile app. But, if i try to debug the application code in CCS it advertises. Why is this happening?

And also, can you suggest any security feature for the basic_ble_oad_onchip application so that it can be secured while doing the OAD through TI simplelink mobile app.

Waiting for a fruitful response. 

  • Hi,

    Can you share how you are flashing the application? Are you flashing the MCUboot image along with the application image in Uniflash?

    Best Regards,

    Jan

  • Hi Jan

    These files I am flashing in my micro I am including mcu boot from location (C:\ti\simplelink_lowpower_f3_sdk_8_10_01_02\examples\rtos\LP_EM_CC2340R5\ble5stack\hexfiles) 

    and basic persistent and OAD on chip bin files from the release folder of their project.

    Waiting for a fruitful response.

  • Hi,

    Thank you for the additional information. Can you clarify what you mean by debugging the project? Do you meant that after you flash the device, if you reset and connect to the running target, then the advertisements starts? Or do you mean that clicking on debug in CCS (which flashes, resets and connects) leads to the device advertising?

    Best Regards,

    Jan