As far as RAM, Espruino needs probably 1kB for static stuff (depending on what's included), then maybe 3kB for stack and the rest is variable storage. On the bigger boards I leave more for stack as it helps with recursion though.
I'm happy to help out where possible. There's some info on http://www.espruino.com/Internals and http://www.espruino.com/Performance as well as several posts on the forum from people asking about porting (a few are quite recent). I'm also doing a talk in October at Fullstack on the internals - which should be recorded, so I'll link to that when it's up.
However from what I can see on that GitHub, most of the hard work has already been done? It's probably just a bit of bugfixing/tweaking required?
Maybe WiFi isn't included in it yet, which would be the big one? However actually adding support requires very little knowledge of Espruino - you're just implementing this interface
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
As far as RAM, Espruino needs probably 1kB for static stuff (depending on what's included), then maybe 3kB for stack and the rest is variable storage. On the bigger boards I leave more for stack as it helps with recursion though.
I'm happy to help out where possible. There's some info on http://www.espruino.com/Internals and http://www.espruino.com/Performance as well as several posts on the forum from people asking about porting (a few are quite recent). I'm also doing a talk in October at Fullstack on the internals - which should be recorded, so I'll link to that when it's up.
However from what I can see on that GitHub, most of the hard work has already been done? It's probably just a bit of bugfixing/tweaking required?
Maybe WiFi isn't included in it yet, which would be the big one? However actually adding support requires very little knowledge of Espruino - you're just implementing this interface