INSTASPINUNIVERSALGUI: Error: C28xx: Error: (Error -150 @ 0x0) One of the FTDI Driver functions used during ... Emulation Package 5.1.641.0

1. Use a instaSPIN lab project to verify whether your emulator work well, connect with the EVM properly.
2. Follow GUI guide to configure the connection and load correct program.

Hello,

thank you for your quicke response.
1. I use the InstaSpin lab project 5b all the time.
2. Can you give a more detailed hint ?

I followed the wiki guide:
processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

after adding a new target configuration file i got the following output:


[Start: Texas Instruments XDS100v2 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\ms3323\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 'jioserdesusb.dll'.
The library build date was 'Dec 9 2016'.
The library build time was '13:48:53'.
The library package version is '6.0.504.1'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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 FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 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).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

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

This test will use blocks of 64 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 64 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 XDS100v2 USB Debug Probe_0]

Thank you very much,
Stefan

Problem still exists.

I also tried the following Troubleshooting instructions: processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems
with the result that all tests are passed, but i still get the error message

(i used the graphical Version of dbgjtag and so it was not very complicated but you have to know some links .. quite hard to get started without:
1. where to get it: processors.wiki.ti.com/.../DBGJTAG_Graphical_User_Interface
2. the instructions: processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems
3. you have to know that the by right-clicking on the .ccxml file in the project explore a tab Pops up where you can find the "test Connection" button

Now I ve also updated the emulation package. There is still the same problem.
... one of the ftdi Driver functions used during ... (Emulation package 6.0.579.0)

1. Use CCS to verify the emulator connection. Can you connect the emulator and load lab05b in CCS without GUI composer? If no, check emulator, board power, switch setting on kit. Which EVM kit and controller are you using?
2. Load the program code to controller first, set the correct switch for code run in flash.
3. What information is reported in Configuration of InstaSPIN GUI? Did you set right emulator for GUI configuration?
4. Run the GUI in CCS as GUI Quick Start Guide if standalone GUI can't work well again.

Hi Yanming,
answers:
1) YES, it s possible to debug it (because i m quite new to CCS i don´t know how to run it without Debugging mode, but debugging is possible). it appears erasing Flash sectors and loading program ... in CCS and i can set a breakpoint to line 149 in proj_lab05b.c (main Routine)

I use CCSv7.0.0 and the drv8301 revB together with C2000 launchxl-f28027F on top

2) can you give me some advice on this. i can not find the "Flash dowload" button in CCS like i m used to press in eclipse.
do i Need to install it via app Center first ? (the Project file already existed in the solution Folder and i only imported it into CCS)

3) i tried to use v1 but neither that nor XDS100v2 works.
i think he uses that config file
C:\ti\guicomposer\eclipse\workspace\.metadata\.plugins\com.ti.binding.program
Content:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="configuration_0">
<instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
<connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe">
<instance XML_version="1.2" href="drivers/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
<platform XML_version="1.2" id="platform_0">
<instance XML_version="1.2" desc="TMS320F28027" href="devices/f28027.xml" id="TMS320F28027" xml="f28027.xml" xmlpath="devices"/>
</platform>
</connection>
</configuration>
</configurations>

4) i have installed gui Composer via app Center in CCS and can get there by clicking view->gui Composer in CCS but there is None available application and i can not find the eclipse/dropins-gc Folder in the ti Folder. the only Folder that exists is eclipse/dropins

It seems the hardware is ok. You can follow the instaspin_labs.pdf and qsg_gui_universal.pdf in \docs\guis\universal, and then look which step will have problem.

Hi Yanming,

I ve tried to run lab02c in debug mode and get the same error (console output).
What CCS Version do you use ?

Hi Yanming,

now i have no error message so far. I think the reason was Jumper 2 on c2000 launchxl eval kit.

(it must be removed).

Best regards,

Stefan