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
