• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 80 subscribers
  • Views 4009 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.

JTAG Communication Initialization Failed + Elprotonic FET_Pro430

sri-sri
Genius 4140 points
Other Parts Discussed in Thread: MSP430G2553

Hi All,

I have been working on my custom board with Msp430g2553 on it. I was working fine till a while and all of sudden it stopped working. I mean it is behaving like dead.

What I have done.

1. Turned off and On (many times)

2. Tried to reprogramme micro via Launchpad.
    I have pulled 3 wires from Msp430g2553 ( Gnd, Test and Reset) and have connected them to launchpad with out     Msp430 on it. I have powered the device externally measured to 3.3 volts.

3. While reprogramming with CCS, the error was, Target device not found.

4. While trying to erase the contents of Micro via fetpro_430 the error was, unable to initialize JTAG communication.

I am suspecting that I have drived the micro in to some sort of weired dead mode with my faulty code. is there any way I can reprogramme the micro? Please help me.

Thanks in advance.

  • 0
    Guru 25210 points

    My experience is that if all your connections are correct, then not being able to program with the Elprotronic tool is an indication of a truly dead part.

  • 0 in reply to Brian Boorman
    TI__Guru 68116 points

    One more thing I would try would be to connect to the device using BSL, and perform a mass erase. You can do this using your launchpad with a G2xx device on it to bridge between your PC and your target board that has your G2553 on it - there is an app note on doing this:

    www.ti.com/lit/pdf/slaa535

    www.ti.com/lit/zip/slaa535

    There's also many other threads on using BSL.

    The reason to try this is for just in case your program somehow altered the flash where your code is stored or you have bad code loaded in your part, and now maybe your device is resetting too quickly for JTAG to connect. If you can manage to erase the part in that case you would be able to get back in.

    Regards,

    Katie

    P.S. You may also want to post your particular SBW connections on your board and what components you have on RST, TEST, etc, to make sure they match up with the diagrams in www.ti.com/lit/pdf/slau278 Have you ever been able to program your target board from your launchpad in the past?

  • 0
    Intellectual 310 points

    Hi Sri-Sri,

    If you still experience the problem, try with connecting the VCC of your custom-board to Launchpad VCC along with other three wires. Additionally, connect a 1K resistor between RESET and VCC, if you haven't done so (You might have probably connected a higher value resistor between RESET and VCC, but replace it with 1K). I hope it may correct the problem.

    If it still doesn't communicate with the MCU, make sure that the LaunchPad communicates well by inserting another MCU on it. (I have two Launchpads with me which doesn't communicate at all).

    You mentioned it's a custom-board. I guess this is a common prototype board. If it is, make sure you've cleaned the board properly. In common prototype board, chances of leakage current is very much higher than custom-etched PCB.

    Regards,

    Binoy Raphael.

  • 0
    Genius 4140 points

    Apologies for keeping this thread alive for quite a long time.

    I problem was with the cable, that is connecting our Custom board to MSP430 launchpad board. We have got new sturdy cable and is working now. Thank you so much for all your help. Cheers.

**Attention** This is a public forum