Leaderboard

I wanted a neater way to do some breadboarding at my desk, so I built an enclosure with batteries and two power supplies and mounted some breadboards to it. Click the photo to see the build on my blog. -Doc

the time keeping is the least thing u should worry about, i would worry about how to put the circuit together on a breadboard. here is the code needed to keep a no-so-accurate time (may be off a few minutes a day) it's taken and modified from the ti 2xx examples (slac080h.zip i think) msp430x20x3_ta_02.c i tried it on a EZ430 dongle and it's working as expected. i build w/ msg430-gcc but it should built under windows w/ CCS also. . use SMCLK at 1Mhz as based . use calibrated value for clock to maximize accuracy. . count to 50,000 to get a timer interrupt (20 times/sec) . ano

You might find this instructable step informative with regards to the 32k crystal. http://www.instructables.com/id/MSP430-Based-Chronulator-using-Launchpad-chip/step11/Determining-the-32768-kHz-Crystals-load-Capacita/ It explains why the crystal's load capacitance needs to be right. It also gives a way that you can check if you have a freq. meter.

As mentioned in my "New users say Hi!" post I have the goal to create a wiki for real beginners... let's say the target groupe is a 14yo Boy who wants to start with microcontrollers and chooses the launchpad instead of an adruino. the wiki should be simmilar to the PAlib wiki: http://www.palib-dev.com/wiki/doku.php I have started to make a short overview of the wiki here: https://docs.google.com/document/d/1tQd ... edit?hl=en i'm looking for people who can help me with this project. the more people we are the faster it will be finished. i will set up the wiki @ my webspace

Similar to what gatesphere said. In http://focus.ti.com/lit/ug/slau144e/slau144e.pdf, pg 380 WDTCNTCL Bit 3 Watchdog timer+ counter clear. Setting WDTCNTCL = 1 clears the count value to 0000h. WDTCNTCL is automatically reset. 0 No action 1 WDTCNT = 0000h You can reset the watchdog by: WDTCTL |= WDTCNTCL Well, You have to tell the controller how you wish to use the pin. If you want to connect it to an LED, you configure it as an output. If you connect a switch to the pin, you need to configure it as an input. Its not going to work if you connect an LED to the pin, and

By page 10-6 of the MSP430x2xxx family user's guide, you would do it like this in ASM: MOV #WDTPW+WDTCNTCL,&WDTCTL Which in C would look something like: WDTCTL = WDTPW + WDTCNTCL; Assuming WDTCNTCL is defined in the appropriate device header. I haven't looked into it, but it should be. Check it out for yourself? The problem with this is that you'd have to do this every few operations or the program would reset anyways. But maybe you can come up with a solution? Good luck!

Wow! tons of replies. Lots to learn. Like you said, put it in a loop. Or if your running off a hardware timer, slow it down. You kind of explained how a watchdog works. You set up the watchdog,so that your program tickles(or pets aka set a bit) before your watchdog timer expires and resets the chip. If your program runs correctly, it will always "tickle" the watchdog...but if it crashes, it will stop setting the watchdog bit..which will reset the chip. The Volatile keyword lets the compiler know that the variable is HANDS-OFF from optimization. Its normally used when declaring

Here, maybe I can contribute something on this thread to initiate some discussions regarding the easter egg. I compiled the stripped code and compared the symbol dump of the resulting .elf against the .elf that contains the easter egg. The 2 functions jump out right off the bat: tune, tune_map. $ msp430-objdump -t 3p4w-clock.elf > 1.txt $ msp430-objdump -t 3p4w-clock_easter.elf > 2.txt $ diff -y 1.txt 2.txt ... 2c2 < 3p4w-clock_ester.elf: file format elf32-msp430 --- > 3p4w-clock.elf: file format elf32-msp430 70,78c70,76 < 0000ff9e l O .text 0000000c