This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: GDB connection via TCP
- To: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Subject: RE: [ECOS] GDB connection via TCP
- From: Gary Thomas <gthomas at redhat dot com>
- Date: Mon, 23 Oct 2000 15:56:56 -0600 (MDT)
- Cc: "Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat, Inc.
On 23-Oct-2000 Fabrice Gautier wrote:
> Hi,
>
> When running RedBoot, I can connect gdb via tcp or serial, I can load a
> program (serial or tcp work), and I succeded running a test program but
> only with serial connection.
>
> When I try to run the test program when connected with tcp, the program
> still try to do diag output via serial but the output is O-packetized as if
> the program thought GDB was on serial.
>
> In the redboot main, there is just before the breakpoint a
> CYGACC_CALL_IF_SET_CONSOLE_COMM(cur); but I don't know when/where 'cur' is
> updated. Anyway removing this line doesn't seem to change anything: serial
> works, tcp doesn't.
>
> I'm wondering if the program itself have to set up the correct diag and/or
> debug channel when it uses te virtual vectors table ?
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.