• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 538 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/LAUNCHXL-F28069M: Not supported in CCS8?

Bjorn Nyman
Prodigy 50 points

Part Number: LAUNCHXL-F28069M

Tool/software: Code Composer Studio

I installed CCS7.4 on my W10 machine, but I couldn't start it, was som registry error. So then I uninstalled and installed CCS8. But when there is no LAUNCHXL-F28069M supported it seems. If I start typing LAUNCHXL only one board shows up.

All I want to do is to start playing with instaspin, but it seems like absolutely nothing works for me. And I have been doing MCU development for a decade, starting with PIC, AVR, etc, using command line software under windows and linux. But this GUI stuff seems so advanced

  • 0
    TI__Guru**** 173310 points

    Bjorn Nyman said:
    But when there is no LAUNCHXL-F28069M supported it seems. If I start typing LAUNCHXL only one board shows up.

    Are you referring to the list that shows up when you start typing the Resource Explorer "Select a Device or Board" search box?

    If so, yes there are currently no launchpads/kits populated there for C2000, but you can still type in F28069M and it will filter and show content for that device. 
    CCSv8 itself does fully support that device.

    If the Resource Explorer is not what you are referring to, then please provide additional information. 

  • 0 in reply to AartiG
    TI__Guru**** 171839 points

    In addition to Aarti's response, check the page below that shows what device setting to use when configuring CCS to be used with the various development boards.

    dev.ti.com/.../

    Regards,
    Rafael

  • 0 in reply to desouza
    Prodigy 50 points

    The issue was a switch on the board, in the wrong position, creating errors when connecting with the debugger. I tried to manually create a debug config (like you suggested) yesterday. Since it/debugging didn't work, I thought the board had to be in that list in resource explorer. But after flipping the switch I can debug it!

    And was also able to spin a motor today as well!