If you've got non-board-specific improvements then it'd be great if you were able to issue a PR for them though.
I noticed you'd pulled in some existing C drivers for the 2 sensors in the iTracker. When I've had to do stuff like that I've generally been using JS modules for the hardware (there is already one for the BME280), so I guess you might find it easier to do that for other ports (they won't be hardware-dependent - your existing drivers seem like they'll only work on nRF5x?).
I do have some code that'll build JS files directly into the firmware in a way that doesn't eat RAM, so hopefully that'll make its way into normal Espruino at some point in the future.
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.
Thanks!
If you've got non-board-specific improvements then it'd be great if you were able to issue a PR for them though.
I noticed you'd pulled in some existing C drivers for the 2 sensors in the iTracker. When I've had to do stuff like that I've generally been using JS modules for the hardware (there is already one for the BME280), so I guess you might find it easier to do that for other ports (they won't be hardware-dependent - your existing drivers seem like they'll only work on nRF5x?).
I do have some code that'll build JS files directly into the firmware in a way that doesn't eat RAM, so hopefully that'll make its way into normal Espruino at some point in the future.