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/CC1352P: Trouble using advanced features

Part Number: CC1352P
Other Parts Discussed in Thread: SYSCONFIG, ENERGYTRACE

Tool/software: Code Composer Studio

I'm getting incredibly frustrated with your software.  Nothing "just works".  I spent at least 10 hours trying to get the RTOS analyzer working, having to find and change so many buried settings that it will take me another 10 hours to do it on my next program.  I've been using Code Composer Studio for over 5 years, but now that I'm trying to use advanced features, I'm finding it incredibly confusing.  I look for documentation, but then little of it applies to syscfg, or it refers to some setting in CCS that I can't find. When the RTOS analyzer tells me it needs certain settings in my cfg file, it doesn't lead me there.  It doesn't give me the code, it really barely helps at all.  Then I google and find a doc and start editing, only to find out there's a GUI editor if I will just right click and select an acronym that bears no specific meaning to me.  Then one of the documents tells me to create a cfg file if I don't have one, so I do.  This new cfg file doesn't give me the option to turn on the settings I need, giving me a cryptic error.  This screws everything up because now it no longer looks at the inherited cfg file, and I can't change it back no matter what I do (other than deleting the project and re-importing my starting point from the resource explorer).  The example I give with the RTOS explorer is my most recent frustration, but it's not my only one.  Figuring out how to do 4-wire JTAG was insanely difficult.  How deep could you possibly bury it?  You brag in your marketing about your advanced power analysis, then the setting I have to change to use it is somewhere deep inside some random menu that I'd never find it without help.  WHY? 

When I started on this project, a different brand of chip was recommended to me, but I went with TI because i have a history with MSP430 chips.  So far, there is almost zero carry-over, and instead I feel like there's got to be a document or a tutorial or something that I've missed, because everything I try to do, I hit a wall.

I know this forum is for support and I'm not really asking for any, but can you please consider making CCS easier to use?  When you have advanced features like the RTOS analyzer, can you make it something that works without my having to conjure 20 lines of code from a pdf I found with google?  Can you combine the cfg file and the syscfg?  Why are there properties menus and board configuration menus and project menus that all seem to overlap, and the settings in them seem to be arbitrarily assigned?  

Again, I understand this is a support forum, so if you want to forward this on as feedback then delete it, I understand.  I would just really like to see this get less punishing to use.  Thanks.

  • Keith,

    You are absolutely right that things are fragmented today. The RTOS configuration and the software configuration necessary to enable RTOS Analyzer really all should be part of SysConfig. That is certainly the vision and hopefully we can continue to grow in that direction.  I will pass on this feedback.  Maybe a SimpleLink Academy lab would be useful short term.

    As far as changing from 2 wire to 4 wire cJTAG (or even JTAG) that is pretty buried today.  This is something we should cover in the CCS Users Guide.  We should add something to the Debug chapter that clearly states that if you want to change JTAG mode, TCLK... that you need to open your target configuration (.ccxml) file and how to do it.  The guide will have to be a bit abstracted as some things are device specific.  However we need to ensure that if you search the guide for specific terms that the appropriate section is found.  I will take an action for us to improve that.

    Regarding power analysis are you referring to EnergyTrace or something else?  I want to make sure that I direct that to the correct people.

    Please don't shy away from providing feedback like this.  We do read it and can hopefully improve as a result.

    Regards,

    John

  • Thank you so much for your response.  I truly appreciate it.  

    Yes, I was referring to EnergyTrace--that's why I was enabling 4-wire JTAG.  If you're updating documentation about that, you could have saved me from a major "duh!" moment: It didn't occur to me to check the launchpad board to see if all 4 JTAG wires were jumpered.  They weren't!  I felt dumb for missing that one, but still a suggestion for documentation.  Thanks!

    Thank you for your support--I am glad I have this forum to lean on when I get truly stuck.  

  • Keith,

    I was looking into creating a short training module for EnergyTrace on cc1352 and came across this:

    http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_40_00_02/docs/zigbee/html/energy-trace/energy-trace.html

    It is actually pretty good.  Just need to make it more visible.  It does not cover checking the jumpers though.

    Regards,

    John

  • Thanks!  I wish I had found this when I was looking before.  It's a nice level of detail, with screenshots and such.