• Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 2162 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.

XDS100V2 error

Marada Naveen Kumar
Intellectual 615 points

Other Parts Discussed in Thread: CCSTUDIO

Hi.

     I've build a xds100v2 emulator based on the design details given by TI.when i try to use it through ccsv5 i got this error.

'error connecting to target:

(Error - 215@ 0x0)

The semaphore for the test bus controller is in a time-out state.Unified-SCIF was unable to acquire the semaphore used to express ownership of a controller by a utility or debugger.you may have to exit other clients because the time-out occured.

(Emulation Package 5.0.569.0)'

what does this mean? Please help.

Regards.

  • TI__Guru**** 480841 points

    Hello,

    Please use the 'Test Connection' option in CCSv5 (see url below) and post your results here:

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems#Code_Composer_Studio_v5

    Thanks

    ki

  • in reply to Ki
    Intellectual 615 points

    Hi Ki.

             I've used that option and when I'm trying to load the code Ive got this error.

    Regards,

    Naveen.

  • in reply to Marada Naveen Kumar
    TI__Guru**** 480841 points

    Looks like your attachment did not get posted properly. Could you re-post the error?

    Thanks

    ki

  • in reply to Ki
    TI__Guru**** 480841 points

    ignore my last post, i see that you meant that you got the same error as in your first post.

  • TI__Guru**** 171729 points

    Hi,

    This issue may be caused by a CCS crash or some software misconfiguration, therefore can you check a few details?

    - Make sure there are no previous instances of CCS running in your PC (even if CCS crashed before), as this may potentially cause this issue. If you open the Task Manager and still see more than one <ccstudio.exe> process, this may be interfering in the communications.

    - Do you have more than one XDS100 connected to the PC (even embedded in development kits)? This could confuse CCS (I suggest you take a look at the Device manager just to be sure).

    - Were you successful in properly programming the FTDI device? To verify, please run the xds100serial.exe utility and see what it reports back (you can copy it to this thread as well).  Check question 6.1.9 of the XDS100 page.

    - Did you change any of the emulator parameters in the .ccxml file you are using? If so, I suggest try to create one from scratch and retry.

    The techincal details that were sent ot us are reproduced below.

    Hope this helps,

    Rafael

    The scan manager uses a software semaphore to ensure that only one client is using the XDS100 at a time.

    The name of the semaphore is based on the driver name and a port identifier.  I don’t see anything there that would depend on their hardware implementation.  Most likely, there’s been a crash or abnormal exit from CCS, and the semaphore previously created is still hanging around.  A reboot of the PC may clear this up.  If it repeats, then we’d need more tests run to try to pin down the issue.  A look at the .ccxml may help, maybe not.  The results from the xds100serial.exe program may show something.