This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
RE: ecos on EDB7111-2
- To: Joon Suan Ong <jsong at cs dot ubc dot ca>
- Subject: RE: [ECOS] ecos on EDB7111-2
- From: Gary Thomas <gthomas at redhat dot com>
- Date: Mon, 26 Jun 2000 05:41:36 -0600 (MDT)
- Cc: ecos-discuss at sourceware dot cygnus dot com
One thing to try is using minicom to connect to the board. Just try this
(3800 8N1) and see what happens when you reset the board. You should see
a string which looks rather like this:
$T050f:882500e0;0d:d0270000;#56
If you're not seeing this, the board isn't running the GDB stubs and we'll
have to look farther.
Note: you did remember to push RESET then WAKEUP I hope.
On 26-Jun-00 Joon Suan Ong wrote:
> Hi all,
>
> I'm having alot of difficulty trying to get the gdb stub to work on an
> EDB7111-2 (rev B) board and hope someone can give me advice on how to
> proceed.
>
> I'm using Redhat 6.2 and built the toolchain from the web instructions
> (binutils-000613, patched gcc-2.95.2 and gdb-5.0). I've tried flashing the
> provided gdb_stub at ecos-1.3.1/loaders/arm-eb7111/cl7111_gdb_module.bin
> as well as using one that I've built (again following the web
> instructions). I'm sure the flashing process works fine. In both cases,
> the stub refuses to talk to gdb on the host. Here's a summary of the gdb
> output:
>
> $ arm-elf-gdb
> GNU gdb 5.0
> <stuff deleted>
> This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf".
> (gdb) set debug remote 1
> (gdb) set remotebaud 38400
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet:
> $Hc-1#09...Sending packet: $Hc-1#09...Timed out.
> Timed out.
> <more timeout messages>
> Ignoring packet error, continuing...
> Couldn't establish connection to remote target
> Malformed response to offset query, timeout
> (gdb)
>
> I've also cvs'ed to the latest version of ecos to build the gdb stub,
> but it still does not work.
>
> I remember in March someone suspected there was a problem with the -2
> revision due to DRAM changes.
> (http://sourceware.cygnus.com/ml/ecos-discuss/2000-03/msg00063.html)
>
> Am I seeing the same problem and is there a fix for it?
>
> Thanks very much!
>