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.

CCS/LAUNCHXL-CC1350: XDCToosl Bug Report

Part Number: LAUNCHXL-CC1350

Tool/software: Code Composer Studio

Hello:

The default configuration for the sample projects is to split them over two projects. The instructions for combining them into one project is out of date (see here). However, I managed to get the project configured using the documentation as a rough guide. However, although there were no errors in the build setup, the build failed with an error about the symbol "DeviceFamily_XYZ" not being defined, despite the fact that the symbol is clearly defined in the build's Symbol settings.

The issue ended up being that the XDCTools section did not have the symbol defined. This shouldn't have happened and required a lot of time on my part to identify the root cause of the issue. Please submit a bug ticket to remove this line and have it reference the project build defines instead, or alternatively to include information in the #error message on how to resolve the issue using the XDCTools configuration page.

Thank you,

Michael

  • I failed to mention that the path to this option is:

    Project Properties->CCS Build->XDCTools->Advanced Options. Within this window, there is a textbox labelled "Additional compiler options (--compileOptions)". This box needs to contain '" -DDeviceFamily_CC13X0 "'. Be sure to include the double quotes (but not the single quotes).
  • Hi Michael,

    What SDK version are you working of?

    Looking at the documentation, it stated at the bottom of the page that you (working on a SDK > = 1.4) need to add "${COMPILER_FLAGS} " under Project Properties->CCS Build->XDCTools->Advanced Options. This would make it use all the compiler specified flags and defines just like you would expect it to.
  • Hi M-W,

    Great! I just tested that and it works. FYI, I used a sample project to identify the settings above (I'm not sure which one), so those hard code the platform string over using the variable and maybe should be updated.

    This is the SDK version: "simplelink_cc13x0_sdk_1_60_00_21". What's the documentation that you're looking at?

    Could the next release of CCS alter this dialog so that ${COMPILER_FLAGS} is the default value when XDCTools is added to the project ( I was prompted to add it once I copied and pasted the .cfg file into my project and removed the dependency on the tirtos project )? Perhaps it could also be grayed out for protection, with an override option that was toggle it from read-only to read-write for people wishing to declare the value themselves? This latter suggestion might not justify investment, but I thought I'd share the idea.
  • Glad it helped!

    The problem with the ${COMPILER_FLAGS} approach is that it can not be used in the normal dual project setup as the depending project (thus the hard coded string).

    I was actually looking at the documentation you linked in your first post, just above the last picture :)

    I will forward the idea of the of defaulting to ${COMPILER_FLAGS} to the team, it sounds to me like it could be of value.