public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo Tyson <hmt@cygnus.co.uk>
To: ecos-discuss@sourceware.cygnus.com
Cc: "Gene Kozin" <gkozin@c-cube.com>, "Stan Shebs" <shebs@cygnus.com>
Subject: [ECOS] Re: ecos/20273 [ECOS] Alert: SPARClite gdb bux (and fix)
Date: Fri, 09 Jul 1999 08:30:00 -0000	[thread overview]
Message-ID: <ptso6x3l88.fsf@masala.cygnus.co.uk> (raw)
In-Reply-To: <199907081842.LAA18286@andros.cygnus.com>


(This message blind copied various places: be careful if replying)

In separate mail I said that we didn't support SPARClite eval boards with a
release of the tools called ecc-98r1 and that a later release called 99r1
should be used, because the eCos SPARClite support work is relatively
recent, and the fact that ecc98r1 "obviously" could not work.

I was wrong: ecc-98r1 ("or better") is the correct toolchain for the
SPARClite releases of eCos that are out there, and it works fine; the tools
in the sourceware site are fine, including the 99-03-19 release of eCos
tools (ecosSWtools-990319).

Now, that bug is genuine, and the patch is welcome, but it escaped our
strict testing regime because the "target sparclite" way of working - using
Fujitsu's own monitor ROM - is not supported by eCos.[1]

Use the CygMon image provided with the release and talk to it using "target
remote ..." (which does support network as well as serial comms) and all
will be well.  That's what we tested.

	- Huge


[1] OK, you *can* use it to load-and-go, *if* your eCos app is configured
suitably, but you don't get debugging facilities or the ability to
interrupt the program or any other nice things... and we didn't test it.

  reply	other threads:[~1999-07-09  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-08 11:29 Gene Kozin
1999-07-08 11:42 ` Stan Shebs
1999-07-09  8:30   ` Hugo Tyson [this message]
1999-07-09 11:33     ` Gene Kozin
1999-07-12  4:15       ` Hugo Tyson

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=ptso6x3l88.fsf@masala.cygnus.co.uk \
    --to=hmt@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gkozin@c-cube.com \
    --cc=shebs@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).