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.

CC1354R10: How to assign MCUBOOT Version number with application code instead of post build steps

Part Number: CC1354R10


Tool/software:

Dear TI Community,

May you please assist myself and future others that may be viewing this post.

1. Would you please describe how to assign a MCUBoot version number inside the application code rather than adding it via the post-build steps in project properties. I listed the current recommended approach towards assigning a version number below:



     ${CG_TOOL_ROOT}/bin/tiarmobjcopy ${BuildArtifactFileBaseName}.out --output-target binary ${BuildArtifactFileBaseName}_noheader.bin --remove-section=.ccfg


     ${COM_TI_SIMPLELINK_CC13XX_CC26XX_SDK_INSTALL_DIR}/tools/common/mcuboot/imgtool sign --header-size 0x100 --align 4 --slot-size 0xF4000 --version 2.0.0 --pad-header --pad --key ${PROJECT_ROOT}/Test_certificate_header.pem ${BuildArtifactFileBaseName}_noheader.bin ${BuildArtifactFileBaseName}-unencrypted.bin


Zephyr has a KConfig option "CONFIG_MCUBOOT_IMAGE_VERSION" which allows the application code to interact with the py imgtool to sign image during compilation. Does TI provide any similar support?

2. May you please also describe how to debug using the mcuboot signed image rather than the _noheader.bin, i.e. what should the post-build steps be to enter debug mode using ...unencrypted.bin.

Kind Regards

Brenton Chetty

  • Hi, I found a workaround.

    In Project_Properties, added a variable, then linked that variable with Predefined_Symbols, then accessed that variable in Application code. I realize that there is no possible way to get the Application code to change the actual version number (in Post-build step) during compilation.