Seeing the recent email, jogged my memory and I went and check something
out.

See below

On Thu, Aug 2, 2012 at 3:24 PM, Franz Gravenhorst <
[email protected]> wrote:

> WHAT TO DO:
>> as i announced last week, everyone should remove this initialize_8mhz
>> function from apps and replace it with fastclock wiring.  if you run the
>> fastclock, you should place a copy of msp430dcospec.h in your app
>> directory, but the copy you reproduce below has an inaccuracy and should
>> read
>>
>> #define TARGET_DCO_KHZ 8000 // the target DCO clock rate in binary kHz
>
>
You really want:

#define TARGET_DCO_KHZ 7812

TARGET_DCO_KHZ is in units of KHZ = 1024 HZ and reall should be labeled as
KiHZ.  It is used in the dco calibration code and referenced as
TARGET_DCO_KHZ/ACLK_KHZ which with 8000 above yields 8000/32 = 250.

This magic number is used by the dco calibation code to tweak the DCO
calibration nobs to match a number of ACLK periods.

Using 8000 above will probably give you a DCO clock more along the lines of
8,192,000 HZ which if you are using a 5438a in VCORE 1 mode (lowest power)
will exceed the specs of the chip.   Also exceeds the spec of the 1611 so
probably is an issue.

This will also effect what you think you are doing for UART, I2C, and SPI
clocking since periperal clocks are derived off the DCO clock (typically).

This is why I've reworked all the msp430 clock code in the tinyprod tree to
use HZ instead of TinyOS's KHZ which is really KiHz which leads to all
kinds of confusion.    And clock is just a tad important.

eric




>>
>>> My problems seems to be realted to this file: "Msp430DcoSpec.h"
>>> If it exists in my source directory, then the Blueooth functionality of
>>> my App does not work any more.
>>> If it does not exist, it is working.
>>>
>>> Contents of this file is:
>>>
>>> #ifndef MS430DCOSPEC_H
>>> #define MS430DCOSPEC_H
>>>
>>> #define TARGET_DCO_KHZ 8192 // the target DCO clock rate in binary kHz
>>> #define ACLK_KHZ 32 // the ACLK rate in binary kHz
>>> #endif
>>>
>>>
_______________________________________________
Shimmer-users mailing list
[email protected]
https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users

Reply via email to