<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to My First Sourceforge Project</title><link>https://sourceforge.net/p/splitcode/blog/2014/01/my-first-sourceforge-project/</link><description>Recent changes to My First Sourceforge Project</description><atom:link href="https://sourceforge.net/p/splitcode/blog/2014/01/my-first-sourceforge-project/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 31 Jan 2014 01:30:07 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/splitcode/blog/2014/01/my-first-sourceforge-project/feed.rss" rel="self" type="application/rss+xml"/><item><title>My First Sourceforge Project discussion</title><link>https://sourceforge.net/p/splitcode/blog/2014/01/my-first-sourceforge-project/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I am currently trying to finish "Advanced" policy but the endeavor occurred really time-consuming. As for &lt;span&gt;[c153580]&lt;/span&gt; it is functional, comes with following limitations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Only the content of ./Evolving and ./Stable is partitioned.&lt;/li&gt;
&lt;li&gt;Vague evolving symbols are not partitioned yet.&lt;/li&gt;
&lt;li&gt;no decent info on sizes of RAM and ROM sections yet.&lt;/li&gt;
&lt;li&gt;no explicit hints during build of why SplitCode performance degrades and uC requires reflashing.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The core of the idea is functional and there are no limitations on which resource references which - SplitCode manages that part as expected.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brutte</dc:creator><pubDate>Fri, 31 Jan 2014 01:30:07 -0000</pubDate><guid>https://sourceforge.net4bea1196a141573f69a1ec033bb7360a52f429dd</guid></item><item><title>My First Sourceforge Project</title><link>https://sourceforge.net/p/splitcode/blog/2014/01/my-first-sourceforge-project/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have decided to make one of my ideas open source.&lt;/p&gt;
&lt;p&gt;I do not know if SplitCode is generic or not but I did try to find that out. All I have found is that the very ends of SplitCode idea are tangent to the "Link to SRAM" and "Link to Flash" build options available in some IDEs (like uVision, CoIDE or CodeWarrior). These two are also available in SplitCode, with the core of the SplitCode continuum spanning in between these.&lt;/p&gt;
&lt;p&gt;First, what has already been made and what the plan is:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;publish the basic, bulletproof project in a public git repository. One architecture, one toolchain, one vendor, one chip.&lt;/li&gt;
&lt;li&gt;design at least several policies for SplitCode. Currently there are only three, that is:&lt;ul&gt;
&lt;li&gt;"Link to SRAM"&lt;/li&gt;
&lt;li&gt;....(placeholder for other policies)&lt;/li&gt;
&lt;li&gt;the most stringent policy, laying just before "Link to Flash", I have not named yet.&lt;/li&gt;
&lt;li&gt;"Link to Flash"&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;make the policies as independent/reusable as possible (each architecture would have to have a separate set of policies but within architecture some common parts are possible).&lt;/li&gt;
&lt;li&gt;each policy has some underlying guidelines the end-user should follow. If some guideline is violated then the user has to be explicitly informed about that and why such violation decreases the development efficiency. This part is not completed.&lt;/li&gt;
&lt;li&gt;I would like the SplitCode project to become an integral part of &lt;a class="" href="https://sourceforge.net/projects/gnuarmeclipse/"&gt;GNU ARM Eclipse plug-in&lt;/a&gt; one day.&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brutte</dc:creator><pubDate>Fri, 17 Jan 2014 16:34:13 -0000</pubDate><guid>https://sourceforge.netdda29a0df2fae9eb8fd9dd77ede00be3c1da4a83</guid></item></channel></rss>