From: "Andy Hare" <andy@hare.u-net.com>
To: "Insight Mail list" <insight@sourceware.cygnus.com>
Subject: Problems with Insight & ARM Angell
Date: Sun, 12 Dec 1999 14:48:00 -0000 [thread overview]
Message-ID: <060601bf44f2$f20b8980$0100000a@dualbeast> (raw)
I have compiled the latest Insight (07/12/99) to target the ARM
processor under NT and cygwin b20.1. The simulator runs fine without any
problems but the connect to an RDI target (ATMEL EB01 development board
running ANGEL) never returns. I get the signup messages from ANGEL but
control does not return.
I have a copy of the ecos toolset for ARM and have added the patches
from Grant Edwards, re-compiled and this works after a fashion, it does
actually allow the code to be loaded onto the development board, but will
not step, continue does however work.
So I know that GDB will talk to the board and run, but I would really
like to get insight working, is there anything I can do to find out where it
is failing and thus help the development effort. If anyone can point me at
the next step then I will try it and get back to you all.
Andy Hare
next reply other threads:[~1999-12-12 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-12 14:48 Andy Hare [this message]
1999-12-13 15:26 ` Fernando Nasser
1999-12-15 16:13 ` Andy Hare
1999-12-15 16:32 ` Fernando Nasser
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='060601bf44f2$f20b8980$0100000a@dualbeast' \
--to=andy@hare.u-net.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).