• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 2141 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Trouble programming MSP430F2274 using MSP-FET430UIF

chris marchese
Prodigy 30 points
Other Parts Discussed in Thread: MSP430F2274

Hi,

I'm currently trying to program an MSP430F2274 on a custom board using the MSP-FET430UIF debugger and keep running into an Unknown Device Error.

I'm using CCS version 5.2 on a 64-bit Windows 7 machine. Upon plugging the FET430 into my laptop, the Green LED lights up and stays lit, so I'm confident that the firmware is up to date. The board design is based off of the ez430-RF2500 kit. I've checked the JTAG interface connections several times and strongly believe that they are correct.

Does anybody happen to know of any other possible causes of the "Unknown Device" Error??

I'd be a liar if I said that I was 100% confident in my board design (in fact, I've already had to rewire several components just to get the appropriate power to the right places) so I'm fairly confident that the root of my issues is likely inherent in the board. However, I've done everything I can think of to fix the board but to no avail. My hopes are that some insight as to what causes of this error may point me in the direction to find my problem.

Another concern of mine is that I may have burnt up the MSP during my attempts at rewiring the board. Is there any way to determine whether or not my microcontroller is still functional??

This is for a school project and the deadline is coming up soon, so a prompt response would be greatly appreciated.

Thanks,

Chris

  • 0
    Guru 92251 points

    chris marchese said:
    The board design is based off of the ez430-RF2500 kit. I've checked the JTAG interface connections several times and strongly believe that they are correct.

    How is your MSP430F2274 connected to the MSP-FET430UIF?

    The reason for asking is that the MSP430F2274 on the ez430-RF2500 target board uses the (2-wire) Spy-by-wire inerface rather than the (4-wire) JTAG interface. The MSP430 Hardware Tools User's Guide SLAU278 shows the required Signal Connections for In-System Programming and Debugging for the MSP-FET430UIF.

    The "Unknown Device" is reported when the MSP430.dll / MSP-FET430UIF combination isn't able to read the identity of the target device over the JTAG or Spy-by-wire interface. This could be either:

    a) The target device isn't correctly connected as per the  MSP430 Hardware Tools User's Guide.

    b) The target device is faulty.

    c) Possibly if the target device is running software which disables the JTAG interface at startup, or cause a reset, before the MSP-FET430UIF can attach to it.

    Has the MSP430F2274 ever had code running on it before, or is a new un-programmed device?

    (At the moment I have got a 2nd hand board with a MSP430F2274 which is running an existing program, but all attempts to access with a MSP-FET430UIF over Spy-by-wire cause CCS to report an "Unknown Device" error ans am trying to investigate)

  • 0 in reply to Chester Gillon
    Prodigy 30 points

    Thanks for the fast response. Fortunately, I've been able to get past the "unknown Device" error. It seems as though there may have been a short in the cable I was using to interface the MSP to the debugger.


    I have, however come across a new issue. I have two different boards I am trying to program as they are intended to communicate to each other. The software seems to run fine on one of the boards. However, when I program the second with an identical software load, the WDT interrupt does not seem to occur as it does on the first board. Is this indicative of a faulty device?? If not, is there anything that comes to mind that may cause the watchdog interrupt to occur on one board and not the other?

    To answer your questions:
    1. I am programming using the 4-wire JTAG interface

    2. The devices have never had any software load prior to my tinkering.

  • 0
    Prodigy 10 points
    Guys, i had this problem, using command line programmer, i solved it by changing the port from com7( i guess it is default) to com1 in windows.

**Attention** This is a public forum