_____ _ | __|___ ___ ___ _ _|_|___ ___ | __|_ -| . | _| | | | | . | |_____|___| _|_| |___|_|_|_|___| |_|
If you have an Espruino board, please read the Quick Start Guide first.
Other documentation of use is:
- The Forum
- Performance Notes
- Implementation Notes
- Build Process Notes
- Building Espruino
- Making your own libraries
- Hardware Debugging Notes
Support / Bugs
Submit bugs with clear steps to reproduce them: a small test case (not your whole program), and an actual and expected result. If you can't come up with these, please post on the forum first as it may just be something in your code that we can help out with.
Work on Espruino is supported by sales of our boards.
If your board isn't made by us but came pre-installed with Espruino then you should contact the manufacturers.
We try and support users of the boards we sell, but if you bought a non-official board your issue may not get addressed. In this case, please consider donating to help cover the time it takes to fix problems (even so, we can't guarantee to fix every problem).
Please see the LICENSE file
Check out the page on building Espruino
There are a bunch of tests in the
tests directory. See
tests/README.md for examples on how to run them.
While Espruino can run on other boards, we make no money from them and so cannot afford to test, fix or support the firmware on them. We're dependent on the community.
You can download binaries from http://www.espruino.com/Download (these aren't the latest, but are more likely to work with your board).
If you are a board manufacturer interested in getting your board officially supported, please Contact Us.
- Original Espruino Board - great support.
- Espruino Pico Board - great support.
- Puck.js - great support.
- Espruino WiFi Board - great support.
- Linux - WORKING
- BBC micro:bit - WORKING
- STM32VLDISCOVERY - WORKING - limited memory so some features removed
- STM32F3DISCOVERY - USB BROKEN
- STM32F4DISCOVERY - WORKING
- STM32F401CDISCOVERY - appears WORKING, but very little testing done
- STM32F429IDISCOVERY - WORKING over serial (A9/A10). No USB and no LCD support
- NRF51822 Development Kit - WORKING
- NRF52832 Development Kit - WORKING
- HY STM32 2.4" - WORKING
- HY STM32 2.8" - WORKING - limited memory so some features removed
- HY STM32 3.2" - WORKING
- Olimexino STM32 / Leaflabs Maple - WORKING - limited memory so some features removed
- Carambola - WORKING - GPIO via filesystem (no I2C)
- Raspberry Pi - WORKING - GPIO via filesystem or wiringPi (no I2C)
- Sony SmartWatch - NOT WORKING - USB VCP support for F2 still needed
- LC-TECH STM32F103RBT6 - WORKING, but with some issues (LED inverted logic, BTN needs pullup to work)
- ST NUCLEO-F401RE - WORKING
- ST NUCLEO-F411RE - WORKING
- ESP8266 - WORKING - Reasonably stable, but expect to find issues
- Arduino (AVR) - NOT POSSIBLE due to the Hardward architecture of AVRs, even though it would fit into an ATMEGA2560. If
avr-gccever gains an easy way to emulate Von Neumann architecture then it might be portable, but for now it isn't.
Check out the documentation on the build process first - this should clear up a lot of potential questions about the Espruino architecture.
Please see CONTRIBUTING.md for some hints about code style/etc.
You can auto-build documentation for all source files - see doxygen/README.md
Any more questions? ask on the forum.
Porting to new devices
If you're using an existing architecture everything can be done from
boards/BOARDNAME.py. See a similar board's
.py file as an example.
However for a new architecture there are a bunch of different files to modify.
boards/*.pyfiles describe the CPU, available pins, and connections - so the relevant linker script, headers + docs can be created
boards/pins/*.csvare copies of the 'pin definitions' table in the chip's datasheet. They are read in for STM32 chips by the
boards/*.pyfiles, but they are not required - see
boards/MICROBIT.pyfor an example.
- Global build options are handled in
makedirectory contains arch-specific Makefile fragments
- Extra libraries like USB/LCD/filesystem are in
- Processor-specific code in
- Processor-specific libs (like the SDK) in
src/jshardware.his effectively a simple abstraction layer for SPI/I2C/etc, which should be implemented in
- Create library functions (see examples in other jswrap files, also the comments in
See libs/README.md for a short tutorial on how to add your own libraries.
Using Espruino in your Projects
If you're using Espruino for your own personal projects - go ahead, we hope you have fun - and please let us know what you do with it on http://www.espruino.com/Forum!
If you're planning on selling the Espruino software on your own board, please:
- Let us know, we might be able to help.
- Read the terms of the MPLv2 Licence that Espruino is distributed under, and make sure you comply with it
- MPLv2 dictates that any files that you modify must be made available in source form. New files that you create don't need to be made available (although we'd encourage it!)
- You won't be able to call your board an 'Espruino' board unless it's agreed with us (we own the trademark)
- You must explain clearly in your documentation that your device uses Espruino internally
- Please don't fork Espruino - improvements get very hard to share, and in the long run everyone loses.
- Please give something back to the project - be it code improvements, documentation or support.
We spend a lot of time supporting Espruino on the forums, but can only do so because we make money from the sales of Espruino boards. If your users request support from us then we have absolutely no obligation to help them. However, we'll be a lot more motivated if you're actively helping to improve Espruino for all its users (not just your own).