From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: danc@iobjects.com (Dan Conti)
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] ROM startup on EBD7212
Date: Fri, 02 Feb 2001 11:27:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010202141310.00aaa740@larwe.com> (raw)
In-Reply-To: <CAEMICOOKMKAGHPNGNFNGEPKCCAA.danc@iobjects.com>
Hi Dan,
>Sometimes i have seen problems where you can change options in the config
>tool, save them, and they dont get reflected properly in the build tree.
It turns out that this is most assuredly the problem. I don't know if it
applies to the Linux tools as well (probably it does), but the linker
script files are not removed by make clean (which means the Windows config
tool Build -> Clean option doesn't remove them either). They are seemingly
only generated on a totally virgin build.
I have now created two sets of ecos working directories, one for ROM and
one for RAM startup, and everything is working great (Thanks Gary :).
>arm-elf-objdump --disassemble image.exe | less
>and verify the address on the left corresponds to your rom.
arm-elf-objdump -h image.exe shows all the info necessary... it led me on
the trail.
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
next prev parent reply other threads:[~2001-02-02 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 15:07 Lewin A.R.W. Edwards
2001-02-02 5:32 ` Gary Thomas
2001-02-02 6:07 ` Lewin A.R.W. Edwards
2001-02-02 10:57 ` Dan Conti
2001-02-02 11:27 ` Lewin A.R.W. Edwards [this message]
[not found] ` <981100836.3a7a692440df9@imp.imms.de>
2001-02-02 6:15 ` Lewin A.R.W. Edwards
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=4.3.2.7.2.20010202141310.00aaa740@larwe.com \
--to=larwe@larwe.com \
--cc=danc@iobjects.com \
--cc=ecos-discuss@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).