Unable to use CCS5.2 and MSP430-JTAG-TINY-V2 with a SBW only device

[Chester Gillon]

I am trying to use CCS 5.2 to debug a MSP430F5510 in a OLIMEXINO-5510, using a MSP430-JTAG-TINY-V2 with olimex.dll v1.0.4.2. CCS reports the error:

Code Select Expand

MSP430: Error connecting to the target: Could not find device (or device not supported)The Olimex MSP430 Programmer can read the MSP430F5510 when SpyBiWire is selected.

I think the problem is that CCS 5.2 doesn't have an option to force either JTAG or SBW mode, and the olimex.dll v1.0.4.2 and/or MSP430-JTAG-TINY-V2 don't support an automatic selection between JTAG or SBW mode.

A different way of illustrating the problem is to use IAR Kickstart. With the Debug Protocol set to Automatic Selection attempting to debug in IAR fails with:

Code Select Expand

Sun Sep 23, 2012 22:50:12: Firmware version 10004002
Sun Sep 23, 2012 22:50:12: Interface dll version 1.0.4.2
Sun Sep 23, 2012 22:50:20: Fatal error: Could not find device (or device not supported)   Session aborted!

And when the Debug Protocol is set to a Manual Selection of Spy-Bi-Wire IAR can then debug:

Code Select Expand

Sun Sep 23, 2012 22:52:59: Firmware version 10004002
Sun Sep 23, 2012 22:52:59: Interface dll version 1.0.4.2
Sun Sep 23, 2012 22:53:00: Device : MSP430F5510
Sun Sep 23, 2012 22:53:00: External voltage : 3.3 V
Sun Sep 23, 2012 22:53:00: VCC voltage : 3.3 V
Sun Sep 23, 2012 22:53:01: Download complete.

Can the Olimex.dll be enhanced to support and automatic selection between JTAG or Spy-Bi-Wire?

[Chester Gillon]

The same problem occurs with a MSP430-JTAG-TINY-V2 and olimex.dll v2.0.0.5

[LubOlimex]

Sorry for the delay I will try to test thoroughly this automatic switch as soon as possible. I've not forgotten the problem. Can you tell me which version IAR EW for MSP430 you used for the IAR test?

Regards,
Lub/OLIMEX

[Chester Gillon]

For the IAR test I used IAR Embedded Workbench Kickstart for MSP430 5.50.1

(this is the free code size limited version, download link is at http://processors.wiki.ti.com/index.php/IAR_Embedded_Workbench_Kickstart_for_TI_MSP430_Release_Notes#FET613_-_IAR_Embedded_Workbench_for_MSP430_version_5.50.1.2C_slac050)

[LubOlimex]

I've got an update, Chester,

I'll start with what I have for IAR EW for MSP430. The configurations from the IDE seem to act different. If you have replaced both msp430.dll and you have added/replaced olimex.dll (both version 2.0.0.5) in the IAR for MSP430 binary folder then you have the option to select either Texas Instruments FET USB or Olimex USB configuration in Debugger tab in your project options. The interesting starts here: if you select Texas Instruments one (MSP430.dll responsible for it) it will NOT automatically switch to SBW mode (I just cut the cable so only the 5 wires for the SBW are there - wires 2,3,8,9,11 - VCC_TOOL, VCC_TARGET, TEST, GND, RESET); but if you select Olimex USB profile (connected with Olimex.dll) it will switch and debug in SBW just fine. So for now use the Olimex configuration (it is somehow even preferable since you can keep the original MSP430.dll in case you use original TI FET debugger also).

Now the situation about the CSS v5.x is different since you can't force SBW in CCS v5.x. It will always try 4-wire and if 4-wire is not available it will try SBW. Using the same cut cable I was unable to debug with Olimex JTAGs. It turns out that it is a bug in the firmware since part of the code runs through the pins required for the JTAGs (and they are cut in my case). Note that the bug is only true for processors which have both 4-wire and SBW interfaces available. If a processor has only SBW interface there shouldn't be a problem (but I still haven't tested all possible scenarios). We are working on a permanent solution and a firmware update should be available soon.

Thanks for notifying us on the problem.

Best regards,
Lub/OLIMEX