From: "Theodore A. Roth" <troth@verinet.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, <gdb@sources.redhat.com>
Subject: Re: gdb support for Atmel AVR
Date: Sun, 10 Feb 2002 10:27:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0202091551010.29100-100000@bozoland.mynet> (raw)
In-Reply-To: <3C6457A8.4090801@cygnus.com>
On Fri, 8 Feb 2002, Andrew Cagney wrote:
:)TARGET_ADDR_BIT is the number of significant bits in a CORE_ADDR. For
:)your target that is 32. The remote protocol will use those 32 bits when
:) requesting raw memory.
:)
:)Separatly, you've got 16 bit pointers you need TARGET_PTR_BIT=16. GDB
:)uses the functions pointer_to_address() and address_to_pointer() when
:)converting a C code/data pointer to/from a CORE_ADDR.
<snip>
:)I'd try the above.
I set TARGET_ADDR_BIT to 32 and TARGET_PTR_BIT to 16 and initial testing
looks like it works. I think had the two swapped when I was playing with
this months ago.
Now I have avr support with only the following modifications to gdb from
cvs:
modify: configure.tgt
add: avr-tdep.c
add: config/avr/avr.mt
add: config/avr/tm-avr.h
This makes me much happier than my previous patch with all the other files
it touched.
I'll continue testing and make up a new patch to send out to the avr
community for testing while I wait for copyright assignment papers to show
up.
Thanks for the help.
Ted Roth
next prev parent reply other threads:[~2002-02-10 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 11:53 Theodore A. Roth
2002-02-08 8:33 ` Andrew Cagney
2002-02-08 9:53 ` Theodore A. Roth
2002-02-08 11:20 ` Daniel Jacobowitz
2002-02-08 14:19 ` Theodore A. Roth
2002-02-08 14:29 ` Daniel Jacobowitz
2002-02-08 14:56 ` Andrew Cagney
2002-02-08 15:10 ` Theodore A. Roth
2002-02-10 10:27 ` Theodore A. Roth [this message]
2002-02-10 10:38 ` Andrew Cagney
2002-02-08 12:49 ` Andrew Cagney
2002-02-11 14:18 ` Theodore A. Roth
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=Pine.LNX.4.44.0202091551010.29100-100000@bozoland.mynet \
--to=troth@verinet.com \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--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