From: Stan Shebs <shebs@apple.com>
To: Grant Edwards <grante@visi.com>
Cc: gdb@sources.redhat.com
Subject: Re: What does sh8 "hms" target talk to?
Date: Thu, 23 Oct 2003 18:41:00 -0000 [thread overview]
Message-ID: <3F9820DA.2070709@apple.com> (raw)
In-Reply-To: <20031022230406.GB16318@grante.dsl.visi.com>
Grant Edwards wrote:
>Hi,
>
>I'm trying to figure out what the "hms" target talks to but I'm
>not getting very far. According to the info file it talks to
>
> "A Hitachi SH, H8/300, or H8/500 board, attached via serial
> line to your host."
>
>One presumes that's overly general, and there actually has to
>be some specific chunk of SW running as a ROM monitor on the
>board. What, exactly, does the "hms" target expect to be
>talking to?
>
It's looking for a human-friendly monitor; "r" for registers, "g" to
execute, etc; basically GDB acts as a fast typist. HMS is a couple
generations back, so it's unlikely that the current monitor is
sufficiently compatible.
>
> 1) Current h8 eval boards ship with something called the "HDI"
> embedded monitor (or sometimes "HDI-M", which I gather is
> the same thing). Will gdb talk to that? (I'm guessing
> not.)
>
At least one person (found via Google) claims that the protocol is
similar to GDB's remote protocol, so maybe "target remote" or
"target extended-remote" will work.
>
> 2) If not, can one still get a monitor to which the hms target
> will talk?
>
> 3) Is one better off just burning GDB stubs into flash?
>
> 4) Or maybe RedBoot (which contains gdb stubs)?
>
Apparently HDI source is not available, which means you can't fix target
problems that come up; I'd recommend replacing with your own stubs.
Stan
next prev parent reply other threads:[~2003-10-23 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 23:02 Grant Edwards
2003-10-23 18:41 ` Stan Shebs [this message]
2003-10-23 18:54 ` Grant Edwards
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=3F9820DA.2070709@apple.com \
--to=shebs@apple.com \
--cc=gdb@sources.redhat.com \
--cc=grante@visi.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).