RE: Error connecting to microcontroller when i launch a debug session

Hello Umesh,

Thank you for getting your feedback through.
I am reading your post and I think it would best to seperate this from the previous post that you posted here: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/109522/715187.aspx#715187

Can you help us with re-creating your problem?
First, what is the version of the High Voltage Kit you are using? If you are unsure, please take a picture of the base-board and the control card (both of them) so we can verify.
Second, which emulator are you using? Is this the on-board emulator or using an external one?
Lastly, What version of Code Compsoer Studio are you using?

If you can answer these questions, this should help us get started on finding out the cause of the error.

Has this been solved? I'm having the exact same error with a brand new C2000 LaunchPad plugged into my Windows 7 64bit computer's USB 2.0 port. Brand new install of CCSv5 with updates. For the target configuration I chose "XDS100v2" and then the "TMS320F28027." The entirety of the error message when I go to debug the "GPIO Toggle" program (no changes have been made to the program) is:

Error connecting to the target:
(Error -1135 @ 0x0)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Emulation package 5.0.899.0)

Hi Madeline, depending on your version of the C2000 LaunchPad the problem could simply be the jumpers.
The first set of C2000 LaunchPads accidentally shipped without jumpers on J1, J2 and J3, which you need to program the F28027.
Can you verify your jumper settings for me?

If your board looks like this... then the problem is the jumpers are missing.

http://www.digikey.com/product-detail/en/QPC02SXGN-RC/S9337-ND/2618262:

You need your board to look like this

Please verify the jumpers and see if that helps fix it.

Jumpers are in place. I have S1 configured as UP UP DOWN. Could that be the problem?

It appears that so far the 3rd switch on S1 was the issue. I switched it up the UP position and now a connection has been established. Now to solve all of the other problems I'm having....