Files
jerryscript/targets/esp8266
Dániel Bátyai 9860d66a56 Rework the public API (#4829)
Related to #4186.

Some notable changes:
  - The term 'Error' now strictly refers to native Error objects defined in
    the ECMA standard, which are ordinary objects. All other uses of
    'error' or 'error reference' where the term refers to a thrown value is
    now called 'exception'.

  - Simplified the naming scheme of many String API functions. These functions
    will now also take an 'encoding' argument to specify the desired
    encoding in which to operate.

  - Removed the substring-copy-to-buffer functions. These functions
    behaved awkwardly, as they use character index to specify the
    start/end positions, and were mostly used incorrectly with byte
    offsets instead. The functionality can still be replicated with
    other functions if necessary.

  - String-to-buffer functions will no longer fail if the buffer is not
    sufficiently large, the string will instead be cropped.

  - Fixed the usage of the '_sz' prefix in many API functions. The term
    'sz' means zero-terminated string in hungarian notation, this was
    used incorrectly in many cases.

  - Renamed most of the public API functions to have shorter, more on-point
    names, rather than the often too long descriptive names. Functions are now
    also grouped by the type of value they operate on, where this makes
    sense.

JerryScript-DCO-1.0-Signed-off-by: Dániel Bátyai dbatyai@inf.u-szeged.hu
2021-12-06 10:20:09 +01:00
..
2021-12-06 10:20:09 +01:00
2016-01-14 07:27:18 +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_ATTR_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_ATTR_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