CCS/CC1352R: makefile and CCS Build Variables

Igor Evdokimov

Part Number: CC1352R

Tool/software: Code Composer Studio

Hello.

I need to add some information to the name of the generated hex file.
I get the variable HASH_INFO in the makefile.init.

But when I try to apply it in the builder settings, nothing comes of it. What am I doing wrong ?
Sample makefile.init

HASH_INFO := $(shell git rev-parse --short HEAD)
$(info HASH_INFO: $(HASH_INFO))
COMPILER_FLAGS += --define=HASH_TAG=$(HASH_INFO)

Post-build steps:

${CG_TOOL_HEX} -order MS --memwidth=8 --romwidth=8 --intel -o ${HASH_INFO}.hex ${ProjName}

At compilation console, the value of this variable is displayed:
HASH_INFO: 89c796f

But as a result, I get blank name of a".hex" file

And the resulting line for the postbuild looks like this:

<Linking>
Finished building target: "KeypadPlus_1352.out"
 
HASH_INFO: 89c796f
C:/ti/ccs1000/ccs/tools/compiler/ti-cgt-arm_20.2.0.LTS/bin/armhex -order MS --memwidth=8 --romwidth=8 --intel -o .hex KeypadPlus_1352

Help me deal with this problem. Unfortunately, I do not have experience working with makefiles.

over 5 years ago

0 Igor Evdokimov over 5 years ago

Intellectual 775 points

As a result, I want to get the file name corresponding to HASH_INFO.

example: 89c796f.hex

0 AartiG over 5 years ago

TI__Guru**** 173310 points

In order to be able to use HASH_INFO in the output file name, it needs to be defined as a CCS build variable. In your use-case it is not a CCS variable, hence does not work.

I don't know of a way to propagate the hash value from the way you have created it into a build variable. It is possible the other way around - i.e., specify the hash value as a build variable and then access it in the C code, as described in this page: https://software-dl.ti.com/ccs/esd/documents/ccs_variables_in_source_code.html

Here is a related thread on this topic: https://e2e.ti.com/support/tools/ccs/f/81/t/526557

Code Composer Studio™︎

Code Composer Studio forum

CCS/CC1352R: makefile and CCS Build Variables