Hello,
I am working with Dr. Brown on the issue of our DCO cal code behaving
differently in gdb than from cold reset. Apparently the "load code.elf"
gdb operation leaves the MSP430 in a state that is different than cold
reset. It now makes sense that this would likely be the case. However, I
did not catch it at first because other pieces of code have worked fine
in gdb without a reset.
With the addition of "monitor reset" to the tail of the startup script,
the code now behaves as expected. Here is the load script that I am
using as .gdbinit.
target remote localhost:17000
echo %% Loading example1.elf to target %%\n
monitor erase all
symbol-file example1.elf
load example1.elf
monitor reset
Thanks for the helpful suggestions. I really find this list and the
list archives to be a great resource to resolve the problems.
Bryce
Bryce Himebaugh
Staff
Indiana University Computer Science Dept
Chris Liechti wrote:
Geoffrey Brown wrote:
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
if its a F1x or F4x device could be interesting conserning problems
with the DCO.
however, additional to the other posters anwers, check that your JTAG
interface does not connect to XIN on the target. old JTAG interfaces
used XIN als additional clock line, but that is not needed anymore.
chris
-------------------------------------------------------
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
