• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 7797 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 connecting to the target: (Error -600 @ 0x0) A required dynamic library could not be located?

Markel Robregado
Guru 86765 points
Other Parts Discussed in Thread: CC2650

Tool/software: Code Composer Studio

Hi,

   I am getting this error below when I try to do CCS->Debug. How do I resolve this problem?

Error connecting to the target:
(Error -600 @ 0x0)
A required dynamic library could not be located.
The library isn't on the search path.
(Emulation package 6.0.504.3)

I am using CCSV7, Windows 10. For Beta Testing requested by Ki-Soo Lee, I installed this patch "ti_emupack_setup_6.0.504.3_win_32". The patch is to resolve CCSV7 crashing issue.

- kel

  • 0
    Guru 86765 points

    Hi,

       I deleted my current CCS installation and installed a fresh copy of CCSV7 "ccs_setup_7.0.0.00043". I applied the fix for CCS crash by copying the DeviceIdentifier.dll fix to the "C:\ti\ccsv7\ccs_base\emulation\analysis\bin".

       I installed a new copy of ble stack to be able to get a fresh copy of hid_emu_kbd_cc2650em_app  and hid_emu_kbd_cc2650em_stack.  I was able to build both projects with ARM Compiler Version 5.2.8. I encountered the same error after doing CCS->Debug. See, screenshot below.

    A Windows 10 update happened recently. Using SmartRF Flash Programmer 2, I programmed both hex files to CC2650 Launchpad. I was able to pair the HID Keyboard, but the functionality does not work. Before, it works without problems. 

    - kel

  • 0 in reply to Markel Robregado
    Guru 86765 points
    Hi,

    Any help regarding this? I am not able to do my work because of this issue. The CCS project that I have been using without problems a couple of weeks ago, now is having this problem.

    - kel
  • 0 in reply to Markel Robregado
    Guru 86765 points

    Hi,

        I found the problem. Some activity in Windows change the CCS Connection to XDS100v3 USB Debug Probe. If I select the default which is XDS110 USB Debug Probe, I am able to do CCS->Debug. This problem is not isolated to my Home PC. Because I got the same error at my work PC.

    - kel

  • 0 in reply to Markel Robregado
    TI__Guru**** 173310 points

    Markel,

    Thank you for reporting back your findings.

    Markel Robregado said:
    Some activity in Windows change the CCS Connection to XDS100v3 USB Debug Probe. If I select the default which is XDS110 USB Debug Probe, I am able to do CCS->Debug.

    Did you re-import those projects after reinstalling CCS and SDK? The default Connection type for cc2650em projects is set to XDS100v3 debug probe. Perhaps you changed it to XDS110 when you were previously working with it, but then if you reimported the example project again from the SDK directory then it would default back to XDS100v3. Could that be what happened?

  • 0 in reply to AartiG
    Guru 86765 points
    Hi AartiG,

    The first time I tested the CCS Projects hid_emu_kbd_cc2650em_app and hid_emu_kbd_cc2650em_stack, at Home Laptop PC, I just import it to CCS and change the predefine symbol to work for CC2650 Launchpad. For these CCS projects I did not change the connection settings. I did the same at CCS at my work PC, because I am going to use these CCS projects as base for software development.

    When I made this post I first encountered this problem at CCS at my Home Laptop PC. That was Sunday, January 29, 2017. Then I came to work yesterday at 8:00 AM. I was expecting no problem with CCS because last week, I demo hid_emu_kbd_cc2650em_app to my team. But, when I try CCS->Debug, I encountered the same error.

    Anyway, I will just learn from this experience. After importing CCS projects, I will check the connection settings.

    - kel