Projects I like to mention
it would be nice to describe some of my interesting and exiting customer-projects as work references here,
but usually these work-contracts are confidential, so I can only mention that these were also related to my offered services and special skills [About] .
However, following are some own side projects I have been working on as well in the past (when time permitted).
Not everything was brought forward to a “final state” and is suitable for public release yet, but I regard this as “interesting fundamental groundwork”.
A lot might be suitable as “building-blocks” which I can also freely incorporate into contract work projects.
What I would also love to do in future, is to work on “crowd funded projects”, if you have some suggestion please let me know :)
The “EBS-HD62_DIY_PCB HW Project”
The “EBS-HD62_DIY_PCB” is a multimedia decoder board using the Fujitsu/Socionext MB8AL2030 (HD62) SOC.
See my “project notes” pdf-document Hd62PubProjNotes which I just recently composed for the public.
The schematics Schematics_Colored and Schematics_BW are also available here.
The “EBS APSOL-SW-Project”
APSOL generally stands for my “Advanced Primitive Solutions” (also registered as the web-site www.apsol.net ).
So the “EBS-APSOL SW Project” stands for 'Advanced Primitive (SW) Solutions' and offers a 'simple/minimalist' SW-environment
with drivers and application examples for easily realizing kind of 'primitive super-loop' application-programs.
Actually 'the catch' is that this “APSOL-SW environment” is supposed to easily compile and run also on various other embedded-system/MCU platforms.
Even allowing to kind of simulate/model/test such applications as PC-Programs running on a Windows- or Linux-PCs is possible.
See [EBS-APSOL_SW] for more details.
The “EBS Make-MAKE-Utility”
The document [EBS-Make-MAKE] describes 'for the curious' how the “EBS APSOL-SW-Project” is structured as a Directory-Tree
and how I use the widely used MAKE-Utility to compile my SW-Tree for various HW-Targets.
Since 'makefile'-s can be a quite complicated subject, actually what I do is to use relatively 'simply structured makefiles'
where basically the 'list of source-files', which 'belong together' and are compiled into a specific library are included from further include-files.
And actually these include-files are generated by my Make-MAKE-Utility.
The background is that, the source-files which are compiled into a library might be located at different sub-directories
(which is a bit tricky to describe using 'wildcards').
And, as reference-material provided to my customers, I can easily generate specific 'customer release SW-Trees'
with only those source-files out of 'my complete SW-Tree' which are actually needed in a customer-project.
So using my Make-MAKE-Utility I can simply 'generate' appropriate makefiles and not need any manual editing.
The customer will get a SW-Tree with 'primitive' makefiles for the case he likes (to modify or) to build the SW himself.
An an alternative, instead of generating 'make include-files' (thus not needing/using a MAKE-Utility at all)
my Make-MAKE-Utility can also generate *.bat (or Linux script files)
where the specified compiler/linker is called directly to build the SW-Tree, which might be even more practical in some cases.
The “EBS HtmlGen-ScriptUtility”
the utility used to create this web-site [EbsHtmlGen]
Regarding News and Change Notes
Instead of having a 'blog' I plan to frequently add interesting news to this web-site.
To easily check out what might have changed here since your last visit,
see my ChangeNotes and in case of interest also have a look at my External_Links .