• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 1228 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: TIREX C2000Ware directory structure & documentation

TobyM
Genius 5200 points
Other Parts Discussed in Thread: CONTROLSUITE, C2000WARE

Tool/software: Code Composer Studio

Hi folks

Im starting a new CCS project and thought it an opportunity to move from ControlSUITE device support to TIREX C2000ware.

Sadly, although SPRUI45 mentions an improved directory layout it seems a lot of the device support for most devices currently covered has simply been wholesale copied into single places with little regard for this. You can see this by comparing the number of devices covered in device support with the number of devices covered in the driverlib directory, obviously the directory listings should match (assuming all devices have driverlibs), but obviously that is nothing like the case. A specific example is the F2802x driverlib.lib is buried under the device support directory (the location of which the driver library user guide fails to mention BTW) rather than the driverlib directory as the documentation suggests it should be.

The project structure obviously has been updated though as now driverlib libraries are moved from lib directories to Debug output directories... is it intentional that we as users should reference debug output? Should there be release output somewhere (or is this simply down to default naming)?

As it stands ControlSUITE device support is actually much easier to use. Is there any plan to ensure such things (either documentation or structure) are corrected?

Thanks, Toby

  • 0
    TI__Mastermind 30255 points
    Toby

    Thanks for starting to migrate to C2000Ware! As this is still very new, we appreciate all feedback and please continue to let us know your thoughts on what you discover!

    We intentionally kept device support very similar to that in controlSUITE to avoid overwhelming headache when coming from controlSUITE. It is true that F2802x is a unique case in which it is one of our older devices that has a driverlib. We chose to keep this directory as close to it was in controlSUITE for those users already familiar with F2802x directory and hence left the library there. The root driverlib directory is reserved for our new standardized driver libraries that is available on F2837xD and newer devices. I've made a note to see if we can clarify this in the package documentation.

    Yes, it is intentionally that the libraries are under "debug". For our newer driver libraries, debug builds enable our additional ASSERTS that help with API usage. Anyone getting started should begin with "debug" and then can later build a "release" version when ready.

    Please elaborate on how we can make the migration or package easier. I understand C2000Ware is newer, but you'll find it is a lot more straightforward and organized than controlSUITE is.

    Best regards
    Chris
  • 0 in reply to Christopher Chiarella
    Genius 5200 points
    Chris,

    Thanks for the info! I understand that you would like to reduce the headache moving from ControlSUITE. This seems like a reasonable a target. However, it means that people using such "older" devices do not see the benefit you mention by "you'll find it is a lot more straightforward and organized than controlSUITE is" because it is essentially organized the same.

    This means that for people working with these devices (which TI still sells and supports whether old or otherwise); A) there is no benefit (except maybe bug fixes in newer iterations of the device support), and B) there is still headache as I guess the main frustration I found was due to the difference between documentation and the reality.

    So; added headache (whether small or otherwise) for no benefit... hopefully the documentation will be fixed else it doesn't seem like much of an incentive to switch TBH.

    BR, Toby
  • 0 in reply to TobyM
    TI__Mastermind 30255 points
    Toby

    I totally understand. The "perks" of the new package are definitely more for newer devices. I wouldn't say no benefit. Package to package C2000Ware has many improvements over controlSUITE, if nothing else the download size :)

    As mentioned, we'll work on improving the documentation especially in regards to the older devices. Let us know if you see other discrepancies.

    Regardless, if you want the latest bug fixes, they will be only present in C2000Ware. We will continue to keep controlSUITE available though while we build up the infrastructure and packages planned around C2000Ware.

    Best regards
    Chris