B20: serial ports status?

B20: serial ports status?

[Rene.Affourtit]

Hello,

In november 1998 there was a question regarding "gdb serial
cross-debugging" (
http://sourceware.cygnus.com/ml/cygwin/1998-11/msg00297.html )

1:  Has anyone succesfully talked to the arm-Angel using a serial line and
using b20? If so what version of gdb /angel did you use?
2: Have these problems been solved  in any of the snapshots? if so which
one?

versions:
Cygwin b20
gdb 4.17 (can't get 4.18 to build yet, but there is enough about that in
the ml-archive :-)
Angel version 1.04 and 1.20 both give the same result. (the funny thing is
when I don't connect the serial line to the board I get exactly the same
output.)

thanks in advance,
    Rene Affourtit

output of gdb:
GNU gdb 4.17-ecosSWtools-arm-990321
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.  This version of GDB is
supported
for customers of Cygnus Solutions.  Type "show warranty" for details.
This GDB was configured as "--host=i586-cygwin32 --target=arm-elf".
(gdb) target rdi s=com1
   DEBUG: Buffer allocated in angel_RDI_open(type=10).
   negotiate_params
   sent negotiate packet
RDI_open: undefined error message, should reset target
   DEBUG: Entered angel_RDI_info.
   DEBUG: RDIInfo_Target.
   wait_for_debug_message waiting for 80010001

(indented lines are debug info from gdb)



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: B20: serial ports status?

[Chris Faylor]

On Thu, Mar 23, 2000 at 11:00:26AM +0100, Rene.Affourtit@pemstar.nl wrote:
>In november 1998 there was a question regarding "gdb serial
>cross-debugging" (
> http://sourceware.cygnus.com/ml/cygwin/1998-11/msg00297.html )
>
>1:  Has anyone succesfully talked to the arm-Angel using a serial line and
>using b20? If so what version of gdb /angel did you use?

Serial I/O in b20 is broken.

>2: Have these problems been solved  in any of the snapshots? if so which
>one?

There is apparently a problem with an interaction between the arm-Angel
and cygwin.  It is strange in that no other targets are reported to be
affected.  This is true of recent snapshots, also.

Sorry.  I would like to have someone debug and fix this problem but the
current state is that there is no fix.  Well... actually someone here
did create a DLL that seemed to work around the problem but I don't think
that it actually solved anything.  They just compiled the cygwin select.cc
file with -g rather than with "-O2 -g".

Christopher Faylor
Cygwin Engineering Manager
Cygnus Solutions, a Red Hat company

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: B20: serial ports status?

[Andy Hare]

This problem shows itself to be in the select() function call within the
serial_read code. I am currently trying to find and fix this problem but I
may be sometime as it has to fit in with my MSc studies and with getting
married in the summer, both of which suck most of my free time away.

I am using angel/ARM with a Atmel EB01 under NT and using Insight to drive
it. The problem only appears to affect the single stepping modes as the run
and continue modes do appear to function, but there is not as much comms
going on at this point.

Andy Hare

http://www.ahare.btinternet.co.uk for Atmel ARM tools

----- Original Message -----
From: Chris Faylor <cgf@cygnus.com>
To: <cygwin@sourceware.cygnus.com>
Sent: Thursday, March 23, 2000 6:49 PM
Subject: Re: B20: serial ports status?


> On Thu, Mar 23, 2000 at 11:00:26AM +0100, Rene.Affourtit@pemstar.nl wrote:
> >In november 1998 there was a question regarding "gdb serial
> >cross-debugging" (
> > http://sourceware.cygnus.com/ml/cygwin/1998-11/msg00297.html )
> >
> >1:  Has anyone succesfully talked to the arm-Angel using a serial line
and
> >using b20? If so what version of gdb /angel did you use?
>
> Serial I/O in b20 is broken.
>
> >2: Have these problems been solved  in any of the snapshots? if so which
> >one?
>
> There is apparently a problem with an interaction between the arm-Angel
> and cygwin.  It is strange in that no other targets are reported to be
> affected.  This is true of recent snapshots, also.
>
> Sorry.  I would like to have someone debug and fix this problem but the
> current state is that there is no fix.  Well... actually someone here
> did create a DLL that seemed to work around the problem but I don't think
> that it actually solved anything.  They just compiled the cygwin select.cc
> file with -g rather than with "-O2 -g".
>
> Christopher Faylor
> Cygwin Engineering Manager
> Cygnus Solutions, a Red Hat company
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com