RE: Problems with load

["Hylla, Kai" <hylla.k@atlas.de>]

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 <set *(char*)> and <set *(short*)> aren't working
either. 

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 

> -----Original Message-----
> From: Andrew Cagney [mailto:ac131313@redhat.com] 
> Sent: Mittwoch, 27. August 2003 16:32
> To: Hylla, Kai
> Cc: gdb@sources.redhat.com
> Subject: Re: Problems with load
> 
> 
> Several things to check:
> 
> - Is the section being loaded marked as LOAD?
> Run 'objdump -h <pgm>' on the executable being loaded and 
> check that all 
> the sections that GDB should load have the LOAD attribute.
> 
> - Is GDB transfering the data?
> There should be output from "load" indicating what GDB is 
> transfering. 
> Is the missing section in the list.
> 
> - Is GDB really transfering the data?
> Enabe remote protocol debugging "(gdb) set debug remote 1" and then 
> perform a load.  You should see memory write packets to the 
> sections in 
> question.
> 
> If all of these are ok, then the problem is in the remote end.
> 
> Andrew
> 
> > I've problems using the gdb load instruction. The command 
> is executed. 
> > But the file is no written correctly into the RAM. Some 
> addresses are 
> > not written. They still contain the value they had prior to 
> the load 
> > command. This behavior is address indepentend. If I move the progam 
> > into anonther location the problem still exist.
> > 
> > I tested some things and discovert that the set instruction is not 
> > executed if the data type is char or short. (Readaccess 
> with datatype 
> > char and shor works.) I'm not sure if this my cause the 
> load problem. 
> > If the CPU executes byte or short writes to the memory it 
> works. So in 
> > IMHO it can't be a hardwareproblem.
> > 
> > I think that the problem is caused due to a gdb 
> configuration error. I 
> > tried several settings (e.g. set download-write-size, set remote 
> > memory-write-packet-size)but it doesn't help.
> > 
> > I use <target remote localhost:8888> where OcdLibDemon from 
> Macraigor 
> > is listening. If I use <monitor char> or <monitor short> to 
> write to 
> > the address it works. Because of that, the OcdLibDemon 
> configuration 
> > <-c PPC5XX8XX -d WIGGLER -a 1 -s 1> should be correct.
> > 
> > Which settings I can use to modify gdbs load and set related 
> > behaviour?
> > 
> > Thanks and regards,
> > Kai
> > 
> > ---
> > K. Hylla
> > Abt. NJT T3
> > 
> > ATLAS Elektronik GmbH
> > A BAE Systems Company
> > Sebaldsbruecker Heerstr. 235
> > D-28305 Bremen
> > 
> 
> 
>