Slide 1 Slide 2 Slide 3 Slide 4 Slide 5 Slide 6 Slide 7 Product List
MSP430 How to JTAG Slide 3

MSP430 JTAG is by definition the four wire JTAG interface described earlier: TDO, TDI, TCK & TMS. It is present on all MSP430 catalog devices and is the fundamental interface by which every MSP430 can be programmed as well as debugged. The physical interface is defined as a 2x7 14-pin connector and is used on almost all MSP430 development boards and programmers. In addition to the standard four wire JTAG interface, some select MSP430 devices also support a two wire TI-proprietary JTAG interface called Spy-Bi-Wire, or “SBW” for short. Simply put, the TI SBW interface time division multiplexes the TDI, TDO & TMS signals along one data connection and TCK is retained as the second connection for clock. Given the implementation, SBW is a bit slower than standard JTAG but makes connecting to the MSP430 easier by cutting required connections by half. Keep in mind that while there are other methods of programming an MSP430 such as bootstrap loader or a custom interface leveraging MSP430’s flexible in-system programming capabilities, JTAG is the only method of debugging an MSP430 MCU. Lastly, an element of JTAG: boundary scan, which can be used to do signal chain I/O testing in multi-IC designs, is not supported today on the MSP430 portfolio. This has been excluded in order to avoid increased silicon costs and more importantly, avoid increased active and standby currents required when implementing boundary scan. This should not create any issues for developers but should be considered up front in systems where designer’s may have been typically leveraging boundary scan on other embedded processors.

PTM Published on: 2011-12-05