Error connecting to the target on PICCOLO controlSTICK

While I still don't know why my controlSTICK got hosed, I have found out how to recover it so that the CCS debugger can connect to the controlSTICK. I though that this information might be useful for all other poor souls that got into the same situation.

So, this is the procedure that got my controlSTICK back to life:

1. Install a lead from GND (header J1 pin 32). (I used the wire provided in the kit. I inserted one end onto J1 pin 32 and I inserted a sharp pin in the other end).  

2. Connect the controlSTICK to the USB port (power up)

3. Briefly touch the XRS pin (pin 3) of the F28027 DSP with the lead going to the GND. This resets the DSP. Pin 3 is the third pin clockwise from the dot on the 48-pin PQFP package of the U2 chip on the board.

4. Launch the Code Composer Studio application on your PC.

5. Connect the CCS debugger to the controlSTICK target (menu Debug | Connect). This should be now successfull.

6. After this, program the DSP Flash with a known good code (e.g. the original BlinkingLED project).

7. You're back in business!

Miro

www.state-machine.com  

encountered a similar error (OCS error) while connecting eZdsp kit for TMS320F28335.

resolved after resetting the DSP.

Pankaj,

I have the same problem (http://e2e.ti.com/forums/p/5971/22459.aspx#22459), i tried re-installing code composer, changed the USB cable for other more protected among other things and the error still there.

I contact to the support but they send me the link to download a new version of code composer, but the error still there. So i wold like to know how you solve this problem.

Gaston

HI guys,

       This is a very strange problem. Try re-programming the onboard XDS100 emulator on the controlSTICK and installing the latest verion of CCS. That might make the problem go away. When you install the latest CCS version, please be sure to un-install your older version first.

Re-programming the emulator: http://community.ti.com/forums/t/6237.aspx

Latest CCS: http://community.ti.com/forums/t/7132.aspx

Let me know what happens.

Charlie

When you programmed the flash did either of you set a password for it and lock the device? If you set a password and lock the flash after programming the Piccolo MCU then you won't be able to connect to it using JTAG. This might be what's causing you issues. I would recommend only locking the flash when you take a product to market.

I'm using CCS 3.3.82.13 and CGT v4.1.3.  I have tried your reset solution and it doesn't seem to help.  I had some issues with the stick when I was running my previously installed version of CCS with Win 2000 on my computer.  I reinstalled CCS from scratch and I even installed the seperate drivers for the XDS 100 emulator.  Nothing worked.

I have switched my computer to Win XP (not because of this) and did another fresh install of CCS.  I was able to then get the board to connect and run the LED Blink program.  I gave it to another person to get the serial port running and then he gave it back to me.  Now it doesn't work and I am getting the same error messages I was getting when I had Win 2000.

He suggested that I use the "Load VCP" option on the USB driver configuration and that doesn't see to have helped.

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

Error connecting to the target:
Error 0x80000240/-150
Fatal Error during: Initialization, OCS,
This error was generated by TI's USCIF driver.

SC_ERR_POD_FAIL <-150>
This utility failed to operate the adapter for a custom emulator.
The adapter returned an error for unknown reasons.

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

Error connecting to the target:
Error 0x80000200/-1047
Fatal Error during: OCS,
PTI_ERR_EMU_CLOSE Error Occured at 0x00000000

I/O Port = 0

Board Name: F28027 XDS100 USB Emulator
Cpu Name: TMS320C2800_0

Tried the ground of pin 3 and still would connect.

Downloaded MProg.exe.  Ran it, loading the ept file.  as follows:
[Basic Details]
Device Type=5
VID PID Type=1
USB VID=0403
USB PID=A6D0
[USB Power Options]
Bus Powered=1
Self Powered=0
Max Bus Power=200
[USB Serial Number Control]
Prefix=TI
Use Fixed Serial Number=0
Fixed Serial Number=12345678
[USB Remote WakeUp]
Enable Remote WakeUp=0
[Windows Plug and Play]
Enable Plug and Play=1
[USB String Descriptors]
Manufacturer=TI
Product=Texas Instruments XDS100+RS232 V1.0
[Programming Options]
Only Program Blank Devices=1
[BM Device Specific Options]
USB Version Number=1
Disable Serial Number=0
IO Pin Pull Down in Suspend=1
[Dual Device Specific Options A]
RS 232 mode=1
245 FIFO mode=0
245 CPU FIFO mode=0
OPTO Isolate mode=0
High Current Drive=1
[Dual Device Specific Options B]
RS 232 mode=1
245 FIFO mode=0
245 CPU FIFO mode=0
OPTO Isolate mode=0
High Current Drive=0
[Dual Device Driver Options A]
Virtual Com Port Driver=0
D2XX Driver=1
[Dual Device Driver Options B]
Virtual Com Port Driver=1
D2XX Driver=0
[R Device Specific Options]
Invert TXD=0
Invert RXD=0
Invert RTS#=0
Invert CTS#=0
Invert DTR#=0
Invert DSR#=0
Invert DCD#=0
Invert RI#=0
C0 Signal=-1
C1 Signal=-1
C2 Signal=-1
C3 Signal=-1
C4 Signal=-1
Enable Ext Osc=0
High Current I/O=0
Load D2XX Driver=0
In EndPoint Size=0


I scanned with the MProg program:

Number of Blank Devices = 0
Number of Programmed Devices = 1

so I used Erase option under DEVICE menu.  It appeared to erase.
When scanned again got:

Number of Blank Devices = 1
Number of Programmed Devices = 0

Tried to connect to Code composer and Got following:

Error connecting to the target:
Error 0x00001200/-1041
Error during: OCS, Target,
Device driver: Problem with the Emulation Controller.
It is recommended to RESET EMULATOR.  This will disconnect each
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.


I/O Port = 0

Board Name: F28027 XDS100USB
Cpu Name: TMS320C2800_0

Abort:        Close Code Composer Studio.
Retry:        Try to connect to the target again.
Cancel:        Remain disconnected from the target
Diagnostic:    Run diagnostic utility.

So I went back to MProg and use Program

Used Program option and got:
Programmed Serial Number: TISHUK6M

Ran MProg again and this time programmed it: returned as follows:
Programmed Serial Number: TISHUKTM.

Tried to connect to device via Code composer Studio.  Got following:

Error connecting to the target:
Error 0x00001200/-1135
Error during: OCS, Target,
Unrecoverable emulation error

I/O Port = 0

Board Name: F28027 XDS100USB
Cpu Name: TMS320C2800_0

Abort:        Close Code Composer Studio.
Retry:        Try to connect to the target again.
Cancel:        Remain disconnected from the target
Diagnostic:    Run diagnostic utility


Any other suggestions or did I do the above correctly?

I experienced some similar problems with my Delfino (320F28335) controlStick.

After re-installing old (3.3) CCS and almost going crazy for not being able to access none of my Defino through neither XDS100 or Blackhawk USB2000 with CCS4, I finally figured out that it's just a setting in CCS4 (v.4.0.2.01003) that jams it all up!

If i enable the "silicon real-time mode" in
Preferences -> CCS -> Debug -> Debugger Options -> generic -> "Enable silicon real-time mode (...)" (checkbox)
i can no longer connect to my processor through JTAG. Very annoying, and it took me several days to figure out since the setting does not apply after you terminate the debug session. It won't stop hang until you do a hardware reboot (disconnect the USB wire) on your emulator and cycle the power on your target platform.

Hope this is helpful for someone out there having the same problems.

Hi

I have met the same problem. Though I can't solve the problem yet, I don't think there is a need to re-programming the emulator, because when I use another computer with CCSv4, The control stick works well. The same situation happens to Experiment Kit F28335, OK for one computer but not-OK for another computer.

I guess it should be a probelm of CCS Configuration.

Qian

Hi,

In Step 3, I think it should be "the third pin anticlockwise"

Sorry, I am back again

Just now, I tried a simple but a little stupid way. Just change the project name to a new one. for example "BlinkingLED" changed to "BlinkingLED1".

I am not sure it works to everyone, but it worth a try.

I'd remove all the projects and the targets, and start fresh with a new target configuration.

That's all there is to it with the controlSTICKs, so if you still can't connect perhaps you damaged your hardware.

If you have a controlCARD make sure any switches are set correctly.

Make sure that after you have a target you actually right click and "Connect Target"