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.

Unable to program MSP430F5522

I have a lot of experience working with a number of MSP430 parts, however, this one has me stuck.  I've tried to program with both IAR and FETPro Lite using the the JTAG FET programmer but both fail.  I have double checked all the connections and verified that the JTAG pin are connected correctly.    

Here's how I've connected it 

And here's a snapshot of the communication on the JTAG bus..

It seems something is working, but I am unfamiliar with the protocol details to see what the problem is.  

I'm stuck - any suggestions would be appreciated!

  • After much trial and error, I sorted my problem - I didn't have the TEST pin connected.  The other MSP430s I've used did not use a test pin, and it's use isn't really documented well anywhere.  Is it sufficient to tie it high to enable JTAG and leave it high?

    Thanks,
    Reza 

  • the TEST pin switche sbetween port pin and JTAG pin usage on chips which do not have dedicated JTAG pins. The pin is current-driven, not voltage-controlled (and also takes the fuse-blowing current on devices with electrical JTAG fuse). So if it is left floating, the pins are GPIO adn the JTAG electronic is disabled. If it is pulled high, the JTAG part is enabled.
    A permanent high connection is not recommended as it causes unnecessary current consumption if the chip is not under FET control. It should be controlled by the FET and floating if the FET is not connected.

  • Thanks for the info.  I just wish it was more clearly stated someplace, or at least in the documentation for the FET programmer.  It could have been worse, only killed like 3 days trying to figure it out. :)  

  • Well, your posted schematics did not contain the JTAG connector, else I might have noticed it. I did look for it but as it wasn't there, I continued.

    You'd be surprised how often the problem is not where the posters thought it were, but rather in the parts (software/hardware) that weren't provided with the quesiton. Sometimes more is simply more. :)

**Attention** This is a public forum