From: "Peter Reilley" <micrio@mv.com>
To: "Hylla, Kai" <hylla.k@atlas.de>
Cc: <gdb@sources.redhat.com>
Subject: Re: Problems with load
Date: Fri, 29 Aug 2003 01:59:00 -0000 [thread overview]
Message-ID: <00ac01c36dd1$34455fa0$c9d145cc@lndnnh.adelphia.net> (raw)
In-Reply-To: <3F4E6220.1000908@redhat.com>
----- Original Message -----
To: "Hylla, Kai" <hylla.k@atlas.de>
Cc: <gdb@sources.redhat.com>
Sent: Thursday, August 28, 2003 4:12 PM
Subject: Re: Problems with load
> > 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.
This packet is aligned on 4 bytes so that can't be the problem.
Can you read the memory back and does it look OK? What errors
are reported when you try to write a byte or short? OcdLibRemote
will print some errors that it sees.
Pete.
Pete.
next prev parent reply other threads:[~2003-08-29 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 15:00 Hylla, Kai
2003-08-28 20:12 ` Andrew Cagney
2003-08-29 1:59 ` Peter Reilley [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-27 7:19 Hylla, Kai
2003-08-27 14:32 ` Andrew Cagney
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='00ac01c36dd1$34455fa0$c9d145cc@lndnnh.adelphia.net' \
--to=micrio@mv.com \
--cc=gdb@sources.redhat.com \
--cc=hylla.k@atlas.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).