Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.333.0)

Hi Luis,

Luis Garcia said:

""Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.333.0)""

Did you verify that the VID/PID for the EEPROM is still programmed correctly?

http://processors.wiki.ti.com/index.php/XDS100#Q:_I_got_an_.22Error_connecting_to_the_target:_Error_0x80000240.2F-151_Fatal_Error_during:_Initialization.2C_OCS.22_when_trying_to_connect_to_the_target_in_Code_Composer_Studio_v4

Also, what is the full version number of the CCS version you are using?

Thanks

ki

Hello, 

I also have been using CCS 4 with the Picollo and a hardware of my own.  My debugger is the XDS100v2 and everything has been working well until this morning. I have downloaded the last version of the Code Composer, the new version is 4.2.3.00004. Since that moment each time I make a change in my application software I have to exit from the Code Composer, shut down the PC and start all from the beginning. If I don't do this procedure and I try to launch directly the debugger I only get the message:

"Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.333.0)"

I have no changes from the hardware neither from the application software, the only change has been the update of the Code Composer. Also I have checked the VID/PID of the XDS driver, removing and installing again the drivers, etc., but I can't operate as before

If anyone out there has an idea of what can i do,  I'd appreciate it.

Thanks in advance

Hello again,

I have found a new way to enter successfully to the debugger session: exit from CCS, power off the target hardware, disconnect the USB connector of the debugger, connect the USB connector, power on the target hardware, enter to the CCS and launch the debugger. In this way I have no need to shut down the PC.

Regards,

Miguel said:

I have found a new way to enter successfully to the debugger session: exit from CCS, power off the target hardware, disconnect the USB connector of the debugger, connect the USB connector, power on the target hardware, enter to the CCS and launch the debugger. In this way I have no need to shut down the PC.

Miguel - you have to do this every time??

I am having the same problem, but under CCS v5.1.0.040001.   Like Miguel, the issue arose for shortly after upgrading (though obviously to a different version, since he is running CCSv4).

The error I get is:

IcePick_C_0: Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.353.0)

Miguel's method does not work for me.

I have also tried a colleague's USB100v2 d, and it fails with the same error (this makes me think it isn't an EEPROM issue).

I am reinstalling CCSv5 to see if that clears it up.

I have reinstalled CCSv5, which didn't help, downgraded to CCS v5.1.0.03, which didn't help, and checked the EEPROM to be sure (it's VID 0403 and PID A6D0, which should be correct).

When I plug in the device I get the message that the drivers didn't install correctly.  When I ask to search for drivers to fix the problem, no drivers are found.  I've also tried installing by pointing the driver installation wizard to the "Blackhawk" folder on my hard drive.  Also no luck.  I've been looking over the XDS100 wiki page, and it simply suggests checking the EEPROM.

Any other ideas?

Thanks,

Rob

Just attempting to 'upgrade driver' from the Device Manager, and searching all of the C:\Windows directory, I got the following error:

"Windows found driver software for your device but encountered an error while attempting to install it.

TI XDS100 Channel A

The system cannot find the file specified"

I had the same problem and i solved from the Device Manager searching the driver manually  in the path that the ccs is installed in my case "C:\Program Files\ Texas Instruments"

Luis,

Thank you.  I had just gotten Channel A to install by searching all of C:\, which took 10+ minutes.  Installing Channel B with your advice made it much much faster.

It works again!

Hi,

I have no option to upgrade the driver: if I allow windows to search the driver the answer is there is not any driver better than installed. If I tried to tell windows the location of the driver as 'c:\ProgramFiles\TexasInstruments', windows reply that there is no driver in this location.

And with regard to the way to get into the debugger I have to be following the same way than before explained:

1. Exit from CCS,

2. Power off the target hardware,

3. Disconnect the USB connector of the debugger,

4. Connect the USB connector,

5. Power on the target hardware,

6. Enter to the CCS and launch the debugger.

Moreover, if I try to exec the point 6 before the 4, in order to make the process shorter, and while the PC is loading the ccs I make the points 4 and 5, I get error again when I try to launch the debugger.

Regards,

Hi,

I go on working with the same problem, even though I have upgraded to the latest version available yesterday. It seems as it would be needed to init the driver (steps 1 to 4) before enter to the ccs.

I'm asking myself if there is anyone in TI who can help me to solve this problem or even to send me some kind of information about what is the meaning of this error.

Maybe it would be helpful to get a list explaining the meaning of each error. I suppose this kind of list must exist, but I have no success searching it among all the documents available in the web and the wiki.

Regards,

Yes, there is a list with errors:

http://infocenter.arm.com/help/topic/com.arm.doc.dui0436a/RVCT20_Errors_and_Warnings.pdf

Turns out the answer was to uninstall the drivers for A and B in device manager, re-scan for a hardware change then let windows xp automatically re-install the drivers. 

Then do the classic power cycle

XDS100v1 working again.

Thank you!! that fixed the problem for me.

Need detailed connection diagram of TMDXDOCK28377D kit.kindly help

Need detailed connection diagram of TMDXDOCK28377D kit.kindly help