Hi Brain,
brain freeze wrote:
Hello,
I am currently trying to learn to use the insight
debug environment. Everything seems to go well until
I go to look at the memory locations that I know are
pointed to by my variable designations (they start at
0x200h). Otherwise I can step through the code and
download the program without any errors. Anyway, they
stay at 0x0000h even though I know they should be
changing. The code is simply counter variables set to
increment once each time a Timer A compare ISR occurs.
I know the code itself is working because using the
IAR c-spy tool, I can watch the memory locations
change.
This is strange. I use Insight on WinXP and Linux, and never have this
problem. I can inspect and change memory OK with either the Insight
memory window or the console window. Are you using a msp430-gdbproxy or
the simulator?
Another observation I saw is that you have to type
"monitor erase" in the gdb console to delete flash
memory, otherwise the download doesn't work.
This is a "feature" :-). Seriously, its a limitation of trying to use a
standard debugger. I aim to make things a bit more transparent when
dupport for the latest GDB is complete.
Enviroment is Windows XP, gdbproxy, mspgcc05062003
build, pc laptop.
I use exactly when, when I have to suffer using Windows.
Regards,
Steve
