public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Andy Hare" <andy@hare.u-net.com>
To: "Fernando Nasser" <fnasser@cygnus.com>
Cc: "Insight Mail list" <insight@sourceware.cygnus.com>
Subject: Re: Problems with Insight & ARM Angell
Date: Wed, 15 Dec 1999 16:13:00 -0000	[thread overview]
Message-ID: <06df01bf475a$4b58c200$0100000a@dualbeast> (raw)
In-Reply-To: <38558031.25A439A0@cygnus.com>

Fernando,

    Thanks for the tip, the latest dll cured the problem with remote debug
via ANGEL. I have now not a problem with stepping through the code using
insight. I have picked up the latest diffs and will be applying them when I
get some time.
    Now the only problems I have is the code I compile not being the code I
run but this is due to a problem with not understanding the code. I am using
the EB01 from ATMEL and converting the AT91 library they issue to run under
the GCC toolset, some of the defines are not as obvious as they would seem
but I am getting closer.

    Cheers again, and if you need any testing doing I will help if I can.

Andy Hare

----- Original Message -----
From: Fernando Nasser <fnasser@cygnus.com>
To: Andy Hare <andy@hare.u-net.com>
Cc: Insight Mail list <insight@sourceware.cygnus.com>
Sent: Monday, December 13, 1999 11:24 PM
Subject: Re: Problems with Insight & ARM Angell


> Andy Hare wrote:
> >
> >     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.
> >
>
> Hi Andy,
>
> Please download the latest cygwin1.dll snapshot from our site.
> gdb should be able to connect properly to the board after you upgrade
> your dll.
>
> >     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.
> >
>
> What exactly do you mean by "will not step"?
>
> BTW, the latest gdb snapshot has Grant's patches incorporated.
>
> >     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.
> >
>
> At least a few of us are using it with no major problems.
> Please let me know if you still have problems after the updates.
> You can e-mail me directly.  Please send me the exact versions of what
> compiler, gdb, cygwin dll you are using.  What you see on your screen
> will also help.
>
> Regards,
> Fernando
>
> --
> Fernando Nasser
> Cygnus Solutions - Toronto Office       E-Mail:  fnasser@cygnus.com
> 2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
> Toronto, Ontario   M4P 2C9              Fax:  416-482-6299
>
>

  reply	other threads:[~1999-12-15 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-12 14:48 Andy Hare
1999-12-13 15:26 ` Fernando Nasser
1999-12-15 16:13   ` Andy Hare [this message]
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='06df01bf475a$4b58c200$0100000a@dualbeast' \
    --to=andy@hare.u-net.com \
    --cc=fnasser@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).