From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32486 invoked by alias); 10 Jul 2007 08:01:22 -0000 Received: (qmail 32476 invoked by uid 22791); 10 Jul 2007 08:01:21 -0000 X-Spam-Check-By: sourceware.org Received: from wx-out-0506.google.com (HELO wx-out-0506.google.com) (66.249.82.232) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 10 Jul 2007 08:01:19 +0000 Received: by wx-out-0506.google.com with SMTP id s7so1133609wxc for ; Tue, 10 Jul 2007 01:01:18 -0700 (PDT) Received: by 10.78.56.19 with SMTP id e19mr1961153hua.1184054477330; Tue, 10 Jul 2007 01:01:17 -0700 (PDT) Received: by 10.78.141.8 with HTTP; Tue, 10 Jul 2007 01:01:17 -0700 (PDT) Message-ID: Date: Tue, 10 Jul 2007 08:01:00 -0000 From: "Sync ma" To: gdb@sourceware.org Subject: Help about RSP command 'p' MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-07/txt/msg00070.txt.bz2 Hi guys, I am working on a board's bootloader, since it was my first time to do such a job, maybe there are many naive mistakes. Anyway, I hope some one could guide me in the right direction. I use a JTAG simulator called BDI2000. From datasheet, it could support gdb debugging. a binary file called 'bootloader.bin' has been 'load 0x80000000 bootloader.bin BIN' in BDI2000 telnet CLI, then I start the cross-gdb and try to connect with simulator, here comes the errors: (gdb) [root@rhl9 tftpboot]# mipsel-linux-gdb bootloader.elf GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=mipsel-linux"... (gdb) set debug remote 1 (gdb) target remote 192.168.35.108:2001 Remote debugging using 192.168.35.108:2001 Sending packet: $Hc-1#09...Ack Packet received: OK Sending packet: $qC#b4...Ack Packet received: Sending packet: $qOffsets#4b...Ack Packet received: Sending packet: $?#3f...Ack Packet received: S05 Sending packet: $Hg0#df...Ack Packet received: OK Sending packet: $p25#d7...Ack Packet received: E02 Remote failure reply: E02 ===== I have referenced Embedding with GNU: the gdb Remote Serial Protocol, 11/99, but I found no description about rsp command 'p', and there even has no handler functions in gdbserver: server.c: main(). Can anyone told me why my cross-gdb send a 'p' rsp command to the BDI2000? Could I select a lower-version gdb to avoid this problem?