Roland Zitzke wrote:
Hi,
since I can't get insight to work reliably on my machine I decided to use
gdb in console mode.
However it looks like I am missing something that is necessary to download
the code to the target.
What is your machine? Insight runs OK on Linux, and Windows NT/2000/XP.
It runs OK for me on Windows 98SE and Me, but some people report it is
rather flaky.
gdb> file /msp430/code/olimex/aout.elf
loads the file
gdb> target remote localhost:4000
establishes a connection.
but when I try to issue a run command it sais the program is already
running.
Correct. Confusing, but correct. This is what GDB does. To run a remote
program you need something like:
file /msp430/code/olimex/aout.elf
target remote localhost:4000
monitor erase all
load
c
The "monitor erase all" will clear the flash. "load" will program it
with you new code. "c" will start it running from the reset vector.
gdb> monitor erase all
does not help.
I receive E0 errors from the remote side.
Had you already sent things to gdbproxy which upset it? There seems to
be a bug in GDB where is sometimes says this command is not supported by
the target the first time I issue it. Repeating the command then works.
I don't see the problem you describe.
What are the steps required in which order to get a simple program running
to some source line (breakpoint)?
This only requires standard GDB commands. It works OK for GDB and Insight.
Is anyone using gdb in console mode?
Yep. I alternate between GDB and Insight, as my mood varies.
Does someone have startup settings for this kind of work?
If you have achieved a connection to gdbproxy, you have pretty much
sorted that out already.
Regards,
Steve
