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/CC1310: CCS10 - SDK Installation issues

Part Number: CC1310
Other Parts Discussed in Thread: CC1312R, CC1352R,

Tool/software: Code Composer Studio

I recently upgraded to CCS10 and in preparation for starting a few new projects, I wanted to get the latest SDKs appropriate to my targets (CC1310, CC1312R, CC1352R). I downloaded the CC13x0 SDK version 4.10.0.10 and the CC13x2 SDK version 4.10.0.78 from the TI web site and ran their installers (on MacOS). I went to CCS10 and it was able to find them both just fine, as shown here in this screen shot from Preferences/Code Composer Studio/Products:

You can clearly see 13x0 and 13x2 version 4.10... SDKs are recognized and installed (along with a bunch of legacy stuff from earlier projects). So far, so good. Everything I installed is right where I put it and CCS10 sees everything. 

PROBLEM 1: When I browse using Resource Explorer, getting ready to start a few projects off some example code (that method is recommended and sure is a nice way to get a base configuration going), I see the 4.10.00.78 SDK for the 13x2 family (good), but the version 4.10.00.10 SDK for CC1310 DOES NOT APPEAR. Interestingly, an older one (3.20.0.23) does, which did NOT show up in the Installed Products list above.

That's problem 1 - the 4.10.00.10 SDK for CC1310 is not showing in Resource Explorer. The fact that other stuff appears that doesn't show in the Installed Products page is interesting and unexpected and probably also wrong, but not of present concern to me.

I note with interest that the same SDK that's missing for CC1310, version 4.10.00.10 does appear under "CC2640R2". I don't recall installing anything for CC2640R2, but maybe this is the missing SDK for CC1310, under an entirely unrelated device heading? I go digging a bit and find in the Release Notes for CC2640R2 SDK 4.10.00.10 from Resource Explorer, it says "This is a GA release of the Core SDK 4.20.03.02 for the CC26xx and CC13xx devices" -- is this the 1310 SDK I'm looking for, just not named 1310 in the Resource Explorer (which also says it's not installed locally, even though it is)? And if it's for CC13xx, does it also cover the CC13x2 family (if so, why is there a separate SDK for CC13x2?)

PROBLEM 2: When I click the Product Details button on the Installed Products listing for SDK 4.10.00.10, it shows a missing dependency, xdctools 3.51.3.28. But if you look back at the Installed Products screenshot, you can see xdctools 3.51.3.28 is there (second from the top), though it does not appear in the Resource Explorer (neither do most of the other xdctools versions). The Package Info for CC2640R2 SDK 4.10.00.10 in RE also says xdctools 3.51.03.28 is missing.

Perhaps the cross-naming of things has confused CCS10 and it can't resolve the dependencies even though all the parts are there?

Just in case I was wrong about the CC2640R2  SDK 4.10.00.10 being the one for the CC1310, I poked around a bit and discovered the Resource Explorer has a version display filter for each line item. Maybe my version 4.10.00.10 specifically naming the CC1310 was filtered out? Nope. Version 4.10.00.10 is nowhere to be found under the CC13x0 SDK heading.

Interesting thing I discovered along the way: the Product Details for the CC13x2 SDK 4.10.00.78 (which otherwise appears intact) shows "xdctools 3.61.0.16 [not installed]" even though Resource Explorer and Installed Products both show it and "package info" from Resource Explorer shows it as a dependency that's met.

There are a few issues here. 

1. The 4.10.00.10 SDK I installed shows up as a CC1310 SDK under Installed Products but not under Resource Explorer. RE does show the same SDK version for CC2640R2 which internally names the CC1310 in its Release Notes, so maybe this is the one I want, despite the name change between RE and Installed Products?

2. The 4.10.00.10 SDK (CC2640R2 and possibly CC1310) shows its XDCTools (3.51.03.28) and its base package not installed when interrogated in RE, even though Installed Products shows both are present in its manifest. Product Details under Installed Products also says XDC 3.51.03.28 is a missing dependency for SDK 4.10.00.10 (though just a few lines down it shows XDC 3.51.03.28 is there). Is there anything to be done about this, or should I just proceed and hope that the sample projects can find the components they need?

