Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Newman <markn_46@yahoo.com>
To: Torsten Mohr <tmohr@s.netic.de>, gdb@sources.redhat.com
Subject: Re: transfer own data via GDB remote protocol, flash a micro
Date: Mon, 08 Dec 2003 22:22:00 -0000	[thread overview]
Message-ID: <20031208222238.75946.qmail@web13804.mail.yahoo.com> (raw)
In-Reply-To: <200312082123.40897.tmohr@s.netic.de>

As for reading the numbers:

READ MEMORY 
 
Syntax 
 m<addr>,<len> 
 Read len bytes starting at memory address addr. 
 
Reply 
 hex-data 
 The values of the requested memory in target byte
order. May be shorter than requested, if some of the
memory could not be read. 
 
 
 E<n> 
 n == two-digit error code. 
 
 
  
 NOTE: partial success should be reported as an error.

 
There is a corresponding write but I am not aware of
anything that supports "flash" burning memory.  Is
anyone else aware of anything?

                              Mark Newman

--- Torsten Mohr <tmohr@s.netic.de> wrote:
> Hi,
> 
> lets say i'm building a hardware debugger that
> understands
> GDB remote protocol.  And further, that debugger
> needs
> some info about the hardware that it is attached to.
> 
> Can i somehow transfer this data via GDB remote
> protocol?
> 
> I didn't see anything in the info pages, so i think
> this does not work.
> 
> As an example, i may want to tell the hardware the
> target voltage, the quarz frequency, some settings
> like, ...
> 
> Another question, is it somehow possible to "flash"
> an attached micro via GDB remote protocol?
> 
> 
> Best regards,
> Torsten.
> 


  reply	other threads:[~2003-12-08 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 20:33 Torsten Mohr
2003-12-08 22:22 ` Mark Newman [this message]
2003-12-08 22:53 ` Thierry Moreau

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=20031208222238.75946.qmail@web13804.mail.yahoo.com \
    --to=markn_46@yahoo.com \
    --cc=gdb@sources.redhat.com \
    --cc=tmohr@s.netic.de \
    /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