This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: MPC860 GDB stub problem...
- To: Gary Thomas <gthomas at redhat dot com>
- Subject: Re: [ECOS] MPC860 GDB stub problem...
- From: Jesper Skov <jskov at redhat dot com>
- Date: 14 Apr 2000 09:09:46 +0200
- Cc: "Alexandre D'Alton" <r9954c at email dot sps dot mot dot com>, ecos-discuss at sourceware dot cygnus dot com
- References: <XFMail.000413101650.gthomas@redhat.com>
>Actually, it looks like it's working fine to me. When the board resets,
>with the GDB stubs in place, it will attempt to connect to a GDB client
>program. You would run this on your host, using a serial connection
>to the target board. You'll need to abandon using the "terminal" program
>(minicom, winterm, whatever) that you used to get the message above.
>
>Run the host-side GDB (e.g. on Linux)
>
> $ powerpc-eabi-gdb
>
> (gdb) set remotebaud 38400
> (gdb) tar rem /dev/ttyS0
> -- at this point, the host side GDB communicates with the target (860)
> -- the '+$T0540:fe005d90;01:00004664;#29' message above, then tells
> -- the host program that a connection has been established
> (gdb)
You may want to add
(gdb) set remotedebug 1
before the 'tar rem' command above. Then you can see what GDB thinks
of the packet.
Jesper