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.

License for debugger CCS6

Other Parts Discussed in Thread: CCSTUDIO, HALCOGEN

I'm using CCS6 with a development board (Hercules TMS570LS12x/11x Development Kit)

I've had it installed for a few months, and now when I try to debug I get a message about the license has expired. Is the free license limited to 90 days? I was under the impression that there was no time limit for development boards.

  • Sounds like you enabled the evaluation license, which is time limited. However, if you are using the onboard XDS100v2 of the Hercules TMS570LS12x/11x Development Kit, then you can use the free license, which is not time based (never expires). I believe you can still use CCS with it without issue. Let me know if you do have an issue.

    Thanks
    ki
  • How do I disable the evaluation license, and only use the free license?

    The popup to the right is what I see when I try to debug. Compiling works, and the device is flashed with the code. But just after the debugger stops at start of main, I see this popup.

  • I see. Can you try the steps documented below:
    processors.wiki.ti.com/.../FAQ_-_CCSv4

    Thanks
    ki
  • I followed the steps, but didn't work. I get the same results in both windows as in my previous picture.

    I even tried deleting licenselocation.txt and TI_CCS_Free_License.lic, as well as trying putting -DFORCE.REG at different locations in ccstudio.ini

    But none of my attempts changed the result.

    A new licenselocation.txt and TI_CCS_Free_License.lic is created at startup of CCS but I still get status "Unlicensed"

  • OK, since it wasn't working, I uninstalled CCS, deleted all the folders that I know of related to TI products (which also removed HalCoGen from my system). I then restarted the computer, installed CCS 6.1.3 again, created a new workspace, and a new empty project. But after compiling and starting the debug session it behaves the same... So I guess there are files unknown to me still on my system, which I didn't delete prior to reinstalling it.
  • Yes, I'm using the onboard XDS100v2.

    I haven't had an issue at all until this point, and now I don't know how to solve it.

    We are in the processes of choosing a toolchain for our work.

    How can I solve this?

  • There is no way to solve it?

  • Hello,
    Can you send me a private message? I will need some details about your environment.

    Thanks
    ki