Dániel Bátyai
ac1c48eeff
Notable changes:
- Updated and the port API interface, new functions have been added
and some have been changed. The port library is now cleaned up to
not have any dependency on jerry-core, as it should be. The port library
is now strictly a collection of functions that implement
embedding/platform specific behavior.
- The default port implementation has been split for windows and unix.
Implemented port functions have been categorized and reorganized,
and marked with attribute((weak)) for better reusability.
- External context allocation has been moved to the port API instead
of a core API callback. The iterface has also been extended with a
function to free the allocated context. When external context is
enabled, jerry_init now automatically calls the port implementation
to allocate the context and jerry_cleanup automatically calls the port
to free the context.
- jerry_port_log has been changed to no longer require formatting to
be implemented by the port. The reason beind this is that it was vague what
format specifiers were used by the engine, and in what manner. The port
function now takes a zero-terminated string, and should only implement
how the string should be logged.
- Logging and log message formatting is now handled by the core jerry library
where it can be implemented as necessary. Logging can be done through a new
core API function, which uses the port to output the final log message.
- Log level has been moved into jerry-core, and an API function has
been added to set the log level. It should be the library that
filters log messages based on the requested log level, instead of
logging everything and requiring the user to do so.
- Module resolving logic has been moved into jerry-core. There's no
reason to have it in the port library and requiring embedders to
duplicate the code. It also added an unnecessary dependency on
jerry-core to the port. Platform specific behavior is still used through
the port API, like resolving module specifiers, and reading source file
contents. If necessary, the resolving logic can still be overridden as
previously.
- The jerry-ext library has also been cleaned up, and many utility
functions have been added that previously were implemented in
jerry-main. This allows easier reusability for some common operations,
like printing unhandled exceptions or providing a repl console.
- Debugger interaction with logged/printed messages has been fixed, so
that it's no longer the port implementations responsibility to send
the output to the debugger, as the port should have no notion of what a
debugger is. The printing and logging functions will now pass the
result message to the debugger, if connected.
- Cleaned up TZA handling in the date port implementation, and simplified
the API function prototype.
- Moved property access helper functions that use ASCII strings as
keys from jerry-ext to the core API.
JerryScript-DCO-1.0-Signed-off-by: Dániel Bátyai dbatyai@inf.u-szeged.hu
About
This folder contains files to run JerryScript on STM32F4-Discovery board with RIOT. The document had been validated on Ubuntu 20.04 operating system.
How to build
1. Setup the build environment for STM32F4-Discovery board
Clone the necessary projects into a jerry-riot directory.
The latest tested working version of RIOT is 2021.10.
# Create a base folder for all the projects.
mkdir jerry-riot && cd jerry-riot
git clone https://github.com/jerryscript-project/jerryscript.git
git clone https://github.com/RIOT-OS/RIOT.git -b 2021.10
2. Install dependencies of the projects
# Assuming you are in jerry-riot folder.
jerryscript/tools/apt-get-install-deps.sh
sudo apt install gcc-arm-none-eabi openocd minicom
The following directory structure has been created:
jerry-riot
+ jerryscript
| + targets
| + os
| + riot
+ RIOT
3. Build RIOT (with JerryScript)
# Assuming you are in jerry-riot folder.
make BOARD=stm32f4discovery -f jerryscript/targets/os/riot/Makefile
The created binary is a riot_jerryscript.elf named file located in jerryscript/build/riot-stm32f4/bin/ folder.
4. Flash the device
Connect Mini-USB for charging and flashing the device.
# Assuming you are in jerry-riot folder.
make BOARD=stm32f4discovery -f jerryscript/targets/os/riot/Makefile flash
Note: ST-LINK also can be used that is described at this page.
5. Connect to the device
Use USB To TTL Serial Converter for serial communication. STM32F4-Discovery pins are mapped by RIOT as follows:
STM32f4-Discovery PA2 pin is configured for TX.
STM32f4-Discovery PA3 pin is configured for RX.
- Connect
STM32f4-DiscoveryPA2 pin to RX pin ofUSB To TTL Serial Converter - Connect
STM32f4-DiscoveryPA3 pin to TX pin ofUSB To TTL Serial Converter - Connect
STM32f4-DiscoveryGND pin to GND pin ofUSB To TTL Serial Converter
The device should be visible as /dev/ttyUSB0. Use minicom communication program with 115200.
- In
minicom, setAdd Carriage Rettooffin byCTRL-A -> Z -> Ukey combinations. - In
minicom, setHardware Flow ControltonobyCTRL-A -> Z -> O -> Serial port setup -> Fkey combinations.
sudo minicom --device=/dev/ttyUSB0 --baud=115200
RIOT prompt looks like as follows:
main(): This is RIOT! (Version: 2021.10)
You are running RIOT on a(n) stm32f4discovery board.
This board features a(n) stm32 MCU.
>
You may have to press RESET on the board and press Enter key on the console several times to make RIOT prompt visible.
6. Run JerrySript
Type help to list shell commands:
> help
Command Description
---------------------------------------
test Jerryscript Hello World test
reboot Reboot the node
version Prints current RIOT_VERSION
pm interact with layered PM subsystem
Type test to execute JerryScript:
> test
This test run the following script code: [print ('Hello, World!');]
Hello, World!