Changing CCS from Stellaris to MSP430 debugging using MSP430-FET430UIF

Assuming you are using CCSv4, you will need to use a different target configuration.  You can create a new target configuration by the menu Target->New Target Configuration...

With this you can select the appropriate MSP430 FET tool and then debug this target configuration.

OK, I tried that.  I am using CCS V 4.1.2.00027.  I noticed that the MSP430-FET430UIF is not a selection under the target selections.  I tried TI MSP430 USB1, USB2, USB3 then selected MSP430F2112, the processor that I am using.  I then went to Target->Debug Active Project and got an error box: "Specified container for launch configuration does not exist.

Suggestions?

I'm using TI MSP430 USB1 with MSP430-FET430UIF for my F2013 (and other) board.  And noticed my Launchpad uses the same.

When you originally installed CCSv4, did you select to install MSP430 (along with other processors)?

 I usually advise people to install everything (about 1.5 Gbyte) and then you can always upgrade licenses later.

Well how would you tell if the MSP430 is loaded?  I was using the MSP430, then I had a stellaris project which was loaded from the CD that came along with the evaluation board.  Now I can't get back into the MSP 430 mode I guess.

Thinking that perhaps I had a damaged CCS I downloaded a new copy.  I had CCS V4.  Now I have CCS V3.  What happened there?  Still cannot connect to processor.

steve

http://processors.wiki.ti.com/index.php/Download_CCS#CCSv4_Release_Archive

OK, now that the license issues have been resolved I have been able to connect to an evaluation board.  My custom board is having problems though.  I get an error box now that says Error initializing emulator: Could not communicate with FET.  What exactly does that mean?

I also measured Voltages on the JTAG connector:

Pin 4 - 3.3VDC - Vcc

Pin 8 - 3.3VDC - TEST

Pin 9 - 0VDC - GND

Pin 11 - 3.3VDC - RST*

Pin 1 - 3.3VDC - TDO/TDI

Pin 7 - 0VDC - TCK

Pin 5 - 0VDC - TMS

Pin 3 - 0VDC - TDI

Are these Voltages normal?

"could not communicate with FET" means that CCS cannot send commands to the MSP inside the FET. It has nothing to do with the JTAG connection with the target MSP.

If this happens, then there is a problem with the detection of the FETs (virtual) COM port or a wrong COM port is configured or something like this.

I have an evaluation board that this works on and other custom board that the debug unit works on.  So I don't think it is the debugger unit.

I am checking the pins on by one with my scope.  The 3.3VDC on JTAG pin 4 is good.  There is movement on the TEST line on JTAG pin 8.  GND is GND.  The reset, JTAG pin 11, line also has movement on it.  The TDO/TDI line, JTAG pin 1, has movement on it.  The TCK line, JTAG pin 7, has movement on it.  The TMS line, JTAG pin 5, has movement on it.  However, the TDI line, JTAG pin 3, has no movement on it.  It stays at ground all the time.  I am going to run the same tests again with my evaluation board.

Anyone have any more suggestions?

steve 

I had another board built and I have the same problem.  There is no movement on the TDI line.  The MSP-FET430UIF still works with another custom board that I have: MSP430F1222, and an evalution board that I have.  I still can't find any information on the activity of the JTAG lines.