This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: GDB stub for RAM startup.
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Ottawa Guy <ottawaguy81 at yahoo dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 11 Feb 2004 04:50:01 +0000
- Subject: Re: [ECOS] GDB stub for RAM startup.
- References: <20040211042857.39973.qmail@web60903.mail.yahoo.com>
Ottawa Guy wrote:
Hello everyone,
I have a general question about GDB STUB. I have
ported GDB stub for my sparc target.
I download my application code along with all my stub
in to the SDRAM of my target. Inside my application
code main() function, I call breakpoint(). This forces
my application to start listening for GDB command.
Now I startup my gdb host program with '-s' option to
load the symbol table. Then use the "target
extented-remote" to connect to my target.
Now here is my question, I should be able to use
"step" command to step my application code right.
I was also able to use my sparc-elf-insight software
to connect to the target, however when I execute
"run", "insight" downloads the application code. How
can I stop this. I want the sparc-elf-insight to
single step without downloading the code again.
It's an option under something like File->Target Settings... and then "More
options". Or you can use the command line which gives you more control.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
Visit us at Embedded World 2004, Nürnberg, Germany, 17-19 Feb, Stand 12-449
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss