• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1109 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/CC1310: Debugger Initialization Error

Saycoda
Expert 1580 points
Part Number: CC1310

Tool/software: Code Composer Studio

Hi all,

I have always in the past been able to debug two targets simultaneously, up until I had a PC crash. Now when I'm using CCSv8 if I have two instances running and try and initiate a debug session, I get the attached error message. I've run "fsclean" to no avail. Can someone please help me get this capability back? I normally start a debug session by clicking the bug in the toolbar.

Thanks in advance .

  • 0
    TI__Guru**** 171044 points
    Hi,

    You did not mention, but the message has specific instructions to fix the error. Did you follow its instructions? If so and the issue is still happening, there is a chance your install of CCS got corrupt.

    One detail: although you can run multiple instances of CCS, the emulation device drivers are not tested to be called by multiple debuggers (not reentrant).

    In this case, if you are debugging two targets simultaneously you should instead create a target configuration with multiple Debug Probes and call it from a single CCS instance. That is the safer approach.

    Details about how to configure CCS to accomplish this, check the section "Multiple Debug Probes" on the Custom Target Configurations page below:
    dev.ti.com/.../node

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Expert 1580 points
    Hi Rafael,

    When I use two instances, the target configurations are customized per probe (previous TI documentation). As far as specific instruction, are you referring to "if this continues, please run fsclean...........". Well I did run fsclean at the path indicated. Are there additional instructions that I'm unaware of?

    Thanks
  • 0
    Guru 92251 points

    Saycoda said:
    Now when I'm using CCSv8 if I have two instances running and try and initiate a debug session, I get the attached error message.

    I think each instance of CCS running creates a SQL database file to cache all devices, where each instance will save its cache in directories of the form:

    C:\Users\<user_name>\Local Settings\Texas Instruments\CCS\ccsv8\0\0
    C:\Users\<user_name>\Local Settings\Texas Instruments\CCS\ccsv8\0\1
    ...

    Where the above directories have files named targetdb.dat, targetdb.dat.valid and others.

    If you delete the above cache directories, CCS should be able to re-create them. I am not sure what exactly fsclean deletes, but have deleted the cache directories when have similar errors.

  • 0 in reply to Chester Gillon
    Expert 1580 points
    C:\Users\<user name>\AppData\Local\Texas Instruments\CCS\ti\0\0 as an example
  • 0 in reply to Saycoda
    Guru 92251 points

    Saycoda said:
    C:\Users\<user name>\AppData\Local\Texas Instruments\CCS\ti\0\0 as an example

    OK, the CCS installation directory name forms part of the pathname for target database cache directory, which is why your examples are different to my PC.

    Do you have both a C:\Users\<user name>\AppData\Local\Texas Instruments\CCS\ti\0\0 and C:\Users\<user name>\AppData\Local\Texas Instruments\CCS\ti\0\1 directory?

    If so, does deleting both directories, when CCS is not running, then allow you to start debug sessions when you have two instances of CCS running?

  • 0 in reply to Chester Gillon
    Expert 1580 points

    Deleting those folders resolved my issue. Thanks