3. The 4.10.00.78 SDK (CC13x2, CC26x2) shows its XDCTools (3.61.00.16) is present but its compiler (arm gnu 9.2.1) is missing when interrogated in RE. Under Installed Products, both the XDCTools and the compiler are shown as [not installed]. XDCTools 3.61.0.16 is listed in the Installed Products manifest. Under Preferences/Code Composer Studio/Build/Compilers, I find TI v20.2.0 LTS and GNU 7.2.1. Furthermore, under CCS/About/Installation Details/ARM GCC Compiler Tools, indeed I find 9.2.1.2019-q4-major (presumably meeting the missing "arm gnu 9.2.1" requirement). 

What should I do about all this? I'm not getting a coherent view of what's installed and which dependencies are met as I move around the environment. I'm about to start a multi-product, multi-platform (CC1310, CC1312R, CC1352R) project and want to be sure I have the latest stuff and that everything is complete and stable before I begin. 

  • Daniel,

    Problem #1

    It looks like that latest cc13x0 SDK posted to Resource Explorer is 3.20.  So even though you have 4.10 installed Resource Explorer does not recognize it.  I checked and the 4.10 SDK has now been handed off to Resource Explorer and should show up by tomorrow.  I will have to follow up with the SDK team on why there is such a lag between the SDK showing up on ti.com and Resource Explorer.

    Problem #2

    Not sure what is going with the XDCTools 3.51.03.28 install.  CCS knows it is there but Resource Explorer does not.  Probably some sycn issue.  I will try to reproduce that on my side and work with the development team to resolve.  Given that CCS is aware of this verison it will use it during the build.  The projects for the SDK typically specify the XDCTools verison to use and then CCS will use that verison.  

    One other thing to note.  You probably want to install the 18.12.x compiler for ARM.  You can do this from the help menu "Install Code Generation Compiler Tools".  The 4.10 SDK is validated with that compiler and not the 20.2.x one.  I have seen some issues using the newer compiler.  In the future the SDK will hopefully specify the compiler as a dependency and have Resource Explorer automatically install it like it did for GCC 9.

    Regards,

    John

  • 1 - Okay. I can certainly wait a day for that to be resolved. 

    2 - Sounds like I don't need to worry much - projects should ask for what they want and it seems like I can expect them to find the XDC version if it's actually there, which it is.

    3 - Compiler 18.12.x - good to know! I have installed that compiler per your instructions and will be sure to specify it in my project files.

    My plan now is to do some background work until #1 is resolved and then I expect to be able to proceed to begin my project family all together after that. I really want to work on all three targets ore or less in parallel, especially as I get things started, to be sure I have a solid footing on each platform I can hand off as a baseline to other developers. Thanks for your help and prompt response.

  • One other note.  In CCSv10 I find I have to do a refresh after installing a compiler to ensure it is discovered.  That will be fixed in 10.1 which I believe will be out next week.  For now after installing I always go here and click refresh:

    I am installing the 4.10 SDK on my mac now and hopefully can reproduce what you are seeing with the XDCTools version.

    Regards,

    John

  • I am able to reproduce the issue with XDCTools.  I have filed a bug to track it. https://sir.ext.ti.com/jira/browse/EXT_EP-9859

    It does not seem to cause any problems.  The CCS build system has found the correct version of XDCTools and uses it.

    Thus it appears to be more of a cosmetic issue.

    Regards,

    John

  • John,

        Glad to know that, thank you. 

        At this point, the only thing that remains is Resource Explorer understanding the 4.10 SDK, which you said might be a day before it was completed.

    DBS

  • Daniel,

    THe 4.10 SDK is on Resource Explorer now.

    Regards,

    john

  • Confirmed!

    Thanks for getting this taken care-of. Looks like there was a version bump, too, from 4.10.0 to 4.10.01.

    I think I'm all set to get started on my various projects now.