Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: Pierre.Habraken@imag.fr
Cc: jifl@eCosCentric.com, gary.thomas@mind.be, qqi@theworld.com,
	gdb@sources.redhat.com, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Can't connect to remote Evaluator 7T
Date: Thu, 20 Feb 2003 14:35:00 -0000	[thread overview]
Message-ID: <20030220143509.4677278A6D@deneb.localdomain> (raw)
In-Reply-To: <3E54E606.D1FDC422@imag.fr> (message from Pierre Habraken on Thu, 20 Feb 2003 15:28:22 +0100)

>>>>> Pierre Habraken writes:

> Mark Salter wrote:
>> [...]
>> % stty -a </dev/ttyS0
>> speed 115200 baud; rows 0; columns 0; line = 0;
>> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
>> eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
>> werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 5;
>> -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
>                                                  ^^^^^^^^
> Ok, I got it : hardware control flow was enabled (crtscts instead of
> -crtscts).

Okay. I'm seeing a different connection problem, then.

> So, now the command 'target remote' sets up the connection, but
> uploading (command 'load') the program to the board fails, leaving gdb
> accepting no more keyboard input (not even ^C, I have to kill it from an
> other xterm).

> I attach below the gdb trace with logging disabled and also the contents
> of the file gdblog.txt produced when logging is enabled (beginning of
> the file only) :

> Anyone an idea ?

> Pierre

> ===============================================================
> $ arm-elf-gdb
> GNU gdb 5.2
> ...
> This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf".
> (gdb) set remotebaud 38400
> (gdb) file guirlande
> Reading symbols from guirlande...done.
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> 0x018210a8 in ?? ()
> (gdb) load
> Loading section .text, size 0x3bec lma 0x8000
                                         ^^^^^^
This seems pretty low in memory. Maybe you are overwriting memory used
by the stub.

--Mark


  parent reply	other threads:[~2003-02-20 14:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 14:59 Pierre Habraken
2003-02-19 15:30 ` [ECOS] " Jonathan Larmour
2003-02-19 15:59   ` Pierre Habraken
2003-02-19 16:32     ` Jonathan Larmour
2003-02-19 17:14       ` Mark Salter
2003-02-19 17:35         ` Quality Quorum
2003-02-19 17:41           ` Mark Salter
2003-02-19 17:47             ` Gary D. Thomas
2003-02-19 17:59               ` Jonathan Larmour
2003-02-19 19:22                 ` Mark Salter
2003-02-20 14:27                   ` Pierre Habraken
2003-02-20 14:33                     ` Gary D. Thomas
2003-02-20 14:59                       ` Pierre Habraken
2003-02-21  8:06                         ` Pierre Habraken
2003-02-21 15:14                           ` Gary D. Thomas
2003-02-20 14:35                     ` Mark Salter [this message]
2003-02-20 14:38                     ` Andrew Lunn
2003-02-19 16:44     ` Mark Salter

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=20030220143509.4677278A6D@deneb.localdomain \
    --to=msalter@redhat.com \
    --cc=Pierre.Habraken@imag.fr \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary.thomas@mind.be \
    --cc=gdb@sources.redhat.com \
    --cc=jifl@eCosCentric.com \
    --cc=qqi@theworld.com \
    /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