This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: GDB connection via TCP
- To: 'Gary Thomas' <gthomas at redhat dot com>
- Subject: RE: [ECOS] GDB connection via TCP
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Mon, 23 Oct 2000 16:53:22 -0700
- Cc: "Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
> -----Original Message-----
> From: Gary Thomas [mailto:gthomas@redhat.com]
> Sent: Monday, October 23, 2000 2:57 PM
> To: Fabrice Gautier
> Cc: Ecos-List (E-mail)
> Subject: RE: [ECOS] GDB connection via TCP
>
>
> You need to make sure that these two values are defined in your CDL
> CYGSEM_HAL_VIRTUAL_VECTOR_DIAG
> CYGNUM_HAL_VIRTUAL_VECTOR_CONSOLE_CHANNEL_DEFAULT
> Most likely, you don't have the latter. If these are not
> both defined, then
> the ethernet I/O can't work completely.
The later was not present but this is not the main problem.
The problem was/is that CYGPRI_HAL_IMPLEMENTS_IF_SERVICES was always defined
because there was no CYGSEM_HAL_USE_ROM_MONITOR option.
Now I added this one (copied from the assabet CDL) but I couldn't activate
it because the RAM startup required to include the GDB Stub.
I can indeed remove this dependency but in fact i'm not sure that's what I
want to do. For If I remove the included gdb stub I loose he thread
support...
In fact I think that what I want to do is to use redboot only as the
provider of the communications channels - particularly over TCP.
How do you think this should be handled ?
--
Fabrice Gautier
fabrice_gautier@sdesigns.com