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
