Hi Steve, There is a function that executes the recalibration of the DCO in the Msp430ClockP.nc file. You could do it yourself whenever you need it. I think the periodic recalibration got removed because most applications don't use the DCO for time critical things.
An other solution for you would be to switch the UART clock over to the 32kHz crystal (ACLK clock), depending on the speed you need. 9600 baud is absolutely no problem to get using that clock. Cheers, Thomas On Sat, Jan 2, 2010 at 3:25 PM, Steve Gulick <[email protected]> wrote: > Hi > > IN the past it seemed the periodic recalibration of the DCO in the MSP430 > had been removed for some reason. Has that been reinstated? Or is there some > means to programaticaly force a recalibration? > > I had been using the DCO as the UART clock source. I found that even at 9600 > baud - in *outdoor* applications the typical temperature changes would cause > the async comm to stop working. I confirmed that the problem was frequency > drift by using a scope and resetting the MSP430 - thus recalibrating the > DCO - would always fix it. > > If there is some reason an automatic, periodic recalibration can not be > done, in my present application the MSP430 always initiates the > communication and it is infrequent so it if there was a routine to force a > recalibration that would work for me - otherwise I will need to use an > external accurate clock source for baud rate generation. > > Thanks > Steve > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
