• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 228 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2640: Help with headless build for cc2640

Renan Santos Adriano
Mastermind 26505 points

Part Number: CC2640
Other Parts Discussed in Thread: CCSTUDIO

Hello Experts,

What we are doing
We currently build our CC2640 project in CCS. We are trying to automate this from the command line (CI) using the CCS headless build (Eclipse “server”) so we can compile without opening the IDE.

Questions

Passing preprocessor flags in headless builds
What is the recommended way to inject/override C/C++ preprocessor symbols for a one-off CI build (without permanently changing the project settings)?

Is there a supported command-line switch to pass something like FOO=1, BAR=xyz just for that build?

If possible, please share the exact ccstudio (or eclipsec) command example that CCS expects for adding defines at build time.

Producing Intel HEX output
Our project currently builds the default .out artifact. We need an Intel HEX file for flashing.

What is the recommended way to generate Intel HEX in a headless flow?

Should we call the TI hex/objcopy utility directly in a post-build step (inside the CCS project), or is there a preferred command-line tool invocation after the build completes?

If there are multiple options (e.g., TI ARM hex utility vs. objcopy), which one do you recommend for CC2640 projects, and what is the exact command line (e.g., output format flag for Intel HEX)?

Regards,

 Karhikeyan Pnnusamy

  • 0
    TI__Genius 16064 points

    Hello Karhikeyan Pnnusamy,

    I would recommend using the CCS CLI we offer rather than the Headless CDT, as per our Create and Build Projects Using Command Line we defer to CDT documentation for further support. 

    "These commands are specific to CCS and are different from the CDT headless commands. When working with CCS projects it is recommended to use the CCS specific commands rather than the CDT headless commands. The reverse holds true for non-CCS projects (standard Eclipse CDT projects). Do NOT use the the CCS specific commands to build standard Eclipse CDT projects. In those cases, use the CDT headless commands (check the standard Eclipse CDT documentation for details)"

    Thanks,
    Alex F