From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19398 invoked by alias); 1 Jun 2004 12:58:12 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 19343 invoked from network); 1 Jun 2004 12:58:10 -0000 Received: from unknown (HELO smtp.silicomp.fr) (194.51.78.40) by sourceware.org with SMTP; 1 Jun 2004 12:58:10 -0000 Received: from mishima.ri.silicomp.fr ([172.16.80.179]) by smtp.silicomp.fr (8.12.10/8.12.10) with SMTP id i51Cp6UD032573 for ; Tue, 1 Jun 2004 14:51:06 +0200 Date: Tue, 01 Jun 2004 12:58:00 -0000 From: Laurent GONZALEZ To: ecos-discuss@ecos.sourceware.org Message-Id: <20040601150459.4b4c5376@mishima.ri.silicomp.fr> In-Reply-To: References: Organization: silicomp =?ISO-8859-1?Q?ing=E9nierie?= Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.0 required=5.4 tests=none version=2.60 X-Spam-Level: X-Scanned-By: MIMEDefang 2.38 Subject: Re: [ECOS] GDB Initialisation problem X-SW-Source: 2004-06/txt/msg00006.txt.bz2 On Tue, 1 Jun 2004 14:34:58 +0200 e.coullien@faiveley.com wrote: > > > Hi, > > We build a card which looks like the Rattler card with a PPC8270. > But when we used GDB, we have to launch a NEXTI and a JUMP *0x60000 > command to begin debug with GDB at our start adress 0x60000. > If we do directly the CONTINUE command, it began at 0x15de4 instead of > 0x60000. Why GDB doesn't go automaticaly to this adress ? > Is there a file in eCos to change for this? > > > (gdb) target remote 192.168.1.3:9000 > Remote debugging using 192.168.1.3:9000 > 0x0000e8b4 in ?? () > (gdb) load hello.elf > Loading section .text, size 0x8de4 lma 0x60000 > Loading section .rodata, size 0x948 lma 0x68de8 > Loading section .data, size 0x574 lma 0x69730 > Start address 0x60000, load size 40096 (Here it > knows that > the program begins at 0x60000 !!!) > Transfer rate: 320768 bits in <1 sec, 507 bytes/write. > (gdb) nexti > [New Thread 1] > 0x00015de4 in ?? () (Why is it at this adress ?) > (gdb) jump *0x60000 > > Thanks, > Hello, try a simple "continue" instead of "nexti" or whatever. regards, -- GONZALEZ Laurent Silicomp Ingénierie Tel: 33 476 41 66 98 -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss