From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Thomas To: elf@florence.buici.com Cc: ecos-discuss@sources.redhat.com, Weilong Li Subject: Re: [ECOS] gdb remote debug problem Date: Sun, 22 Apr 2001 13:17:00 -0000 Message-id: References: <20010422125415.A17603@buici.com> X-SW-Source: 2001-04/msg00286.html On 22-Apr-2001 elf@florence.buici.com wrote: > Today, when I started to do the same thing that worked for me > yesterday, I am getting the behavior you describe. > > I enabled a remotelogfile in GDB and discovered that the remote end > was sending an the initial string, but never responding to further > communication. I'm guesing that my stub isn't running properly. > > - * - From the log file > > w $qC#b4 > r ++$T0508:ec370000;04:e00f0000;#4c > w +$qOffsets#4b > r > w $qOffsets#4b > > This is unexpected as this was working OK so recently and I've not > made either hardware or software changes...that I can think of. > > Try typing in the "w" lines manually and see what happens. I have seen cases where the '+$qOffsets#4b' came in too fast for the target to handle. If this works manually, try generating the target code to run at a different baud rate, say 19200, instead of 38400. Then in GDB you'll need to try: (gdb) set remotebaud 19200 (gdb) tar rem /dev/XXX