From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17207 invoked by alias); 27 Aug 2004 06:59: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 17191 invoked from network); 27 Aug 2004 06:59:03 -0000 Received: from unknown (HELO smtp.hispeed.ch) (62.2.95.247) by sourceware.org with SMTP; 27 Aug 2004 06:59:03 -0000 Received: from indel.ch (217-162-27-127.dclient.hispeed.ch [217.162.27.127]) by smtp.hispeed.ch (8.12.6/8.12.6/tornado-1.0) with SMTP id i7R6x2rY004617 for ; Fri, 27 Aug 2004 08:59:03 +0200 Received: from fabi.indel.ch [192.168.1.19] by indel.ch [127.0.0.1] with SMTP (MDaemon.v2.7.SP5.R) for ; Fri, 27 Aug 2004 08:57:35 +0200 Message-Id: <5.2.0.9.1.20040827084729.01d1ba90@NT_SERVER> X-Sender: cenedese@NT_SERVER (Unverified) Date: Fri, 27 Aug 2004 06:59:00 -0000 To: gdb@sources.redhat.com From: Fabian Cenedese Subject: Re: bdi2000 and gdb (newbie question) In-Reply-To: <20040826205715.GF6632@john.intrig.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: gdb@sources.redhat.com X-Return-Path: cenedese@indel.ch X-SW-Source: 2004-08/txt/msg00410.txt.bz2 >I've got a bdi2000 and Cogent csb337 running the micromonitor boot loader. >I've been able to compile and download the umon to the csb337 successfully >using the bdi2000 and jtag interface. > >prompt> gdb CSB337_tst.elf > >(gdb) target remote 192.168.100.44:2001 >Remote debugging using 192.168.100.44:2001 >0x00000000 in ?? () snip >Program received signal SIGTRAP, Trace/breakpoint trap. >0x63655220 in ?? () >(gdb) step >Cannot find bounds of current function I don't know this target. But you should look at what data gets returned over the remote interface (was that "set debug remote 1"?). I also had similar effects when I returned wrong data for the registers in my self written stub. Another thing to look at is the endianess. I work with PPC which can be both little and big endian. Maybe you need to set it ("set endian big/lttle/auto"). BTW, 0x63655220 is "ceR " in ASCII or " Rec" if you change order. Maybe this looks familiar? I think some string is interpreted as value for the register (Ok, I know that the remote protocol is MADE of strings :). bye Fabi