• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Microcontrollers » MSP430™ Microcontrollers » MSP430 Ultra-Low Power 16-bit Microcontroller Forum » Can spi-bi-wire pins be routed out via board test points?
Share
MSP430™ Microcontrollers
  • Forum
  • Announcements
  • E2E Wiki
Options
  • Subscribe via RSS
MSP430 Resources
  • MSP430 Product Folder
  • MSP-EXP430G2 - MSP430 LaunchPad Value Line Development kit
  • MSP430 Getting Started Guide
  • MSP430 Microcontroller Projects
  • More Resources >
  • Can spi-bi-wire pins be routed out via board test points?

    Can spi-bi-wire pins be routed out via board test points?

    This question is answered
    John Mielke
    Posted by John Mielke
    on Jul 23 2012 19:35 PM
    Prodigy140 points

    Hi,

    With more advanced CPU’s there is usually requirement on JTAG connection such that there better match in length, since clock frequency runs up to dozens of MHz.

    If using a 1MHz to 12MHz 430 device, what is the frequency for the spi-2-wire JTAG? We checked in MSP430 Programming Via the JTAG Interface User's Guide.pdf and see the 350 kHz ± 100 kHz value, but the document seems only describes this value in the context of flash programming.

    For ordinary program load, run, breakpoint, what is this JTAG frequency? If the speed is low, may I not use any standard JTAG header and just use short wires to connect the 430 device with emulator, for which the scheme looks like:

    430 spy-bi-wire pins→ two test points on board→ two wires/cables with one end soldered on the test points→ MSP-FET430UIF spi-bi-wire pins

    ?

    The quality of connection would definite be inferior as comparing to putting a dedicated JTAG header on board, and saves extra space. Had this ever been done in practice and does it work?

     

     

    John

    MSP430 Jtag
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • Jens-Michael Gross
      Posted by Jens-Michael Gross
      on Jul 25 2012 07:44 AM
      Verified Answer
      Verified by John Mielke
      Guru140085 points

      SBW is a serialized JTAG. I think I read something in the MHz range. Normal JTAG shouldn't be much slower, since SBW requires three times the clock speed to be equally fast, and SBW is slower than normal JTAG. So normal JTAG frequency likely is at least half of SBW frequency or even the same. (I never read any details).
      Also, JTAG/SBW frequency is independent of MSP operating frequency.

      For the RST pin, the recommendation is to have not more than 2.2nF capacitance on the RST pin or SBW may fail.

      John Mielke
      see the 350 kHz ± 100 kHz value, but the document seems only describes this value in the context of flash programming.

      The 350kHz looks strange (too low) to me. However, the flash controller requires 350kHz +-100kHz clock speed (not necessarily the MCLK speed) for programming the flash.

      To program flash through JTAG, the software usually injects a small code snippet into RAM and lets it execute by the CPU. In theory, JTAG could directly program flash too, but since it requires checking for flash controller registers etc, this would be much slower than when executed by the CPU. However, in any case, the controller requires the proper working frequency. On 5x family devices, the flash controller has its own internal oscillator for the proper clock.

      Out of curiosity, I just did connect a logic analyzer to my 5438 target board. The maximum frequency I observed for 4-wire JTAG on TCK was 4MHz (50% DC). On TDI or TDO, the maximum was 2MHz. In SBW mode, the observed frequencies were 1MHz (actually 666.66kHz but with a DC of 25%) or less for the clock and less for the data line.
      This was done with an MSP-FETU430IF and the elprotronic software.
      Note that after reset, the default CPU frequency of the 5x family is ~1MHz (= much slower than JTAG), on 1x family even only ~600kHz.

      About the header, well, in our devices there is a 10-pin combo header that contains the JTAG pins, VCC, and RS485. The FET is connected by an adapter. Sicen we already needed RS485, VCC/GND and RST, adding a few more pins was no problem. And if you need a removable connection (don't want the FET hardlinked forever), a dedicated header is usually better than a test point.

      _____________________________________
      Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.
      If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • TonyKao
      Posted by TonyKao
      on Jul 25 2012 09:02 AM
      Genius3770 points

      The datasheet states that the maximum SBW frequency is 20mhz, while the max JTAG frequency is 5mhz (or 10mhz for some newer ones), which makes sense since it is a half duplex line with three signals encoded, and 20mhz would still make it slower than JTAG. However as JMG observed I don't think a FET would approach nearly that fast a frequency when doing SBW.

      Tony 

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Jens-Michael Gross
      Posted by Jens-Michael Gross
      on Jul 25 2012 10:42 AM
      Guru140085 points

      TonyKao
      I don't think a FET would approach nearly that fast a frequency when doing SBW.

      Not those FETs with the 1612 processor which has a maximum MCLK of 8MHz :)

      _____________________________________
      Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.
      If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • John Mielke
      Posted by John Mielke
      on Jul 25 2012 13:24 PM
      Prodigy140 points

      Jens and Tony,

      Thanks both, and especially to Jens for the values which are truly helpful.

      We asked someone doing MSP430 for years and he said that he had succeeded many times even using software connection out of the board for JTAG debugging/programming. Most likely SBW just works slower, rather than at a multiplied speed of JTAG. We will test these ourselves.

       

      John

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    TI E2E™ Community
    • Support Forums
    • Blogs
    • Videos
    • Groups
    • Site Support & Feedback
    • Settings
    TI E2E™ Community Groups
    • TI University Program
    • Make the Switch
    • Microcontroller Projects
    • Motor Drive & Control
    Other Communities
    • Deyisupport
    • Designsomething.org
    • beagleboard.org
    • TI on Element 14
    • TI on TechXchangeSM
    Other Technical & Support Resources
    • WEBENCH® Design Center
    • Product Information Centers
    • Technical Documents
    • TI Design Network
    • TI Technical Articles
    • TI Training

    All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

    Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

    Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
    TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

    TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
    embedded processors, along with software, tools and the industry’s largest sales/support staff.

    © Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
    Trademarks | Privacy Policy | Terms of Use