From: Richard Earnshaw <rearnsha@arm.com>
To: mckennad@esatclear.ie
Cc: Richard Earnshaw <rearnsha@arm.com>,
gdb@sources.redhat.com, insight@sources.redhat.com,
Richard.Earnshaw@arm.com
Subject: Re: ARM Simulator Bug?
Date: Wed, 03 Sep 2003 13:53:00 -0000 [thread overview]
Message-ID: <200309031353.h83DrLc17626@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 03 Sep 2003 11:36:23 BST." <3f55c427.298a.0@esatclear.ie>
> Hi Richard,
>
> I think I have gotten closer to solving my problem. It relates to the linker
> script I use with compilation of gcc.
>
> If I take the standard armelf.x from the ldscripts directory and link against
> it my problem disappears. My problem is that I wish to place my reset vectors
> at 0x00 not the standard 0x8000. So I change the line:
>
> /* Read-only sections, merged into text segment: */
> . = 0x8000;
>
> to
>
> /* Read-only sections, merged into text segment: */
> . = 0x00;
>
> and my problem resurfaces. At a quick check of my memory contents from gdb at
> 0x00 I get 0x01 as opposed to what I get when I "download" the program using
> Run->Download of 0xEA000015.
>
> Any ideas?
Not really. Does "arm-elf-objdump -xd exe-file" display something
sensible?
R.
next prev parent reply other threads:[~2003-09-03 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 10:36 David Mc Kenna
2003-09-03 13:53 ` Richard Earnshaw [this message]
2003-09-03 13:59 ` gdb run command Raja Saleru
2003-09-03 14:02 ` Tim Combs
-- strict thread matches above, loose matches on Subject: below --
2003-09-03 14:57 ARM Simulator Bug? David Mc Kenna
2003-09-03 15:20 ` Richard Earnshaw
2003-09-04 11:45 ` Richard Earnshaw
2003-09-03 9:13 David Mc Kenna
2003-09-03 9:51 ` Richard Earnshaw
2003-09-02 14:31 David Mc Kenna
2003-09-02 18:17 ` Richard Earnshaw
2003-09-02 11:27 David Mc Kenna
2003-09-02 12:43 ` Richard Earnshaw
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=200309031353.h83DrLc17626@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=mckennad@esatclear.ie \
/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