CC2650 - IcePick_C: Error connecting to the target: (Error -600 @ 0x0) A required dynamic library could not be located.

Morgan Fitzgibbon

Other Parts Discussed in Thread: CC2650, CC2650STK

After compiling the 'SimpleBLEBroadcaster' I am getting the following error;

Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
Cortex_M3_0: Failed Board Reset
IcePick_C: 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 5.1.641.0)

I have tried to select between Cortex M3 and IcePick_C but no joy?

over 10 years ago

0 JXS over 10 years ago

TI__Guru** 105180 points

Hello Morgan,

Can you post a screen shot of the installed CC26xx device support as described in the SW Developer's Guide (SWRU393)?
Also, which reference board are you connecting to? SmartRF06 + CC2650EM? There should be no options requiring a change if you are using this HW setup. If you did modify, please delete & re-import your project.

Best wishes

0 Morgan Fitzgibbon over 10 years ago in reply to JXS

Expert 1360 points

I am using the board 'Debugger DevPack' connected to the PC and this board is plugged into the CC2650 (SensorTag)

"Can you post a screen shot of the installed CC26xx device support as described in the SW Developer's Guide (SWRU393)?"

- I have that doc opened but cant find the instructions to do this in the doc?

0 Morgan Fitzgibbon over 10 years ago in reply to Morgan Fitzgibbon

Expert 1360 points

1. I open the file "/SimpleBLEBroadcasterStack/targetConfigs/CC2640F128.ccxml" and go to the advanced pane ...

2. Next I test the connection I am getting the following:

[Start: Texas Instruments XDS100v3 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\Lara\AppData\Local\TEXASI~1\CCS\
ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusbv3.dll'.

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-600' (0xfffffda8).
The title is 'SC_ERR_LIB_ANY_LOCATE'.

The explanation is:
A required dynamic library could not be located.
The library isn't on the search path.

[End: Texas Instruments XDS100v3 USB Debug Probe]

0 JXS over 10 years ago in reply to Morgan Fitzgibbon

TI__Guru** 105180 points

If you are using Devpack Debugger, then you need to select XDS110. If this option isn't available, please check for updates in CCS. The XDS100v3 will not work with the Devpack Debugger.

Best wishes

0 Morgan Fitzgibbon over 10 years ago in reply to JXS

Expert 1360 points

I have switched to XDS110 and have tested the connection got the following result:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\Lara\AppData\Local\TEXASI~1\CCS\
ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Feb 18 2015'.
The library build time was '23:56:50'.
The library package version is '5.1.641.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.
The cause may be one or more of: invalid firmware update, invalid
XDS110 serial number, or faulty USB connection. The firmware and
serial number may be updated using the xdsdfu utility found in
the .../ccs_base/common/uscif/xds110 directory of your
installation. View the ReadMe.txt file there for instructions.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Next I have run the xdsdfu utility as susggested here but I get the following error:

***************************************************

Examples:

xdsdfu -f firmware.bin -r

Writes firmware.bin firmware to the device, and then resets it.

xdsdfu -s 00001234 -r

Sets device serial number to "00001234", and then resets device.

ERROR: No file name was specified. The file name is required.

C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -f firmware.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2014 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

The requested device was not found on the bus.

C:\ti\ccsv6\ccs_base\common\uscif\xds110>

0 Martin Sunstrum over 10 years ago in reply to Morgan Fitzgibbon

Intellectual 340 points

I am getting the exact same issues as Morgan. Using the same hardware, just purchased this week.

Running Windows 8.1 x64

If I go back to the original XDS100v3 USB Debug Probe_0, I get the -151 error as seen by others.

=================================================================================

[Start: Texas Instruments XDS100v3 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\Martin\AppData\Local\TEXASI~1\CCS\
ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusbv3.dll'.

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during
the connect returned bad status or an error.
The cause may be one or more of: invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.

[End: Texas Instruments XDS100v3 USB Debug Probe_0]

0 Morgan Fitzgibbon over 10 years ago in reply to Martin Sunstrum

Expert 1360 points

I am using Windows7 Ultimate Service Pack 1

0 Martin Sunstrum over 10 years ago in reply to Martin Sunstrum

Intellectual 340 points

The error message indicates that the XDS100 EEPROM values may be blank.

Downloaded FTDI application to try to change them, but the application was not able to detect any corresponding USB device.

But if I open Windows Device Manager, I see the following:

The EEROM VID and PID values are as shown as below:

From other TI app notes, these values may not be right. But as I said, if I tried to change them, the FTDI app couldn't discover the FTDI device !?

NOT sure if this info will help TI or not.

Thx, Martin

0 Martin Sunstrum over 10 years ago in reply to Martin Sunstrum

Intellectual 340 points

Looks like bulletin board rejected my pictures ... show here it is in words.

Device Manager showed "Texas Instruments Debug Probes"
Under there, 2 devices
1) XDS110 Class Data Port
2) XDS110 Class Debug Port

