From: "Hylla, Kai" <hylla.k@atlas.de>
To: <gdb@sources.redhat.com>
Subject: Problems with load
Date: Wed, 27 Aug 2003 07:19:00 -0000 [thread overview]
Message-ID: <E3DFC065C0C04D40BFD9DE229C77A1DC1C0E23@mssrv03.atlas.de> (raw)
Hi!
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
Tel.: +49 421 457-3231
Fax : +49 421 457-1702
next reply other threads:[~2003-08-27 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 7:19 Hylla, Kai [this message]
2003-08-27 14:32 ` Andrew Cagney
2003-08-27 15:00 Hylla, Kai
2003-08-28 20:12 ` Andrew Cagney
2003-08-29 1:59 ` Peter Reilley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E3DFC065C0C04D40BFD9DE229C77A1DC1C0E23@mssrv03.atlas.de \
--to=hylla.k@atlas.de \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox