Akos Kiss
36479ddc1a
The 'external' toolchain file does nothing but transitively sets some cmake system variables from values received on the command line, and forcibly sets the C compiler. However, the same cmake system variables can be directly set via the command line, together with the C compiler, and specifying a toolchain is not a must. Thus, this patch drops the superfluous 'external' toolchain file and updates cmake-based targets to invoke cmake in a simpler form. Related changes in this commit: - While updating the cmake invocations, all the command line arguments have been reviewed and simplified (removed those, which did not change the defaults). - Removed unnecessary forced C compiler settings from some toolchain files (and/or changed them to setting the "compiler works" flag to true, thus keeping cmake's compiler identification logic but disabling some of its overzealous compiler sanity checks). JerryScript-DCO-1.0-Signed-off-by: Akos Kiss akiss@inf.u-szeged.hu
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