My First Sourceforge Project

I have decided to make one of my ideas open source.

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.

First, what has already been made and what the plan is:

• publish the basic, bulletproof project in a public git repository. One architecture, one toolchain, one vendor, one chip.
• design at least several policies for SplitCode. Currently there are only three, that is:
  • "Link to SRAM"
  • ....(placeholder for other policies)
  • the most stringent policy, laying just before "Link to Flash", I have not named yet.
  • "Link to Flash"
• 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).
• 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.
• I would like the SplitCode project to become an integral part of GNU ARM Eclipse plug-in one day.