I'm hoping I'll be able to get compiled JS code running reliably in an IRQ. If I can do that then radio should get better even on the cheap modules... I do need to try some of the slightly better receivers though - they'd be really helpful.
sometimes I feel like @Gordon is obsessed with power consumption!
:) It's an excuse really. I feel there's a bit of 'competition' from small Linux-based devices, that undoubtedly have much faster V8-based JS implementations. I don't want to move out of the area where Espruino is really good, into an area where it looks bad compared to other devices :)
Software Serial
I've been thinking about this, but personally I haven't had a need for it so hadn't prioritised it. It shouldn't be too hard. I just made a bug for it, and I'll try and get around to it at some point.
What I wish is for LOTS of ram
Espruino was designed (with the JsVar blocks) so that it could use external RAM if needed, although I never actually went as far as making that happen. It shouldn't actually be too difficult to make a build of Espruino that would use external RAM - it'd obviously be slower when it had to drag stuff out of RAM, but when executing from its internal 'cache' it shouldn't suffer too big of a hit.
But for the moment, just doubling the available RAM seems like a good start - which could be done on existing chips by keeping the read-only data in flash memory (and out of RAM).
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.
I'm hoping I'll be able to get compiled JS code running reliably in an IRQ. If I can do that then radio should get better even on the cheap modules... I do need to try some of the slightly better receivers though - they'd be really helpful.
:) It's an excuse really. I feel there's a bit of 'competition' from small Linux-based devices, that undoubtedly have much faster V8-based JS implementations. I don't want to move out of the area where Espruino is really good, into an area where it looks bad compared to other devices :)
I've been thinking about this, but personally I haven't had a need for it so hadn't prioritised it. It shouldn't be too hard. I just made a bug for it, and I'll try and get around to it at some point.
Espruino was designed (with the JsVar blocks) so that it could use external RAM if needed, although I never actually went as far as making that happen. It shouldn't actually be too difficult to make a build of Espruino that would use external RAM - it'd obviously be slower when it had to drag stuff out of RAM, but when executing from its internal 'cache' it shouldn't suffer too big of a hit.
But for the moment, just doubling the available RAM seems like a good start - which could be done on existing chips by keeping the read-only data in flash memory (and out of RAM).