• 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 » Basic Clock Module settings
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 >
  • Forums

    Basic Clock Module settings

    This question is answered
    paddu1
    Posted by paddu1
    on Aug 07 2012 06:09 AM
    Expert1195 points

    Hi,

    This is a basic question about the MSP430 clock settings for MSP430G2xx series.
    Is it required to use the code "clr.b &DCOCTL ; set lowest DCOx and MODx settings"
    when setting the DCO clock.
    The user guide and the sample code recommends below to set the DCO clock.
    clr.b &DCOCTL ; set lowest DCOx and MODx settings
    bis.b #DCO2+DCO1+DCO0, &DCOCTL ; select max DCO Tap
    bis.b #RSEL0+RSEL1+RSEL2, &BCSCTL1 ; select range 7

    Is it safe to remove the "clr.b &DCOCTL" line if we do not need to reconfigure the DCO during program
    execution?

    Regards.
    Paddu.

    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 Aug 07 2012 08:47 AM
      Verified Answer
      Verified by paddu1
      Guru139900 points

      paddu1
      Is it safe to remove the "clr.b &DCOCTL" line if we do not need to reconfigure the DCO during program execution?

      This line is required when you switch the RSEL setting. because when you just switch RSEL while DCOx is in the higher hegions, the resulting DCO frequency might be far too much for the MSP and it will crash.
      Also, during a switch of RSEL, there might be one truncated (= high-frequency) DCO pulse which won't do any good too.
      It is recommended to not only set DCOx back, but also use a /2 divider on MCLK while doing the switch.
      However, to make this precaution work, you must change RSEL before you set DCOx high again. (switch the two bis.b lines in your example)

      In your posted example, the clr.b probably isn't necessary, but it might leave a MODx bit set while DCOx is already on max, which is not a valid setting (even though likely not harmful).

      _____________________________________
      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.
    • paddu1
      Posted by paddu1
      on Aug 07 2012 10:14 AM
      Verified Answer
      Verified by paddu1
      Expert1195 points

      Hello Jens-Michael,

      Thank you so much for the information.

      I understood that we need to set lowest tap when there is a need to switch RSEL(Frequencies).
      And according to my understanding if there is no necessary to switch between
      different frequencies, this code is not ncessary at the begining of the program(intialization of clock)
      because after reset the DCO will start from the lowest settings.

      Regards
      paddu.

      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 Aug 07 2012 12:23 PM
      Guru139900 points

      paddu1
      because after reset the DCO will start from the lowest settings.

      Take another look into the users guide.

      DCOx starts with DCO_3 after a reset, not with DCO_0.

      _____________________________________
      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.
    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