This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ARM setup: How to load from flash?


[ ... ]



Tell gcc you don't want start files linked in. IIRC, it's
-nostartfiles.


I think what I *really* want is to keep the default routines in these files, but execute additional pieces of code *before* they are loaded (see below). It's probably not that much work to write a custom version of it all, though...

Or maybe I can combine -nostartfiles, some custom start code, and explicit link of the startup files in some clever way...





That's not the real reason, though. Actually, it's not even true that I'm "using" COFF. So far, I've just loaded plain binary files and simply started execution from the start of the image. These files are created using objcopy -b binary

That's "-O binary", of course.



------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]