From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26608 invoked by alias); 4 Jul 2002 04:33:04 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26597 invoked from network); 4 Jul 2002 04:33:01 -0000 Received: from unknown (HELO TheWorld.com) (199.172.62.104) by sources.redhat.com with SMTP; 4 Jul 2002 04:33:01 -0000 Received: from shell.TheWorld.com (rlh@shell01.TheWorld.com [199.172.62.241]) by TheWorld.com (8.9.3/8.9.3) with ESMTP id AAA23600; Thu, 4 Jul 2002 00:33:00 -0400 Received: from localhost (qqi@localhost) by shell.TheWorld.com (8.9.3/8.9.3) with ESMTP id AAA4220988; Thu, 4 Jul 2002 00:33:00 -0400 (EDT) X-Authentication-Warning: shell01.TheWorld.com: qqi owned process doing -bs Date: Wed, 03 Jul 2002 21:33:00 -0000 From: Quality Quorum To: "KONG, Gangfeng" cc: Daniel Jacobowitz , Andrew Cagney , Subject: Re: Remote target behind console server In-Reply-To: <5.1.0.14.1.20020703182312.028e9410@mailhost.iprg.nokia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-07/txt/msg00042.txt.bz2 On Wed, 3 Jul 2002, KONG, Gangfeng wrote: > > > > > > > Hi, > > > > > > I start the gdb stub on the target by: > > > gdbstart -s 38400 -t /dev/ttyS0 > > > and start the gdb on the development box by: > > > gdb vmlinux > > > gdb) > > > gdb) set remotebaud 38400 > > > gdb) target remote my-server-ipaddr:port #note, the port I put > > > here is the serial port# on the server, > > > #not L4 port, correct? > > > >No, you have to use telnet port here. > > Hi, > > normally, I use the command: > telent server-ipaddr 2001 > to access its port 1. (2002 for port 2, 2003 for port 3 ...) > > It looks like console server already map its L4 port into serial port. I suppose that L4 means port 4 on the server and /dev/ttyS0 on the target then you have to use 'target server-ipaddr 2004'. If L4 means something else, then use another port. How to debug a connection: 1. Make sure that terminal server is properly configured and the cable is good: connect port 4 on the terminal server to the some known working target, e.g. standar UNIX serial port, do 'telnet server-ip 2004' and type stuff on console and check responses. 2. Make sure that gdb stub is workin properly: connect port 4 on the terminal server to debug port on the targe, start gdb stub, again do 'telnet server-ip 2004' and make sure that by hitting return you cause gdb to send you properly formed packets. 3. Start gdb and do 'target remote server-ip:2004' I would be very surprised if it does not work at the point. > > Thanks > GF > Thanks, Aleksey