From: Fernando Nasser <fnasser@redhat.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Angel not present
Date: Tue, 20 Mar 2001 09:31:00 -0000 [thread overview]
Message-ID: <3AB79319.23ABF02@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010320115416.02a377f0@mail.larwe.com>
"Lewin A.R.W. Edwards" wrote:
>
> Hi Fernando,
>
> > > > > >2) Old versions of Cygwin had a problem with the serial port. The
> > > > >
> > > > > I have observed this problem with Cygwin 1.1.8, which is the currently
> > >
> > > I am observing the problem _right now_ on this Win2000 system. It's not a
> >
> >In this case, I think you should post a note to the Cygwin people. They
>
> I don't believe it's a Cygwin problem, though. I am told, and believe, that
> it's an Angel bug.
>
> If you happen to have an AT91EB40 there, try using it with gdb 5.0 at
> 115200bps. For me, it locks up right after the "Angel Debug Monitor.."
> sign-on message, more than 9 times out of 10. This is consistent with what
> I've been told about gdb and angel not switching speeds at the same time.
>
I was looking and some list messages and it seems that GDB 5.0 does have
a problem with RDI on Cygwin. Everyone who switched to a recent GDB
snapshot said that the problem disappeared.
It may well worth a shot.
> When this happens, gdb is locked up and the entire cygwin session needs to
> be killed in order to proceed. That is under cygwin 1.1.8 under Win2000.
>
> Now for another reliability test: I load a simple hello world program and
> stepi through it (connected at 9600bps). I try it three times and it stops
> in a different place each time. When I don't step it, it runs perfectly
> (it's an infinite loop, and it keeps running blinking LEDs, so I know it's
> not just randomly stopping after some amount of time).
>
> I've never had these sorts of problems using gdb talking to gdb stubs, but
> they seem endemic to Angel use.
>
> >it may become irrelevant -- Microsoft stopped selling Win9x altogether.
> >It seems that there is no current way of buying it, just Millennium and
> >2000.
>
> WinME is pretty much 9x with 2000's icons (and a god-awful media player
> applet that takes over your whole life). MS is trying to get the home user
> market firmly weaned off DOS with Windows XP (Whistler) but I am not
> holding my breath... billions of dollars in unsupported legacy peripherals
> out there.
>
> >I still don't understand why I don't see this problem. We must have
> >some different setup somewhere. I haven't done anything too heavy in
> >the 2000 machine though, only in the NT4.0 one. Would it be some 2000
> >problem? I think you should definitively post to the Cygwin list...
>
> I have an NT4.0 (server) box next to me, I quickly tried the 115200bps test
> above and it hung exactly the same way. I haven't tried any further testing.
>
> === Lewin A.R.W. Edwards (Embedded Engineer)
> Work: http://www.digi-frame.com/
> Personal: http://www.zws.com/ and http://www.larwe.com/
>
> "Und setzet ihr nicht das Leben ein,
> Nie wird euch das Leben gewonnen sein."
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-03-20 9:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-20 1:53 Daniel.Andersson
2001-03-20 5:41 ` Lewin A.R.W. Edwards
2001-03-20 6:35 ` Fernando Nasser
2001-03-20 6:51 ` Lewin A.R.W. Edwards
2001-03-20 7:51 ` Fernando Nasser
2001-03-20 8:23 ` Lewin A.R.W. Edwards
2001-03-20 8:40 ` Fernando Nasser
2001-03-20 9:08 ` Lewin A.R.W. Edwards
2001-03-20 9:31 ` Fernando Nasser [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-19 8:59 Daniel.Andersson
2001-03-19 9:05 ` Lewin A.R.W. Edwards
2001-03-19 8:36 Daniel.Andersson
2001-03-19 8:49 ` Lewin A.R.W. Edwards
2001-03-19 9:29 ` 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=3AB79319.23ABF02@redhat.com \
--to=fnasser@redhat.com \
--cc=insight@sourceware.cygnus.com \
--cc=larwe@larwe.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).