From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6466 invoked by alias); 19 Feb 2003 15:30:49 -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 6447 invoked from network); 19 Feb 2003 15:30:48 -0000 Received: from unknown (HELO jifvik.dyndns.org) (62.253.130.87) by 172.16.49.205 with SMTP; 19 Feb 2003 15:30:48 -0000 Received: from eCosCentric.com (garibaldi.jifvik.org [172.31.1.2]) by jifvik.dyndns.org (Postfix) with ESMTP id D34A1383DB; Wed, 19 Feb 2003 15:30:42 +0000 (GMT) Message-ID: <3E53A321.1060907@eCosCentric.com> Date: Wed, 19 Feb 2003 15:30:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.2) Gecko/20021203 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Pierre Habraken Cc: gdb@sources.redhat.com, ecos-discuss@sources.redhat.com Subject: Re: [ECOS] Can't connect to remote Evaluator 7T References: <3E539BFB.6B81024F@imag.fr> In-Reply-To: <3E539BFB.6B81024F@imag.fr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00346.txt.bz2 Pierre Habraken wrote: > > Now I want to use RedBoot instead of Angel. > I uploaded redboot.UU onto the board and then verified (using a > communication program) that redboot was properly installed (see redboot > banner below). > But when I launch arm-elf-gdb and type the command 'target remote > /dev/ttyS0' then gdb fails to talk to redboot : > ================================================================= > $ 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) target remote /dev/ttyS0 > Remote debugging using /dev/ttyS0 > Ignoring packet error, continuing... > Ignoring packet error, continuing... > Ignoring packet error, continuing... > Couldn't establish connection to remote target > Malformed response to offset query, timeout > ================================================================= > Could it be that the serial line is not configured as required on the > gdb side ? (using ckermit I had to force parity to none...) Possible, but unlikely since you're receiving stuff at all (packet errors, not just timeout) and I assume you have the baud rate right :-). Before target remote you could do: set debug remote 1 to see what that says. If that doesn't reveal anything interesting then (if I'm remembering right) you can also do: set remotelogfile gdblog.txt before the target remote, which should give a slightly more accurate version of what was sent/received, into the file gdblog.txt. Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine