This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: RedBoot+GDB+application combo question
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Stephan Eisvogel <eisvogsn at iis dot fhg dot de>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Fri, 20 Feb 2004 09:19:19 -0700
- Subject: Re: [ECOS] RedBoot+GDB+application combo question
- Organization: MLB Associates
- References: <4036312E.1B1C6601@iis.fhg.de>
On Fri, 2004-02-20 at 09:09, Stephan Eisvogel wrote:
> Hi list,
>
> I've built a working RedBoot loader w/ GDB on a V850E/MS1 system with
> software breakpoints ( "br *" ) and an unused timer output that is fed
> back into the NMI for periodic "bp hit" checking i.e. much like the
> existing V850 port, just heavily tweaked for V850E/MS1.
>
> Now I'm into running the kernel test suite and the question I haven't
> seen answered is, how do I go about the GDB stuff. I have RedBoot in
> internal flash and load the application into RAM. Do I keep the GDB code
> in RedBoot and leave out GDB completely for the application, therefore
> debugging by using RedBoot's GDB, or should I pack GDB into the app and
> make it override RedBoot's VSR table, with RedBoot completely out of the
> picture once I've typed "go"?
>
> If there's more than one way, I'd like the "elegant" route. ;)
Both ways work, but I prefer the "GDB is part of RedBoot" route, because
that way your application can run with or without GDB. If you build the
GDB stubs into your application, it can only be run with GDB.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss