<html><head>
<style id="css_styles" type="text/css"><!--blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: right;'] { list-style-position: inside;}
body { font-family: Tahoma; font-size: 12pt; }--></style></head>
<body><div>Thanks for the advice.</div><div>The glue has already been used by me, including glue for the FPC-makefiles. And some glue for Lazarus.</div><div><br /></div><div>My question was more meant to be a fundamental one about the organization of code.</div><div>Embedded is now a very viable target for FPC.</div><div>MCU's become powerful enough to be easily used for FPC ( and OOP ).</div><div>This would mean more targets and a much wider public.</div><div><br /></div><div>The more targets added, the better.</div><div>But it could/should be better organized.</div><div>Making adding targets more easy. And strong typing (for peripherals) possible.</div><div><br /></div><div><br /></div>
<div>------ Origineel bericht ------</div>
<div>Van: "Michael Ring" <<a href="mailto:mail@michael-ring.org">mail@michael-ring.org</a>></div>
<div>Aan: <a href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</a></div>
<div>Verzonden: 7-9-2018 13:39:09</div>
<div>Onderwerp: Re: [fpc-devel] ARM embedded for ATSAM</div><div><br /></div>
<div id="xc29d395aff8b437" style="color: #000000"><blockquote cite="f8c22217-9f87-3d1b-e556-1205d9c91fb0@michael-ring.org" type="cite" class="cite2">
<p>definitions for microcontrollers are available in the
rtl/embedded/arm directory, there is one (sometimes several)
pascal file for a class of microcontrollers of one vendor.</p>
<p>There is some light glue in the compiler/arm/cpuinfo.pas and
systems/t_embed.pas directory to make a new microcontroller
available.</p>
<p>What I do is to auto-generate the main microcontroller file from
the header files of the microcontroller vendor.</p>
<p>On top of this you can then build your own library or extend pxl.</p>
<p><br />
</p>
<p>Michael</p>
</blockquote></div>
<style type="text/css"><!--#xc29d395aff8b437 #x99140e0c1d6a4e40a91fdb9ce47b12e0{
font-family:'Segoe UI';
font-size:12pt;
}
#xc29d395aff8b437 #x2edaf26808594c9ab09bf5a9bacf8cc1{
font-family:'Segoe UI';
font-size:12pt;
}
#xc29d395aff8b437 #xdd7be2969fb2492f940c0c10e0ff1c6b{
font-family:'Segoe UI';
font-size:12pt;
}
#xc29d395aff8b437 #xa8e42006782f4540a05bd685b14e35b2{
font-family:'Segoe UI';
font-size:12pt;
}
#xc29d395aff8b437 #xea798b92e0cf41ae81b06163a50020e8{
font-family:'Segoe UI';
font-size:12pt;
}
#xc29d395aff8b437 #xebf1bcb88d134ec7a43afb100f84807a{
font-family:'Segoe UI';
font-size:12pt;
}
#xc29d395aff8b437 #x550a2a54d1cb483085428ba56062d351{
font-family:'Segoe UI';
font-size:12pt;
}--></style><style type="text/css"><!--#xc29d395aff8b437 blockquote.cite{
margin-left:5px;
margin-right:0px;
padding-left:10px;
padding-right:0px;
border-left:1px solid #CCC ;
}
#xc29d395aff8b437 blockquote.cite2{
margin-left:5px;
margin-right:0px;
padding-left:10px;
padding-right:0px;
border-left:1px solid #CCC;
margin-top:3px;
padding-top:0px;
}
#xc29d395aff8b437 a img{
border:0px;
}
#xc29d395aff8b437 li#xc29d395aff8b437 [style="'text-align: center;'"],#xc29d395aff8b437 li#xc29d395aff8b437 [style="'text-align: right;'"]{
list-style-position:inside;
}
#xc29d395aff8b437{
font-family:Segoe UI;
font-size:12pt;
}--></style></body></html>