From: Jesper Skov <jskov@redhat.com>
To: <Andreas.Karlsson@combitechsystems.com>
Cc: jskov@redhat.com, ecos-discuss@sourceware.cygnus.com, aeb@arm.com
Subject: RE: [ECOS] how to run the program
Date: Thu, 31 Aug 2000 02:08:00 -0000 [thread overview]
Message-ID: <14766.8350.892160.715784@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <2253171AF143D21185A60000F8FA748B0229A93C@pluto.combitech.se>
>>>>> "Andreas" == <Andreas.Karlsson@combitechsystems.com> writes:
Andreas> Which CDL file hal_arm_aeb.cdl?
Yes.
Andreas> This can't be the first time. Anyone out there who have done
Andreas> this and want to share experiences? Why inventing the wheel
Andreas> twice?
The eCos build system builds eCos. Application building/linkage
is done by whatever system the user is using. The output image from
that process needs further mangling to be installed in the AEB flash
(due to the AEB rom monitor).
Basically, the process is just more cumbersome than what is also
required for other platforms - on other platforms you may have to
convert the ELF object to binary for EPROM programming, or convert it
to SREC format for downloading and in-situ flash updating.
For the AEB you simply need to do more than just an objcopy. Indeed,
if you are lucky, someone has already written something to simplify
that process. But it is outside the scope of the eCos build system.
Jesper
next prev parent reply other threads:[~2000-08-31 2:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-31 1:49 Andreas.Karlsson
2000-08-31 2:08 ` Jesper Skov [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-30 2:44 Andreas.Karlsson
2000-08-30 9:03 ` Jonathan Larmour
2000-08-31 1:22 ` Jesper Skov
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=14766.8350.892160.715784@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=Andreas.Karlsson@combitechsystems.com \
--cc=aeb@arm.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).