diff options
| -rw-r--r-- | Makefile | 9 | ||||
| -rw-r--r-- | README | 22 |
2 files changed, 30 insertions, 1 deletions
@@ -1,6 +1,6 @@ BOARD ?= -.PHONY: check jerryscript micropython +.PHONY: check jerryscript micropython zephyr.js help: @echo "make <target> BOARD=<board>" @@ -17,6 +17,13 @@ micropython: check $(MAKE) -C micropython/zephyr BOARD=$(BOARD) cp micropython/zephyr/outdir/$(BOARD)/zephyr.bin micropython-$(BOARD).bin +zephyr.js: check + @if [ -z "$$ZJS_BASE" ]; then echo "You must use zmake-z.js <targets> BOARD=<board> to build Zephyr.js"; false; fi + # Workaround for some Kconfig problem + $(MAKE) -C zephyr.js/deps/zephyr mrproper + $(MAKE) -C zephyr.js BOARD=$(BOARD) + cp zephyr.js/outdir/$(BOARD)/zephyr.bin zephyr.js-$(BOARD).bin + clean: check $(MAKE) -C jerryscript -f ./targets/zephyr/Makefile.zephyr clean BOARD=$(BOARD) @@ -74,3 +74,25 @@ GPIO and timing, i.e. all needed to blink an LED. For example code and instructions on blinking, follow https://github.com/micropython/micropython/tree/master/zephyr#quick-example (the code there needs to be updated for LED GPIO as used by your board!) + + +Zephyr.js +--------- + +Zephyr.js currently officially supports only 2 boards: arduino_101 (x86) +and frdm_k64f. It various places, it so far hardcodes support for these +2 boards and bundles its own Zephyr snapshot, so building for other boards +is complicated (and has a good chance to fail still). This is known issue +and work is ongoing to improve the situation (but no specific ETA). + +Build with: + + make micropython BOARD=frdm_k64f + +The result is in the top-level directory, file + + zephyr.js-<board>.bin + +Default Zephyr.js mode of operation is no interactive mode, a JavaScript +application is bundled into the firmware binary. Steps above use default +"hello world" application, which prints a message to the console. |