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.

  • Resolved

Specification for Spy-Bi-Wire protocol to program MSP430G2153

Intellectual 595 points

Replies: 4

Views: 553

Hi

A short summary is: I need a specification for the protocol used to program MSP430 over a 5 pin interface (Spy-Bi-Wire).

The long version is: I want to develop a stand-alone PCB tester/programmer ("Test Box") that will, via a multitude of test pins, perform the following functions on production boards:

1. Test various parameters of the test specimen (internal voltage, current consumption etc);

2. Program in a "Test Program" to the MSP430G2153.  This will not be the final program, but will allow the test specimen to exercise its hardware in a way which is not the final product operation but in a way which allows the Test Box to make various measurements easily.

3. One the "Test Program" is there, the Test Box will make suitable measurements and calculate appropriate values for some parameters.

4. The Test Box will then erase the Test Program.

5. The Test Box will then program in the Final software to the test specimen, which software will have been modified as required incorporating various results from the measurements performed at 3.

6. The Test Box will then perform one or two further tests.

7. The Test Box will then code protect the MSP430G2153.

The need for it to be standalone (no PC connected) and to have our own custom hardware for the various test.measurements, leads me to believe there is unlikely to be anything 'off the shelf' available for this, and we will have to design a special equipment to program the MSP430.  We already do this for Atmel AVR chips on other products.

What I am having trouble finding is a specification for the protocol used to program the MSP430G2153.  Does anyone know if it is available?  The test specimens have 5 contacts available and thus far I have used MSP-FET430UIF for development programming/debugging with this 5 pin interface.  I believe the interface is called "2-Wire JTAG Communication (Spy-Bi-Wire)".  The pins used on the microcontroller are four in number: GND, VCC, Reset and Test/SBWTCK.

Thanks

Tony

  • JTAG / SBW with open source is covered by slau320 MSP430 Programming Via the JTAG Interface

    Also, TI FET's micro / PC side is open software / hardware slac460 MSP430.DLL

    Of course, you can make you own FET, but maybe in your case will be better / more simple to use TI FET hardware with execution customized JTAG command sequence from PC side.

  • Tony Payn
    What I am having trouble finding is a specification for the protocol used to program the MSP430G2153.  Does anyone know if it is available?  The test specimens have 5 contacts available and thus far I have used MSP-FET430UIF for development programming/debugging with this 5 pin interface.  I believe

     Hi, all you need is ready to use or you can build the hardware part you need:

    http://www.ti.com/tool/REP430F

    or Elprotronics same product:

    http://www.elprotronic.com/rep430f.html

     Olimex too has a JTAG programmer isolated with a FLASH on board where you can select which file to program.

     On TI link all schematics and source code are present.

     Regards

     Roberto


     Please login & click    Verify Answer    if this post answered your question.

  • In reply to zrno soli:

    Many thanks Zrno for that, the document slau320 is exactly what I need.  I will also consider options based on your comments regarding FET/PC open information.

  • In reply to Roberto Romano:

    Thank you Roberto, I wasn't aware of these boards but note that they are very close to what I want. I see that they may well form part of my own hardware set-up for programming/testing.

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.