From: Kim Lux <lux@diesel-research.com>
To: gdb@sources.redhat.com
Subject: Re: gdb for multicore processors ?
Date: Thu, 08 Dec 2005 05:49:00 -0000 [thread overview]
Message-ID: <1134020979.27506.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1134020836.27506.21.camel@localhost.localdomain>
One more thing.
XGate code gets compiled to reside in flash. However, it gets relocated
to run from RAM as it runs much faster there. GDB will have to know
that the address it sees in RAM isn't the address it was compiled to.
The file format is elf, if that helps.
Thanks in advance for your ideas.
On Wed, 2005-12-07 at 22:47 -0700, Kim Lux wrote:
> We need to port gdb to handle the Freescale (formerly Motorola)
> 68HC9S12X devices, which have 2 processors: the main CPU called the
> 9S12 and an auxillary IO RISC processor called the XGATE processor.
>
> Each processor has its own register set and instruction set. They are
> not the same. They share the same memory map, but the xgate processor
> addresses things differently.
>
> I'll provide more details of the processors as people need them.
>
> We already handle the 9S12 CPU with gdb in the 68HC9S12 devices. (No
> XGATE on them.)
>
> We interface to the processor via a Background Debug Pod. The 9S12X BDM
> can set breakpoints for each processor independently.
>
> So... how do we set GDB up to handle this ?
>
> We are building the BDM, so theoretically we could connect 2 gdb
> processes to the same BDM, if that helps. That would allow us to have a
> separate GDB instance for each process. Or should one GDB instance
> handle both processors ?
>
> The goal is to use gdb under Eclipse. There it would be preferable to
> have 2 separate instances of gdb.
>
>
--
Kim Lux, Diesel Research Inc.
next prev parent reply other threads:[~2005-12-08 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 5:47 Kim Lux
2005-12-08 5:49 ` Kim Lux [this message]
2005-12-08 13:56 ` Daniel Jacobowitz
2006-09-29 3:30 gdb for multicore processors? Bridge Wu
2006-09-29 18:10 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1134020979.27506.23.camel@localhost.localdomain \
--to=lux@diesel-research.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox