From: Brendan Simon <bsimon@ctam.com.au>
To: William Blum <Billb@alerton.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Power PC Application
Date: Mon, 29 Nov 1999 15:02:00 -0000 [thread overview]
Message-ID: <3842F84F.38DD20D0@ctam.com.au> (raw)
In-Reply-To: <3842FB0D.EAA8658D@alerton.com>
William Blum wrote:
> We are working on a Motorola MPC860 Power PC project and want to use
> Insight as the debug platform. The target PPC is a 'bare' system. We
> plan to access the target using Macraigor 'Wiggler' or 'Blackbird' On
> Chip Debug" (OCD) devices. We have the PPC cross-toolchain, based on
> egcs, in place and functional. Can you tell us how we can go about
> applying Insight for use in such an environment?
The Wiggler is only useable on MS-Windows systems. I don't know of any
wiggler drivers for any other OS which is quite annoying; but that's life
I guess. I did a Canadian cross-compile of Insight the was targeted for
powerpc-eabi and hosted on a MS-Windows machine using the Cygwin
environment. It seem to run but it did crash or play up quite often.
This was the very first release of Insight so I put it down to it's
imaturity. Apart from being buggy, the GUI was not settup for remote
downloads to embedded systems. The only way to target the wiggler BDM
was to go to the gdb command prompt and type the usual setup stuff (eg.
"ocd wiggler lpt"). You will need a startup script to initialise the 860
registers and memory map etc. One day I'll get around to looking at
Insight again. We are currently using SDS Single Step on MS-Windows. I
would dearly love to run Insight (preferably on a Linux box).
Brendan Simon.
next prev parent reply other threads:[~1999-11-29 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-29 14:12 William Blum
1999-11-29 15:02 ` Brendan Simon [this message]
1999-11-29 16:06 ` James Ingham
1999-11-29 20:16 ` Brendan Simon
1999-11-30 3:12 ` Kai Ruottu
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=3842F84F.38DD20D0@ctam.com.au \
--to=bsimon@ctam.com.au \
--cc=Billb@alerton.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).