• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 12394 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: Error -716: Required dynamic library jscserdes could not be located.

Anthony Bristow1
Prodigy 55 points
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hello,

I just downloaded Code Composer Studio to get acquainted with the software I tried building and debugging multiple different example project for the C2000Ware and kept getting this error:

Error connecting to the target:
(Error -716 @ 0x0)
Required dynamic library jscserdes could not be located.
The library isn't on the search path.
(Emulation package 9.1.0.00001)

I already attempted to try and find a solution to this problem on this link: http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html.

Unfortunately under my .ccxml file after I changed the value of XDS from 100 to 110 I still got the same error. 

Specifically: 

Required dynamic library jscserdes not found

This error is caused when the target configuration file (.ccxml) is configured to use the XDS100 Debug Probe but the target board uses a XDS110 Debug Probe. The root cause is that, since these two debug probes have a great deal of common configuration files, the emulation software mistakenly assumes the correct probe is loaded but the file is missing.

To correct this error, simply change the target configuration file from XDS100 to XDS110. This is very common in the F280049C Launchpad boards and a misconfigured example code.

Error connecting to the target:
   (Error -716 @ 0x0)
   Required dynamic library jscserdes could not be located.
   The library isn't on the search path.
  • 0
    TI__Guru**** 170554 points

    Hi,

    Thanks for sending a detailed post. 

    Unfortunately this is one of the most elusive errors recently found. The reference was confirmed by myself and other two developers when the project was imported directly from the C2000Ware and the Debug Probe misconfiguration was triggering the problem. 

    https://e2e.ti.com/support/microcontrollers/c2000/f/171/p/825168/3054686#3054686 

    Despite this, others still found the same issue but the root cause was not the same.

    In these cases, we also suspect that a faulty install could also cause the problem. Check the first posts of the thread above for details on which files should be present in your filesystem.

    A few other developers reported this issue but the threads went inconclusive - they never responded. 

    I will keep investigating to see if there is anything else that I can do to try and pinpoint the root cause for this issue. 

    Hope this helps,

    Rafael