Akos Kiss 9ced3addaa Bump ESP8266 target to SDK v2.1.0 (#2697)
Until now, the ESP8266 target used a non-tagged git hash revision
of the RTOS SDK (from Oct 2017). Moreover, the compiler was also a
custom-built gcc.

This commit sets the RTOS SDK version to v2.1.0, released Oct 2018,
which is the latest old-style SDK for ESP. The commit also changes
the used gcc to an Espressif-provided pre-built toolchain, which is
tagged for the (latest) v3.0.1 SDK release.

(The SDK bump is not to the latest SDK version because the new
v3.x line of the SDK is "ESP-IDF style", which is incompatible with
the current target code base. On the other hand, the toolchain
comes from the latest SDK release because the v2.x line had no
pre-built toolchain suggestions -- but it builds v2.x sources
correctly.)

JerryScript-DCO-1.0-Signed-off-by: Akos Kiss akiss@inf.u-szeged.hu
2019-01-15 08:35:39 +01:00
..
2016-01-14 07:27:18 +09:00
2017-11-08 19:13:34 +09:00

About

Files in this folder (targets/esp8266) are copied from examples/project_template of esp_iot_rtos_sdk and modified for JerryScript. You can view online from this page.

How to build JerryScript for ESP8266

1. SDK

Follow this page to setup build environment

2. Building JerryScript

# assume you are in jerryscript folder
make -f ./targets/esp8266/Makefile.esp8266

Output files should be placed at $BIN_PATH

3. Flashing for ESP8266 12E

Follow this page to get details about this board.

make -f ./targets/esp8266/Makefile.esp8266 flash

Default USB device is /dev/ttyUSB0. If you have different one, give with USBDEVICE, like;

USBDEVICE=/dev/ttyUSB1 make -f ./targets/esp8266/Makefile.esp8266 flash

4. Running

  • power off
  • connect GPIO2 with serial of 470 Ohm + LED and to GND
  • power On

LED should blink on and off every second

5. Cleaning

To clean the build result:

make -f ./targets/esp8266/Makefile.esp8266 clean

To clean the board's flash memory:

make -f ./targets/esp8266/Makefile.esp8266 erase_flash

6. Optimizing initial RAM usage (ESP8266 specific)

The existing open source gcc compiler with Xtensa support stores const(ants) in the same limited RAM where our code needs to run.

It is possible to force the compiler to store a constant into ROM and also read it from there thus saving RAM. The only requirement is to add JERRY_CONST_DATA attribute to your constant.

For example:

static const lit_magic_size_t lit_magic_string_sizes[] =

can be modified to

static const lit_magic_size_t lit_magic_string_sizes[] JERRY_CONST_DATA =

That is already done to some constants in jerry-core. E.g.:

  • vm_decode_table
  • ecma_property_hashmap_steps
  • lit_magic_string_sizes
  • unicode_letter_interv_sps
  • unicode_letter_interv_len
  • unicode_non_letter_ident_
  • unicode_letter_chars