I was having a similar timing issue. When the chip is powered up or reset, the oscillator must be allowed to stabilize for 100,000 cycles or so. My problem happened immediately after a power up and then the chip was put into the LPM3. The oscillator never stabilized and the timing was inaccurate. There is a quick blurb in the user manual in the oscillator section about the situation.
I don't know if this may be the problem but it is worth knowing.

Garret Crisler


----- Original Message ----- From: "Geoffrey Brown" <[email protected]>
To: <[email protected]>
Sent: Friday, December 03, 2004 7:41 AM
Subject: [Mspgcc-users] gdb-proxy disrupting DCO setting code


We're having problem with setting the DCO to provide an accurate Baud rate when attached to a gdb-proxy. The DCO setting code is enabled at the beginning of our code -- the DCO is
derived from a 33kHz crystal.   When we run without
gdb everything is fine. When we run with gdb, even with no breakpoints enabled, the DCO setting
code fails with a high probability.
It's clear that the gdb proxy polls the jtag interface when in continue mode. We don't have the gdb proxy code but we do have TI's debugger DLL from which I believe this was derived. In the DLL code, the status of the processor is checked by doing a read of the processor's
jtag control register.

Does reading the jtag control register disrupt critical timing in the MSP430 (e.g. timer A) ?

Does the gdb proxy use a method different than the MSP430_Status routine provided in
TI's dll  to check the state of a runnning processor ?

Is there a way around the difficulty we're having ?

Geoffrey Brown



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users


Reply via email to