Connexions

You are here: Home » Content » 3.3 - Lab 3: Clocking on MSP430
Content Actions
Lenses

What is a lens?

Lenses

A lens is a custom view of Connexions content. You can think of it as a fancy kind of list that will let you see Connexions through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to Connexions materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual Connexions member, a community, or a respected organization.

This content is ...
Affiliated with (?)
This content is either by members of the organizations listed or about topics related to the organizations listed. Click each link to see a list of all content affiliated with the organization.
  • This module is included inLens: Rice University OpenCourseWare
    By: OpenCourseWare ConsortiumAs a part of collection:"Introduction to the Texas Instruments ez430"

    Click the "Rice University OCW" link to see all content affiliated with them.

    Rice University OCW
  • This module is included inLens: Texas Instruments MSP430
    By: Texas Instruments

    Comments:

    "Basic setup for clocks on the MSP430."

    Click the "TI MSP430" link to see all content affiliated with them.

    TI MSP430
Also in these lenses
  • This module is included inLens: Jacob Borgeson's Lens
    By: Jacob Borgeson

    Click the "Jacob's" link to see all content selected in this lens.

    Jacob's
Tags

(?)

These tags come from the endorsement, affiliation, and other lenses that include this content.

3.3 - Lab 3: Clocking on MSP430

Module by: Naren Anand Based on: Lab 4: Clocking on MSP430 by adrian valenzuela

Summary: In this lab, we will cover various timing options for the MSP430.

The following exercise will show you how to manipulate the clocking system on the ez430. You will need to refer to the ez430's Schematic and User's Guide to correctly configure the clock as specified.
Problem 1: Clock Setup
In order to easily check the state of the clock, output MCLK/SMCLK (they are both defaulted to the same source) from a pin header (HINT: Output the SMCLK from P1.4 on pin 6). Use the oscilloscope to observe the frequency of the clock, and to see the impact of the changes you will make.
  1. Without modifying the clock registers any further, at what clock rate is the processor running at? How is the clock currently configured in order to produce this built-in clock signal? In other words, what is the clock's source and how is the source configured?
  2. Write code that sets the DCOCLK to operate at 8MHz. You should be able to do it in just two lines of code. We will use this clock setup for all future programs unless otherwise noted.
  3. Using your new (8MHz) timer settings and your SOS light system from Lab 1, modify the code so that each "dot" and "dash" delay is for approximately the same ammount of time. Basically, generate the same behavior as the original version but using the new clock settings. What were the original (much slower) settings for the clock? What was changed in order to keep the original blink rate?
Problem 2: VLO Clock Setup
The following is code to set the MSP430 to operate off of the VLO clock. The only problem is that it doesn't work. Macro definitions and logic operations are incorrectly used (although the comments are correct). Without adding or removing any lines of code, properly source the MSP430 off the VLO clock.
WDTCTL & ~WDTPW + WDTHOLD;              // Stop watchdog timer
BCSCTL1 |= LFXT1S_2;                    // LFXT1 = VLO
IFG1 = OFIFG;                           // Clear OSCFault flag
__bis_SR_register(SCG1 + SCG0);         // Stop DCO
Now using these timer settings, repeat number 3 from this lab's problem 1.

Comments, questions, feedback, criticisms?

Send feedback