Not much of a open source project if nothing is open source about ut, except for the use of an arduino :P
What about writing new code for the E1 and E2 boards?
I'd guess writing code in C would be easier then writing it in ASSEMBLY?
I've set up a programmer and built a interface-cable that goes directly into the original update-port of the eblade boards already.. The chips are code-protected though so not much usefull information to gather from them without doing some pretty invasive RE. Including acid and UV-lighting certain parts.
To view the assembly-debug info you could just run the firmware in IDA-Pro for instance..
There's no way of converting the Assembly-code back into a high-level programming-language though..
If er can get enough knowledgeable people on-board on a collaboration to develop either code for existing boards or or to write new from scratch or template, I'm in