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: TMS320C2000 Experimenter Kit support for CCS V5 or newer

Tool/software: Code Composer Studio

Does CCS V7 support the TMS320C2000 Experimenter kit with the F28069 Piccolo card? In the V7 resource list, this kit does not look to be included.

  • Robert,

    Yes this kit is supported by CCSv7. The Experimenter kit will have an XDS100 onboard (likely an XDS100v1). I have used this kit with CCSv7 before.

    When you say it is not in the resource list, do yo mean when creating a project or browsing in Resource Explorer or something else?

    Regards,
    John
  • Hi John,

    Thanks very much for the info. Yes, I was referring to the resource list, but after working my way up to CCSv6.2 successfully, I now know for certain that the kit is supported well beyond CCSv4, which is what the guide included with the kit specified.

    After getting CCSv6.2 working with the kit I think I may now have the insight and successful reference knowledge to get CCSv7 going. Being totally new to CCS and TI software tools in general, I suppose there are a few things I have to get familiar with, although I do have a lot of experience with Eclipse.

    Thanks

    Robert

  • Robert,

    If you are familiar with Eclipse then getting up to speed on CCSv7 should be pretty straight forward.  We do add our own build toolchain and plug-ins so there are differences.  We have some workshops to help with learning the environment.  They are accessible from within Resource Explorer. You can access Resource Explorer from the View menu and the shot below shows where the C2000 workshop is.

    Regards,

    John

  • Hi John,
    Thanks for the additional info.
    FYI: Right now I am stuck not being able to integrate SYS/BIOS into my CCSv7 IDE.
    My method was to download and install the compatible version of SYS/BIOS and then after starting CCSv7 I assumed it would discover the new install as long as SYS/BIOS was installed in the default folder ( C:\ti\bios_6_50_01_12 ). Unfortunately, this method hasn't worked for CCSv7 or for CCSv6 ( using the CCSv6 compatible version of SYS/BIOS and user guide ).
    How do I make this work?

    Thanks
    Robert G
  • Robert,

    If you go to Windows -> Preferences this will open the preferences dialog. In the tree on the left go to Code Composer Studio -> Products.
    Try clicking the Add button at the top right and specifying the c:\ti\bios_6_50_01_12 folder and then click the rediscover button. CCS should automatically find BIOS in that location unless the discovery at startup is disabled.

    Regards,
    John
  • Hi John,

    Thanks for the info. Yes this method worked correctly. BTW: Is this correct method ( and probably a host of other updated info ) shown in some updated user guide or other corrected documents I can download? I never saw the preferences method in anything I read, so I may be missing an important doc I can use moving forward regarding C2000 + SYS/BIOS.
    Also, can I use this same method for discovering the full TI-RTOS standalone folder for the C2000? If so, would I actually be able to download a simple test image to it to the C2000 Experimenter board and be able to run it? Or would there be some driver-level conflicts or other incompatible components that TI-RTOS C2000 would contain?

    Regards,
    Robert
  • Robert,

    CCS should really automatically discover those products if they are installed under C:\ti
    There is a handbook that has some more information on this sort of thing here:
    processors.wiki.ti.com/.../Projects_and_Build_Handbook_for_CCS
    But really in your case it should have just worked.

    You can use the same method for pointing to other versions of TI-RTOS. You can then have a project use that version and it should not conflict with other projects that use the other version. Basically you can have different projects use different versions of the software products. The handbook has some information on that as well.

    Regards,
    John