From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6950 invoked by alias); 27 Aug 2003 15:00:50 -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 6930 invoked from network); 27 Aug 2003 15:00:49 -0000 Received: from unknown (HELO mail96.atlas.de) (194.221.176.153) by sources.redhat.com with SMTP; 27 Aug 2003 15:00:49 -0000 Received: from VSSRV01.atlas.de (vssrv01.atlas.de [10.200.101.18]) by mail96.atlas.de (Postfix) with SMTP id 77B9113B14 for ; Wed, 27 Aug 2003 17:00:48 +0200 (CEST) Received: from mgsrv01.atlas.de ([10.200.101.16]) by VSSRV01.atlas.de (NAVGW 2.5.1.2) with SMTP id M2003082717004819267 ; Wed, 27 Aug 2003 17:00:48 +0200 Received: by mgsrv01.atlas.de (Postfix, from userid 65534) id 4541C22BD1; Wed, 27 Aug 2003 17:00:48 +0200 (CEST) Received: from mssrv01.atlas.de (mssrv01.atlas.de [141.200.122.90]) by mgsrv01.atlas.de (Postfix) with ESMTP id EB54E22BD1; Wed, 27 Aug 2003 17:00:47 +0200 (CEST) Received: from mssrv03.atlas.de ([141.200.122.92]) by mssrv01.atlas.de with Microsoft SMTPSVC(5.0.2195.5329); Wed, 27 Aug 2003 17:00:48 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Problems with load X-Mimeole: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 27 Aug 2003 15:00:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hylla, Kai" To: "Andrew Cagney" Cc: X-OriginalArrivalTime: 27 Aug 2003 15:00:48.0699 (UTC) FILETIME=[0004B8B0:01C36CAC] X-Spam-Status: No, hits=-5.1 required=5.0 tests=BAYES_01,MAILTO_TO_SPAM_ADDR,QUOTED_EMAIL_TEXT version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-SW-Source: 2003-08/txt/msg00300.txt.bz2 Hi! The sections are loaded. The error is not, that a hole section isn't loaded. Instead contain the loaded sections byte errors. It seems that some bytes aren't written. The debug messages are all OK. As I said before and aren't working either.=20 One of the load debug messages is : Sending packed: $x14000d4,314:8\000[snip] where X14000d4 is the address where the data is written to and 314 is the size of the block which will be written, right? Is there a possibility to change the minimum block size? I.e. limit it to 4 bytes? I think that this will solve the problem... It seems that the target can't handle packages who write data where the data isn't 4 Byte aligned. Thanks and regard, Kai --- K. Hylla Abt. NJT T3 ATLAS Elektronik GmbH A BAE Systems Company Sebaldsbruecker Heerstr. 235 D-28305 Bremen Tel.: +49 421 457-3231 Fax : +49 421 457-1702=20 > -----Original Message----- > From: Andrew Cagney [mailto:ac131313@redhat.com]=20 > Sent: Mittwoch, 27. August 2003 16:32 > To: Hylla, Kai > Cc: gdb@sources.redhat.com > Subject: Re: Problems with load >=20 >=20 > Several things to check: >=20 > - Is the section being loaded marked as LOAD? > Run 'objdump -h ' on the executable being loaded and=20 > check that all=20 > the sections that GDB should load have the LOAD attribute. >=20 > - Is GDB transfering the data? > There should be output from "load" indicating what GDB is=20 > transfering.=20 > Is the missing section in the list. >=20 > - Is GDB really transfering the data? > Enabe remote protocol debugging "(gdb) set debug remote 1" and then=20 > perform a load. You should see memory write packets to the=20 > sections in=20 > question. >=20 > If all of these are ok, then the problem is in the remote end. >=20 > Andrew >=20 > > I've problems using the gdb load instruction. The command=20 > is executed.=20 > > But the file is no written correctly into the RAM. Some=20 > addresses are=20 > > not written. They still contain the value they had prior to=20 > the load=20 > > command. This behavior is address indepentend. If I move the progam=20 > > into anonther location the problem still exist. > >=20 > > I tested some things and discovert that the set instruction is not=20 > > executed if the data type is char or short. (Readaccess=20 > with datatype=20 > > char and shor works.) I'm not sure if this my cause the=20 > load problem.=20 > > If the CPU executes byte or short writes to the memory it=20 > works. So in=20 > > IMHO it can't be a hardwareproblem. > >=20 > > I think that the problem is caused due to a gdb=20 > configuration error. I=20 > > tried several settings (e.g. set download-write-size, set remote=20 > > memory-write-packet-size)but it doesn't help. > >=20 > > I use where OcdLibDemon from=20 > Macraigor=20 > > is listening. If I use or to=20 > write to=20 > > the address it works. Because of that, the OcdLibDemon=20 > configuration=20 > > <-c PPC5XX8XX -d WIGGLER -a 1 -s 1> should be correct. > >=20 > > Which settings I can use to modify gdbs load and set related=20 > > behaviour? > >=20 > > Thanks and regards, > > Kai > >=20 > > --- > > K. Hylla > > Abt. NJT T3 > >=20 > > ATLAS Elektronik GmbH > > A BAE Systems Company > > Sebaldsbruecker Heerstr. 235 > > D-28305 Bremen > >=20 >=20 >=20 >=20