From: "Ramana Radhakrishnan" <ramana.r@gmail.com>
To: raja.saleru@iap-online.com
Cc: gdb@sourceware.org
Subject: Re: gdb load command flow
Date: Fri, 14 Nov 2008 08:13:00 -0000 [thread overview]
Message-ID: <67ea2eb0811140013k607b4ee9nabadc956e85397e1@mail.gmail.com> (raw)
In-Reply-To: <59596.210.143.35.18.1226650011.squirrel@www.iap-online.com>
On Fri, Nov 14, 2008 at 8:06 AM, <raja.saleru@iap-online.com> wrote:
>
> Hi
>
> I would like to know the flow between the gdb and OpenOPCD communication
> when the below command is executed.
>
> (gdb) load
>
> I understand till the flow
>
> command_line_handler -> load_command() -> target_load() -> generic_load()->
>
> from generic load, how it will communicate with gdbserver of OpenOCD ? Is
> it through socket write() or through RSP (remtoe serial protocol) ? for
> sending the executable segments into the target for loading ?
set debug remote on
help set debug
will help you.
cheers
Ramana
>
>
> At the OpenOCD, which function is called for loading ?
>
> Thanks in Advance
> Raja Saleru
>
>
next prev parent reply other threads:[~2008-11-14 8:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <33036.210.143.35.19.1225860010.squirrel@www.iap-online.com>
2008-11-07 7:49 ` gdb internal functionality raja.saleru
2008-11-07 12:21 ` EBo
2008-11-10 10:53 ` Jeremy Bennett
2008-11-07 18:22 ` Michael Snyder
2008-11-14 8:07 ` gdb load command flow raja.saleru
2008-11-14 8:13 ` Ramana Radhakrishnan [this message]
2008-11-14 9:07 ` Jeremy Bennett
[not found] ` <59596.210.143.35.18.1226650013.squirrel@www.iap-online.com>
2008-11-26 1:28 ` gdb remote serial packet has wrong address raja.saleru
2008-11-26 18:46 ` Michael Snyder
[not found] ` <28893.210.143.35.18.1227662837.squirrel@www.iap-online.com>
2009-01-06 10:35 ` adding new commandline interface to gdb ? raja.saleru
2009-01-07 9:09 ` teawater
[not found] ` <17669.210.143.35.18.1231238130.squirrel@www.iap-online.com>
2009-01-20 8:36 ` info watch command raja.saleru
2009-01-20 13:46 ` 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=67ea2eb0811140013k607b4ee9nabadc956e85397e1@mail.gmail.com \
--to=ramana.r@gmail.com \
--cc=gdb@sourceware.org \
--cc=raja.saleru@iap-online.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