Under Properties, "Device Instance Path" showed VID / PID = 0451 / BEF3

0 Martin Sunstrum over 10 years ago in reply to Martin Sunstrum

Intellectual 340 points

An item to note is as follows:

Under Window Device Manager, the XDS100 showed up under "Texas Instruments Debug Probes"
Other app notes seemed to indicate that they should show up under "Universal Serial Bus controllers"

Possibly that is a hint towards the problem ...

0 Morgan Fitzgibbon over 10 years ago in reply to Martin Sunstrum

Expert 1360 points

That is what I see as well ... i.e they are not under Universal Serial Bus Controllers

A colleague of mine has suggested to download the FTDI drivers at:
www.ftdichip.com/FTDrivers.htm

I have not tried that yet - is this a solution - if so what are the exact steps?

0 Morgan Fitzgibbon over 10 years ago in reply to Martin Sunstrum

Expert 1360 points

My previous post did not save?

I see in my Device Manager as well that the Texas Instrument Debug Probes are not under the 'Universal Serial Bus Controllers' either?

A colleague of mine has suggested downloading the FTDI drivers @ www.ftdichip.com/FTDrivers.htm

Would that help ? If so what are steps to install these drivers ?

Thanks

0 Morgan Fitzgibbon over 10 years ago in reply to Morgan Fitzgibbon

Expert 1360 points

Make sure that the DevPack board is mounted up correctly to the CC2650STK board ! This solved my issue (Unfortunately there are 2 ways that the boards can mate together 1) One on top of the other and 2) where 1 board sticks out the left and the other one to the right.... 1) is correct but 2 is not and I found that this caused a battery drain issue to .. In my experience boards should connect foolproof...then I check the connection again!

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\Lara\AppData\Local\TEXASI~1\CCS\
ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Feb 18 2015'.
The library build time was '23:56:50'.
The library package version is '5.1.641.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]

0 Martin Sunstrum over 10 years ago in reply to Morgan Fitzgibbon

Intellectual 340 points

Hi Morgan,

I also mounted them as you describe in 1), but still getting the issue.

With your new working setup, how does it show up in the Device Manager ? Under "Texas Instrument Debug Probes" are not under the 'Universal Serial Bus Controllers" ?

Thanks, Martin

0 Morgan Fitzgibbon over 10 years ago in reply to Martin Sunstrum

Expert 1360 points

Hi Martin,

If you mount the CC2650DevPack (XDS110 probe) on the tag as per the following pic @ www.ti.com/.../CC-DEVPACK-DEBUG

then I run the test connection it worked for me.(see the report above).The problem is that it is very easy for someone to connect it the other way and not realise the side effect of draining the battery as well.

Check Vbat+ and Vbat- to ensure that it is ~3V. If it is hooked up incorrectly then the voltage is about 1.3V! which points to a battery drain (load regulation issue)

Morgan

0 Martin Sunstrum over 10 years ago in reply to Morgan Fitzgibbon

Intellectual 340 points

Hi Morgan,

Yes, my DevPack is installed properly, and the cell battery is reading 2.9V, and with the DevPack plugged in. I can still run the Sensor Tag app, and see active sensor data.

Something else is going on here that is not super obvious ...

Quick questions:
1) With your new working setup, how does it show up in the Windows Device Manager ? Under "Texas Instrument Debug Probes" or under the 'Universal Serial Bus Controllers" ?

2) When you "Test Connection", is the test performed on XDS100v3 or just XDS100 ?

Thx, Martin

0 Martin Sunstrum over 10 years ago in reply to Martin Sunstrum

Intellectual 340 points

My typo ...

2) When you "Test Connection", is the test performed on XDS100v3 or just XDS110 ?

0 Morgan Fitzgibbon over 10 years ago in reply to Martin Sunstrum

Expert 1360 points

For 1) Under "Texas Instrument Debug Probes" which is separate from 'Universal Serial Bus Controllers'

For 2) performed on XDS110 not 100...Switch it to 110 .. I think that is a problem if you use 100.

0 Martin Sunstrum over 10 years ago in reply to Martin Sunstrum

Intellectual 340 points

Figured out my issue ...

Reinstalled CCS on Win7 machine, and all worked well.

Went back to my Win8.1 machine, and rebuilt my Eclipse project from scratch. Made sure XDS110 Debug Probe setup initially.
Worked great from there !

Under my Windows Device Manager, probes showed up under "Texas Instrument Debug Probes"
(NOT under the 'Universal Serial Bus Controllers" )

VID/PID was 0451 / BEF3, so not problem with FTDI EEROM values.

Thx all for help !

Martin

0 user3842826 over 10 years ago

Prodigy 20 points

In your screenshot, go to General -> Device -> Connection and select the XDS110 Debug Probe. Now check Debug settings again.

Worked for me.

Regards

Bluetooth®︎

Bluetooth forum

CC2650 - IcePick_C: Error connecting to the target: (Error -600 @ 0x0) A required dynamic library could not be located.