Re: [ECOS] additional PC (i386) serial ports

["Talia Sound and Vision P/L" <jtalia at ozemail dot com dot au>]

Hi,
Thanks for your quick response.
I hacked plf_stub.c and now we can download the test program using another
serial port
(ser1 for now) in the target. The problem now is the screen output (Hello
eCos world) from the application can't be seen in the gdb console anymore. I
can get it to appear on the target's screen
by setting CYGSEM_HAL_I386_PC_DIAG_SCREEN, but some other process also
prints characters on the target screen, so it's not so clean. How can I get
the application console out back to gdb?
Or alternatively how can I stop the target screen being written to by
anything other than the application?
Thanks again,
regards
Ranj Wickremasinghe

>From: Jesper Skov <jskov@redhat.com>
>To: Talia Sound and Vision P/L <jtalia@ozemail.com.au>
>Cc: ecos-discuss@sourceware.cygnus.com
>Subject: Re: [ECOS] additional PC (i386) serial ports
>Date: Tuesday, 9 May 2000 18:10
>
>
>Talia> Hi, Our application needs to communicate with two devices on
>Talia> two serial = ports. For debugging gdb/Insight requires another
>Talia> serial port. My problem is ecos only seems to recognize = the
>Talia> first two serial ports, and the gdb stub always uses the first
>Talia> port.  The 3rd port need not be in the production hardware,
>Talia> only for debugging. = Ideally the application should use the
>Talia> standard ports (first two) and gdb use the third port. Is = it
>Talia> possible to modify the gdb stub code to do this?=20 Thanks in
>Talia> advance.  Regards Ranj Wickremasinghe.
>
>Yes, look in hal/i386/pc/.../src/plf_stub.c. You could add some CDL
>configury to control which port the GDB stub talks over (and
>contribute it back), or you could just hack it to use COM3 :)
>
>Jesper
>