Other Parts Discussed in Thread: CC2652R, SYSCONFIG
I'm working with a customer that is creating and using their own *.projectspec files, to generate CCS projects for the CC2652R, which uses the TI SimpleLink SDK for CC13x2_26x2. What we are finding is that when the projectspec is uses with the CCS Import tools, CCS always sets COM_TI_SIMPLELINK_CC13X2_26X2_SDK_INSTALL_DIR to point to the "latest" version installed under C:/ti and picked up by CCS. However, both the customer, as well as myself supporting the customer, need to have multiple versions of the SDK installed in CCS to support multiple projects of development on different versions.
How can we force a projectspec to use a specific SDK version for the COM_TI_SIMPLELINK_* variable during the import project? If we perform the import occurs from a SimpleLink SDK example tree itself, it seems to always choose the parent SDK version correctly, not the "latest". However, I cannot seem to discover the mechanism by which this happens. It seems like "magic" is occurring.
The customer needs to be able to maintain the custom pojectspec files outside the SDK tree. It is not an acceptable solution to pollute the SDK sources with custom and/or modified files and code.
Thanks,
Stuart