SplitCode / Blog: Recent posts

The "Advanced" policy was relaxed a little bit and from that a "Convenient" policy was born.

"Convenient" policy freely allows editing of the whole content of files from ./Evolving/ folder, still keeping the advantage of no flashing requirement in between builds.
Mind this is opposed to a more restrictive "Advanced" policy even printf() strings from ./Evolving/ are ROMed so above property can be very useful. That bit of convenience has been traded for increase of RAM usage.... read more

I am struggling with untracking some files I have added to the index by mistake.
I didn't expect it is so easy to add a file to index and so difficult to remove it from there.

Related story.

My recent two commits were failed attempts to achieve only that!
Without the ability to remove files from index everything is going to complicate a lot.... read more

I have upgraded GNU ARM Eclipse plugin (1.8.1.20140218) and the new version comes with an OpenOCD Debugging Support (1.1.1) - a Debugging Configuration tailored for OpenOCD.

This Plug-In provides a "Restart Button" which makes whole build process even simpler and more seamless.

Instead of current "GDB Hardware Debugging" style:

1. Launch GDB
2. Program uC
3. debug
4. stop GDB
5. edit source
6. build
7. goto 1... read more

With [1b94560] push an Advanced Policy comes with a verbose build steps.
Now after modifying a source the build process informs about what has changed in *.ld layout since previous build (this is planned to be changed and compared against previous memory content, not previous build as not every build is programmed into memory).

From there it should be quite easy to provide a more descriptive way of what has been changed and why some modifications cause ROM content change (and impose time-consuming reflashing).... read more

I am currently trying to finish "Advanced" policy but the endeavor occurred really time-consuming. As for [c153580] it is functional, comes with following limitations:

• Only the content of ./Evolving and ./Stable is partitioned.
• Vague evolving symbols are not partitioned yet.
• no decent info on sizes of RAM and ROM sections yet.
• no explicit hints during build of why SplitCode performance degrades and uC requires reflashing.... read more

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

I do not know if SplitCode is a known solution 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). Both are also available in SplitCode, with the core of the SplitCode continuum spanning in between those.... read more