Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

MPS430 JTAG design.

Other Parts Discussed in Thread: MSP430FE427, MSP430F2618, ISO7241M

I just begin use MSP430 in my new design.

Here is the reference schematic of JTAG

http://www.ti.com/lit/an/slaa184/slaa184.pdf

 

 

And my DIY JTAG ( it does not work)

Please take a look and tell me what was wrong? Thank you!

  • Hello I am Vishal Patil. I am also first tried to develop my own par-port JTAG  that didn't work. I know that from my  experience that Par-port JTAG doesn't work with Spy-Bi-Wire interface or two wire interface. I  somewhere read  that  par-port  timing do not match with Spy-Bi-Wire interface. I think it should work with four wire JTAG  interface. try it for MSp's With 4 wire JTAG support only ( the MSP which support both Spy-Bi-Wire wire and JTAG  do not work with Par-port  JATAG ) . if you want to debug with par -port JATAG  then Use only MSP  that only supporting  JATAG and not  Spy-Bi-Wire wire. If you are using MSP with both Spy-Bi-Wire and JATAG, I thing it will not work. Due to this G2xxx series, some 2xxx   series do not work with that.

       My suggestion is that JUST buy launchpad . It is very chip. It support USB  Spy-Bi-Wire   debug support. I think it is one of the best tool for getting started .I think it support all devices with Spy-Bi-Wire interface . just get started with launch pad. It is best one.

  • 1. EN1 and EN2 should be connected to Vcc1 and Vcc respectively.

    2. What software do you use on the PC?

     

  • Thank Vishal Patil . I already had lauchpad. it's good.

    But i just begin with msp430fe427 and msp430f2618, they don't have Spy-Bi-Wire, so i tried to build jtag - parallel to program them.

    I have build 2 version, the first taken schematic from olimex-fet (http://olimex.com/dev/images/msp430-jtag-d-sch.gif), and the second is the one in previous port using 7241. But both don't work :(

  • Thank Lichen Wang,

    I did as you mention but it still don't work.

    I using IAR debug, MSP430Flasher form TI, Lite FET Flash Programmer from Elprotronic, and also MSPFET from http://kurt.on.ufanet.ru/. And the chip using is msp430f2618 and msp430fe427.

    I also have a question, look at the appnote, i don't see the RST/NMI, is it can be omitted.

     

  • The software expects certain hardware. If your DIY hardware does not meet that expectation, it will not work. That is why I asked you what software you use.

    Do you know what hardware works with those software you tried? Do you know the details of the hardware they expect?

    Another problem is, TI keeps changing the details of JTAG and they do not tell us what they are doing.

     

  • do you have tried for Olimex . I have tried for that , But it become fail.(I have not tested them with only  JATAG). I think olimex circuit should be work. do you have tried for that.

  • The appnote say "It is designed to be a drop-in replacement board for the MSP-FETP430IF interface box", so i guess i can use it with which soft support MSP-FETP430IF.

    In appnote, they use ISO150, which is bi-directional, but i think  the ISO7241M with 3 ouput, 1input, single-direction is enough.

    From datasheet, the delay of ISO150 is 27ns, while ISO7241M  is 22ns. The working voltage is same.

    And, i don't have MSP-FETP430IF here, can i program msp430 through 4-wire jtag without RST/NMI pin using MSP-FETP430IF.

    Thank you.

  • @ i tried olimex jtag too, fully schematic clone, but it don't work too.

  • Trong Duong Minh said:
    Please take a look and tell me what was wrong?

    Besides the unconnected EN1/EN2 (should be put to GND or VCC accordign to datasheet - liekly VCC), some devices require their TEST pin to be pulled up to enable JTAG mode of the port pins. And some PC software requires the RESET pin to be connected and controllable too, if there is no way to cause the device to reset by a controlled VCC shutdown (which isn't in your case)

  • So the RST/NMI pin is need. And just do as appnote described is not enough. Thank you for your useful explaining.

  • Trong Duong Minh said:
    So the RST/NMI pin is need. And just do as appnote described is not enough. Thank you for your useful explaining.


    Well, JTAG itself will work, and if you write your own software, you can surely do without the RST pin. It is, however, convenient to have a way to reset the device.

    As for TEST, if you don't use the JTAG pins for anything in your applicaiton, you can tie it to high directly on the target PCB, leaving the JTAG interface enabled all the time. However, controlling it from the JTAG adapter is a 'nicer' way. It might be sufficient, to jsut have a pullup on the JTAG side, so if th eadapter is not connected, this pin is floating (whcih is the correct state for this pin if JTAG is not needed).
    If th edevice has dedicated JTAG pins and no TEST pin to switch between I/O port and JTAG, then of course this is void :)

**Attention** This is a public forum