<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>I was missing something then ! Thanks. (It's usually the obvious things - staring me right in the face - that I miss)<br><br>Given that one controller unit file can be re-used amongst multiple controllers, that leaves a giant case() statement - which I can live with.<br><br>And, there is a 2 line patch to allow the compiler to compile to assembly - then use binutils to assemble and patch. This gives the flexibility to accommodate non-standard setups.<br><br>Expecting to provide a patch set in about a week to include a huge number of stellaris parts support.<br><br>John<br></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><font face="Tahoma" size="2"><hr
size="1"><b><span style="font-weight: bold;">From:</span></b> Florian Klämpfl <florian@freepascal.org><br><b><span style="font-weight: bold;">To:</span></b> FPC developers' list <fpc-devel@lists.freepascal.org><br><b><span style="font-weight: bold;">Sent:</span></b> Tue, August 16, 2011 2:46:06 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [fpc-devel] Stellaris Update<br></font><br>
Am 16.08.2011 12:24, schrieb John Clymer:<br>> Sorry, missed the second set of questions....<br>> <br>> I was able to get the stellaris part setup in t_embed.pas and<br>> cpuinfo.pas, then I got build errors when I build an executable - it was<br>> missing the Controller's startup file - these are in rtl\embedded\arm. <br>> Once FPC finishes compiling the program, it wants to link with a unit<br>> with the same name as the Controller. So, if each controller gets<br>> supported separately, then that folder is going to be chock full of<br>> controller specific startup files - most of which will be duplicates<br>> inside the same family.<br><br>This files are needed anyways to provide the declartions for hardware<br>access. Common declarations/startup code can be easily placed in<br>commonly used include files, and, see below.<br><br>> <br>> Unless I'm missing something, in order to get a binary for the
LM3S8962,<br>> using that specific controller as the target, I had to have a file in<br>> that folder with that same name - and with the unit inside named the<br>> same as the microcontroller.<br><br>This could be changed in the compiler, this is why we have<br>controllerunitstr and it proved to work well for me when working with LPCs.<br>_______________________________________________<br>fpc-devel maillist - <a ymailto="mailto:fpc-devel@lists.freepascal.org" href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</a><br><span><a target="_blank" href="http://lists.freepascal.org/mailman/listinfo/fpc-devel">http://lists.freepascal.org/mailman/listinfo/fpc-devel</a></span><br></div></div>
</div></body></html>