This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: insight can't connect to the redboot
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: "twomol" <twomol at 126 dot com>
- Cc: "ecos-discuss" <ecos-discuss at ecos dot sourceware dot org>
- Date: 28 Feb 2005 10:12:59 +0000
- Subject: Re: [ECOS] insight can't connect to the redboot
- References: <20050226104833.A767465C06A@smtp.ecoscentric.com>
"twomol" <twomol@126.com> writes:
> Nick Garnett,hello!
>
>
>
> ======= 2005-02-24 18:36:11 wrote:=======
>
> >"twomol" <twomol@126.com> writes:
> >
> >> all,hello
> >> I use insight to connect to the target(ARMS3C44B0) running redboot by serial . After setting the connection parameters and clicking OK button, Insight hangs . But if I use terminal to connect to the redboot ,I type some words like "$g#67 ", it response words like "$G123456789abcdef0...#xx ". Dose this means that the connection with stub is right?
> >> How can I check out what's the problem?
> >> Thanks in advance!
> >
> >That output looks correct for a functioning GDB stub. Instead of using
> >Insight, try using command-line GDB instead, you are more likely to
> >see any error messages. You could also try turning on logging:
> >
> >(gdb) set remotelogfile /dev/tty
> >(gdb) target remote /dev/ttyXX
>
> Thank you very much !
> I'm sorry I use cygwin. Does this also work on Cygwin?
> I do that similarly
> (gdb) set remotelogfile ~/stablog
> (gdb) target remote com1
Have you set the baud rate correctly? Do something like:
(gdb) set remotebaud 38400
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
>>>>> Visit us in booth 2539 at Embedded Systems Conference 2005 <<<<<
>>>>> March 8 - 10, San Francisco http://www.embedded.com/esc/sf <<<<<
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss