From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Documentation for .ldi file?
Date: Mon, 16 Sep 2013 14:35:00 -0000 [thread overview]
Message-ID: <l174uv$sq2$1@ger.gmane.org> (raw)
Can somebody please point me to the documentation for writing a .ldi
file? I'm trying figure out how to
1) Add a new section that's always at the beginning of the binary
image which contains the image entry point.
2) Set the location of the Cortex-M3 interrupt table -- which is
neither at the beginning of the program image, nor does it
contain the image entry point. Is hal_vsr_table the only symbol
I need to worry about defing to determine the location of the
M3's VTOR table?
Why the multiple layers of obfuscation when just writing a gnu linker
script would be so much easier?
I get the impression that somehow all these layers were supposed to
allow people who know nothing about hardware, the Gnu toolchain or
embedded systems development do embedded systems development?
AFAICT, it backfired and just makes it that much harder to create a
port and figure out what's wrong when something doesn't work.
--
Grant Edwards grant.b.edwards Yow! I'm gliding over a
at NUCLEAR WASTE DUMP near
gmail.com ATLANTA, Georgia!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2013-09-16 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 14:35 Grant Edwards [this message]
2013-09-16 22:00 ` Sergei Gavrikov
2013-09-18 16:51 ` [ECOS] " Grant 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='l174uv$sq2$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).