• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 657 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.

CCS/CC2640R2F: CCSv10 compatibility with projects that depend on previous versions of XDCtools

rperezti
Genius 12670 points
Part Number: CC2640R2F

Tool/software: Code Composer Studio

I'm trying to use CCSv10 to build a project from simplelink_cc2640r2_sdk_4_10_00_10. The SDK release notes for that SDK state that it was built and tested with CCSv9.0 but I was hoping that CCSv10 would be backward compatible. Is this even likely to work or should I stop here and downgrade to CCSv9.0?

When I try to build in CCSv10 it fails with a non-descriptive error message, "Cannot build project. Referenced project 'glucose_sensor_cc2640r2lp_stack_library' contains build-errors."

One thing I noticed, and I suspect causes problems, is that while the project depends on XDCtools v3.50.1.12_core, CCSv10 reports this version is not available and automatically switches to XDCtools v3.61.0.16_core.

I have confirmed that XDCtools v3.50.1.12_core is installed at C:\TI but CCSv10 doesn't auto detect it. Is there a way to force CCSv10 to auto detect the earlier version of XDCtools?

Thanks

  • 0
    TI__Guru**** 162325 points

    Ruben,

    CCS should detect and allow you to use older versions of teh XDCTools. In fact if you download the SDK from Resource Explorer it should automatically download the appropriate XDCTools.

    I have run into an issue in v10.0 (fixed in 10.1) that you often have to click refresh in the product discovery settings to get it to find installed products.

    Can you check the settings below and make sure that C:\ti is setup as a location in the discovery path and then hit refresh and see if it adds it to the list in the bottom section:

    Note that the build error may not be related to xdctools.  The 4.10 SDK actually wants you to use the 18.12 compiler and not the 20.02 that ships with CCS.  If you click on the glucose_sensor_cc2640r2_stack_library in the project explorer it should show you the actual build errors for it in the problems view.

    I know that for some of the BLE5 examples in the SDK if I build them with the 20.02 compiler I get an error when building related to a runtime library change.  

    Regards,

    John

  • 0 in reply to JohnS
    TI__Genius 12670 points

    Updating the compiler version resolved the build issues. Thanks!