Fw: gdbserver, remote serial protocol and endian issues

["Paul Bartlett" <paul.bartlett@st.com>]

----- Original Message -----
From: "Paul Bartlett" <paul.bartlett@st.com>
To: <ac131313@cygnus.com>
Sent: Tuesday, April 09, 2002 5:28 PM
Subject: Re: gdbserver, remote serial protocol and endian issues


>
> > I assume you mean something like a memory read at &foo only
> works if
>  > done as a 16 bit operation by the remote target.
>
> Yes. There are certain configuration registers for SH4/SH5
that
> appear
> in the memory map that *must* be written using the appropriate
> access size.
>
> > Proposals for an extension to the protocol that implement
this
> have been
> > posted (search for e-mail from jtc).  The memory attribute
> framework was
> > introduced in preparation for this.
>
> I've spent a good proportion of the day trawling the list
> archives for JT Conklin's stuff.
>
> I noticed that he was a prolific contributor up to about 16
July
> 2001 and then just disappeared completely.
>
> A cursory inspection of remote.c shows that the memory
attribute
> changes have made it down to remote_xfer_memory(). I presume
> that all that needs to be done (for remote targets anyhow) is
to
> come up with suitable changes to the rsp and propagate the
> parameters through.
>
> I see that one of JT's last contributions was a suggested
> syntax.
>
> Does anybody have any opinions on which way to go from here?
>
> Paul
>
>