[ECOS] GDB mystery sort of solved

Gary Thomas gary@mlbassoc.com
Fri Apr 2 06:38:00 GMT 2004


Chuck McManis said:
> At 09:41 PM 4/1/2004, Gary Thomas wrote:
>>GDB (nor eCos) will no change the debug channel baud rate on the fly.
>>In GDB, you can adjust this before making the connection via "set
>>remotebaud XXX"
>>
>>Can you elaborate on what you are seeing?
>
> Certainly, I've got the following setup:
>
>          "Demon"
>          (Development
>           Machine)
>            |
>            |
>       +----+--------------+
>                           |
>                    DECServer 700 Terminal
>                         Server
>                  +--+--+--+--+--+--+--+--+
>                                     |
>                                     |
>                               +---------------+
>                                    COM1       |
>                                 Target Machine|-----> To KVM Switch
>                               +---------------+       (vga, kbd)
>                                     |
>                                     V
>                                 Private Network
>
> The terminal server is "named" tty2 (its one of two) but I've given it an
> alias in the host table of "mystic"
>
> Ports on the terminal server as accessed using telnet to ports 2001 (port1)
> through 2016 (port 16). The terminal server does 9600 baud, max.
>
> I boot the target machine and see the Redboot initialization screen on both
> the KVM switch and to a terminal window telneted to the terminal server.
>
> Starting gdb on demon, I type :
>

Try this:
  (gdb) set remotebaud 9600

GDB will assume that it can connect at 38400 unless you tell it otherwise.
It does *not* assume that the port is configured.

> (gdb) target remote mystic:2012
> Remote debugging using mystic:2012
> 0x0000e3e4 in ?? ()
> (gdb) load hello-ecos.srec
> Loading section .sec1, size 0x5205 lma 0x108000
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
>
> This differs greatly from the expected/desired behavior which is:
>
> (gdb) target remote 192.168.110.123:9000
> Remote debugging using 192.168.110.123:9000
> 0x0000e3e4 in ?? ()
> (gdb) load hello-ecos.srec
> Loading section .sec1, size 0x5205 lma 0x108000
> Loading section .sec2, size 0x5fe lma 0x10d208
> Loading section .sec3, size 0x218 lma 0x10d808
> Start address 0x108000, load size 23067
> Transfer rate: 184536 bits in <1 sec, 329 bytes/write.
> (gdb)
>
> In this second go, I've got a second ethernet card in demon connected to
> the 192.168.110.0 network and I'm debugging that way.
>
> If I telnet to the target through the terminal server and use tftp to load
> hello-ecos.srec it works fine. (no debugging though :-)
>
> Anything else I could check/show you ?
>
> --Chuck
>
>


------------------------------------------------------------
Gary Thomas                 |
MLB Associates              |  Consulting for the
+1 (970) 229-1963           |    Embedded world
http://www.mlbassoc.com/    |
email: <gary@mlbassoc.com>  |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



More information about the Ecos-discuss mailing list