From: "KONG, Gangfeng" <gkong@IPRG.nokia.com>
To: Quality Quorum <qqi@theworld.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
Andrew Cagney <ac131313@ges.redhat.com>, <gdb@sources.redhat.com>
Subject: Re: Remote target behind console server
Date: Fri, 05 Jul 2002 13:56:00 -0000 [thread overview]
Message-ID: <5.1.0.14.1.20020705134259.026a0300@mailhost.iprg.nokia.com> (raw)
In-Reply-To: <Pine.SGI.4.40.0207050115590.4236760-100000@shell01.TheWorl d.com>
>
> >
> > In order to check the whole system, I did install a kgdb stub of linux
> on my
> > laptop, so that I can move it around. What I have done are:
> > 1. enable the /dev/ttyS0 in /etc/inittab, then I can login through
> serial port
> > the check whether it works. I connect it to the port 1 of my console
> > server,
> > then, I remotely login into it by 'telnet server-ipaddr 2001'. Works!
> > SO:
> > - target serial port works
> > - console server works
> > 2. I move the laptop target close to my development box, and I use
> serial cable
> > to connect them directly. I start the stub on target by 'gdbstart -s
> > 38400 -t
> > /dev/ttyS0'. And then start the gdb on the development box. Now I
> can use
> > gdb to debug my target box as expected.
> > SO:
> > - the stub on target is ok
> > - the gdb on the development box is ok
>
>
>I suppose that you are using null-modem cable at the point.
Yes.
> > 3. Now I move the laptop target back to the console server and connect
> the port
> > 1 to its serial port and start the stub by 'gdbstart -s 38400 -t
> > /dev/ttyS0', and
> > go the development box to start the gdb and try to access the target
> > box by
> > 'target remote server-ipaddr:2001'.
> > But it fails......
> >
> > I don't know what's wrong.
>
>I suppose port configuration or wrong cable or wrong baud rate, I
>suppose you have to use stright cable here and in many cases authobaud
>feature does not work with gdb stub.
>
>Anyway, connect you rtarget to the terminal server, start gdb stub, do
>'telnet serverip 2001' and try to figure out what is going wrong until
>you see '$...#yy in response to pressing ENTER.
Hi,
You are definitely right. The baudrate is wrong, the console server seems not
to be able to auto-configure the baudrate of its ports. I use your suggestion
'telnet serverip 2001' to talk to every possible baudrate of the target from
9600 to 115200. I can not get '$...#yy' reply in any baudrate. But 9600 set
did give
a me persistent reply '$s05#b8', all of the other baudrate set gave me a series
of changing replies. Late I tried 'target remote serverip:2001' with a 9600
baudrate
stub. I works!
Thank you very much for your help, I understand it better now!
GF
next prev parent reply other threads:[~2002-07-05 20:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 18:12 KONG, Gangfeng
2002-06-28 15:49 ` Andrew Cagney
2002-06-28 17:51 ` Quality Quorum
[not found] ` <Pine.SGI.4.40.0206282044520.3477647-100000@shell01.TheWorl d.com>
2002-06-28 18:45 ` KONG, Gangfeng
2002-06-28 21:29 ` Daniel Jacobowitz
2002-07-02 20:05 ` KONG, Gangfeng
2002-07-02 21:40 ` Quality Quorum
2002-07-03 8:40 ` Andrew Cagney
2002-07-03 18:22 ` KONG, Gangfeng
[not found] ` <Pine.SGI.4.40.0207030038590.3981310-100000@shell01.TheWorl d.com>
2002-07-03 18:26 ` KONG, Gangfeng
2002-07-03 21:33 ` Quality Quorum
2002-07-03 21:55 ` Eli Zaretskii
2002-07-08 9:49 ` Andrew Cagney
[not found] ` <Pine.SGI.4.40.0207040021350.4215142-100000@shell01.TheWorl d.com>
2002-07-04 15:01 ` KONG, Gangfeng
2002-07-04 22:21 ` Quality Quorum
[not found] ` <Pine.SGI.4.40.0207050115590.4236760-100000@shell01.TheWorl d.com>
2002-07-05 13:56 ` KONG, Gangfeng [this message]
2002-07-05 16:21 ` Quality Quorum
2002-06-29 7:45 ` Quality Quorum
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=5.1.0.14.1.20020705134259.026a0300@mailhost.iprg.nokia.com \
--to=gkong@iprg.nokia.com \
--cc=ac131313@ges.redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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