Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Rick.Lee <rickmaillist@gmail.com>
To: Rick.Lee <rickmaillist@gmail.com>, gdb@sourceware.org
Subject: Re: gdb over smbus
Date: Mon, 09 Jul 2007 08:44:00 -0000	[thread overview]
Message-ID: <ee979a50707090143y5c2d453fj5b080b7d078392c6@mail.gmail.com> (raw)
In-Reply-To: <20070706115920.GA10648@caradoc.them.org>

thanks,Daniel,
      there are some incorrect information about this soc, through
smbus interface, cpu core registers, such as status register, register
files r0-rx could not be accessed, all other peripheral registers can
be accessed,including breakpoint enable/disable.
      with these restrictions, is it still possible to do such a
converter to support source level debuging?
      thank you.
Rick

2007/7/6, Daniel Jacobowitz <drow@false.org>:
> On Fri, Jul 06, 2007 at 04:21:46PM +0800, Rick.Lee wrote:
> > hi,all,
> >    I have a soc with smbus interface, through this smbus interface,
> > all kinds of resources on chip can be accessed, such as sram,
> > registers, to set/enable/disable breakpoint, restart soc.
> >    I want to know if it's possible to port GDB on this soc to supoort
> > souce code level debug?
> >    BTW, gcc compiler has been ported to support this kind of soc.
> >    I know little about gdb porting, any information are appreciated!
>
> Probably.  You should write a convertor between your SMBus debug
> interface and the GDB remote protocol, and then connect GDB to it over
> TCP.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>


  reply	other threads:[~2007-07-09  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  8:21 Rick.Lee
2007-07-06 11:59 ` Daniel Jacobowitz
2007-07-09  8:44   ` Rick.Lee [this message]
2007-07-09 11:40     ` Daniel Jacobowitz

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=ee979a50707090143y5c2d453fj5b080b7d078392c6@mail.gmail.com \
    --to=rickmaillist@gmail.com \
    --cc=gdb@sourceware.org \
    /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