public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: elf@florence.buici.com
Cc: ecos-discuss@sources.redhat.com, Weilong Li <wli@mtu.edu>
Subject: Re: [ECOS] gdb remote debug problem
Date: Sun, 22 Apr 2001 13:17:00 -0000	[thread overview]
Message-ID: <XFMail.20010422141730.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <20010422125415.A17603@buici.com>

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 <Timeout: 2 seconds>
>  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

  reply	other threads:[~2001-04-22 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-22  3:08 Weilong Li
2001-04-22 10:04 ` elf
2001-04-26  0:59   ` Weilong Li
2001-04-26  7:06     ` elf
2001-04-22 12:54 ` elf
2001-04-22 13:17   ` Gary Thomas [this message]
2001-04-22 13:13 ` elf
2001-04-22 13:20 ` elf
2001-04-22 15:44 ` elf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=XFMail.20010422141730.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=elf@florence.buici.com \
    --cc=wli@mtu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).