This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: (gdb) Couldn't establish connection to remote target


On Tue, 2002-07-30 at 10:23, Rolf Kistler wrote:
> Hi!
> 
> Thank you for helping a newbie (as you may have thought when reading the
> post, I hope I did not bother the ecos pros too much). It worked!
> 
> I thought I did the equivalent in the GUI of the config tool. However, using
> the commandline tool as proposed did the job (I just used the command line
> to build our application). What is the difference between the two tools? Or
> better, what was it that I have built?
> 

Did you actually import the ...FLOPPY.ecm file using the GUI.  That's
probably the biggest possibility for problems.  Without it, you'd most
likely end up with a RedBoot which didn't have GDB support in it.

Note: next time, copy even messages like this to the ecos-discuss list.
That way, everyone gets to benefit from the answers, as well as being
archived for the future.

> However, many thanks.
> 
> Rolf
> 
> 
> 
> -----Original Message-----
> From: Gary Thomas [mailto:gary@chez-thomas.org]
> Sent: Dienstag, 30. Juli 2002 16:44
> To: kistler@bbv.ch
> Cc: eCos Discussion
> Subject: Re: [ECOS] (gdb) Couldn't establish connection to remote target
> 
> 
> On Tue, 2002-07-30 at 08:39, Rolf Kistler wrote:
> > Hello!
> >
> > Do you also have an i386 target and try to connect to it through the gdb
> > finding this output on the cygwin shell?
> >
> > (gdb) set remotebaud 38400
> > (gdb) target remote COM1
> > Remote debugging using COM1
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Couldn't establish connection to remote target
> > Malformed response to offset query, timeout
> >
> > After checking plugs, cables, port settings, using terminal programs,
> > sending gdb remote packages by hand, searching the mail list etc. I
> finally
> > tried it with the pre-built redboot.bin on the target (to be found at
> > http://sources.redhat.com/ecos/boards/redbootbins/x86pc/). And see there,
> it
> > works! But why?
> >
> > If someone knows a solution why our own build of redboot (which is 30k
> less
> > in size) does not switch correctly to the gdb mode, please send me an
> > answer.
> >
> > If have used the latest CVS sources configuring them with the 1.3.net tool
> > just plainly using the template "i386 PC Target". The weird thing is that
> > redboot compiles, links, runs and even provides its services on the
> console.
> > But it hangs if you try to send it a gdb packet. Did I miss something? I
> > have tried various configuration changes without result. We would like to
> > make some changes in the source to access the extended RAM and our
> Ethernet
> > controller. But if we are not able to debug it, well.
> 
> Did you try this (or the ConfigTool equivalent)?
>   % ecosconfig new pc redboot
>   % ecosconfig import
> ${ECOS_REPOSITORY}/hal/i386/pc/current/misc/redboot_FLOPPY.ecm
>   % ecosconfig tree
>   % make
> 



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]