public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <kseitz@firetalk.com>
To: Paul_Heijman@eu.omron.com
Cc: insight@sourceware.cygnus.com
Subject: Re: Remote Serial Protocol
Date: Mon, 17 Jul 2000 05:41:00 -0000	[thread overview]
Message-ID: <3972FEF6.DE1A3FCD@firetalk.com> (raw)
In-Reply-To: <4125691F.003B2726.00@eu.omron.com>

Paul_Heijman@eu.omron.com wrote:
> 
> Hi,
> 
> I discovered from the Logfile that my stub doesn't recognize a bunch of commands
> like 'P' and 'Z'.
> Does someone have a (complete) reference of these 'remote serial' commands ?
> I guess the 'P' command writes a single register, but the rest is not clear.

Normally, it is safe to ignore commands that your stub doesn't
recognize/implement.

The protocol definition used to be in remote.c, but it has recently
moved into the info files. I found it by following these nodes:

Target, Remote, Remote Serial, Protocol. The definition is at the bottom
of this page. 'Z' is used to insert a breakpoint, apparently.

Keith

      reply	other threads:[~2000-07-17  5:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-17  2:47 Paul_Heijman
2000-07-17  5:41 ` Keith Seitz [this message]

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=3972FEF6.DE1A3FCD@firetalk.com \
    --to=kseitz@firetalk.com \
    --cc=Paul_Heijman@eu.omron.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).