public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
To: egcs@cygnus.com
Cc: insight@sourceware.cygnus.com
Subject: Re: Power PC Application
Date: Mon, 29 Nov 1999 20:16:00 -0000	[thread overview]
Message-ID: <38434208.5F2F0729@ctam.com.au> (raw)
In-Reply-To: <14403.5508.686402.112185@leda.cygnus.com>

James Ingham wrote:

> Brendan,
>
>  > 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.
>
> Was there anything in particular that seemed to give it trouble, or
> was it just general instability?

It was a while ago now but I think it was a bit of both.  I particularly
remember trying to set breakpoints and it seemed that the code would execute
without ever stopping at the breakpoints.
I've just had a quick revisit and played with it using the simulator target.
I'm impressed again :)  It didn't playup and it broke at every breakpoint.
I noticed that I too had link errors for crt0 so I used -msim.  This implies
that my other tests on our hardware was using the -mads option which may have
been the cause of the problems I was seeing.  Alternatively, I do have access
to a Motorola ADS board and I may have tried with that piece of hardware but it
is so long ago now that I can't quite remember.


>  > 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.
>
> This is not entirely true.  Insight is not currently set up for use with
> the wiggler target.  It IS set up to do normal gdb remote protocol
> stuff.  It is also setup to do some other kinds of DLL based remote
> debugging.
>
> It would be pretty straight-forward to add support for the BDM to
> Insight, and I will be happy to help anyone who wants to do so get
> started.

That would be very cool.  There are quite a few people using BDM for Motorola
processors.  This would also be good the these embedded systems running eCos.
I tried using the BDM with a Linux port to the MPC860 but it died.  The gurus
on the powerpc-linux mailing list said it is impossible to use the BDM with
Linux due to its virtual memory management etc.

Brendan.


  reply	other threads:[~1999-11-29 20:16 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
1999-11-29 16:06   ` James Ingham
1999-11-29 20:16     ` Brendan Simon [this message]
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=38434208.5F2F0729@ctam.com.au \
    --to=bsimon@ctam.com.au \
    --cc=egcs@cygnus.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).