From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: Documentation for .ldi file?
Date: Wed, 18 Sep 2013 16:51:00 -0000 [thread overview]
Message-ID: <l1clks$7cb$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1309170059210.18810@sg-laptop>
On 2013-09-16, Sergei Gavrikov <sergei.gavrikov@gmail.com> wrote:
> http://ecos.sourceware.org/docs-latest/user-guide/install-tree.html
> http://ecos.sourceware.org/docs-latest/user-guide/modifying-the-memory-layout.html
>
> MLT? http://ecos.sourceware.org/fom/ecos?_recurse=1&file=73#file_93
>
> Fortunately, we can dig a bit more, if we take a look on user guides for
> previous eCos releases, for example we can find MLT's look and feel
>
> http://ecos.sourceware.org/docs-1.3.1/guides/user-guides.7.html
Thanks for the pointers. I had forgotten there was supposed to be
some GUI memory layout tool that auto-generated stuff.
> By the way, cortexm.ld has USER_SECTION macro (arm.ld lacks)
>
> #define USER_SECTION(_name_, _region_, _vma_, _lma_) \
> ._name_ _vma_ : _lma_ \
> { __ ## _name_ ## _start = ABSOLUTE (.); \
> *(._name_*) \
> __ ## _name_ ## _end = ABSOLUTE (.); } \
> > _region_
>
> I must confess I have not used it. But, it seems this macro gives more
> freedom for .ldi designers.
That looks like what I needed. In the end, I just put some absolute
symbol assignments in my .ldi file to get the vector table located in
the right spot, while the "vectors" section contains only the
program's entry point. It's ugly, but it works. One day I'll have to
try to fix it so that I use a USER_SECTION for the vectors.
--
Grant Edwards grant.b.edwards Yow! ! I'm in a very
at clever and adorable INSANE
gmail.com ASYLUM!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-09-18 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 14:35 [ECOS] " Grant Edwards
2013-09-16 22:00 ` Sergei Gavrikov
2013-09-18 16:51 ` Grant Edwards [this message]
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='l1clks$7cb$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).