Commit 5383a500 authored by Paul Sokolovsky's avatar Paul Sokolovsky
Browse files

zephyr/README: Update to require Zephyr 1.8.

There're a lot of changes and fixes in 1.8 regarding IP stack,
incompatible with previous Zephyr versions, so supporting them
doesn't make sense.

This is  the last commit which should build with Zephyr 1.7.
parent d57c6564
MicroPython port to Zephyr RTOS MicroPython port to Zephyr RTOS
=============================== ===============================
This is an initial port of MicroPython to Zephyr RTOS This is an work-in-progress port of MicroPython to Zephyr RTOS
(http://zephyrproject.org). (http://zephyrproject.org).
The port integrates well with Zephyr build system, using the latest This port requires Zephyr version 1.8 or higher. All boards supported
features which will be available in 1.6.0, and thus requires Zephyr by Zephyr (with standard level of features support, like UART console)
master to build against. All boards supported by Zephyr (with standard should work with MicroPython (but not all were tested).
level of feature support, like UART console) should work with
MicroPython (but not all were tested).
Features supported at this time: Features supported at this time:
* REPL (interactive prompt) over Zephyr UART console. * REPL (interactive prompt) over Zephyr UART console.
* `utime` module for time measurements and delays. * `utime` module for time measurements and delays.
* `machine.Pin` class for GPIO control. * `machine.Pin` class for GPIO control.
* `usocket` module for networking (IPv4/IPv6).
* "Frozen modules" support to allow to bundle Python modules together * "Frozen modules" support to allow to bundle Python modules together
with firmware. Including complete applications, including with with firmware. Including complete applications, including with
run-on-boot capability. run-on-boot capability.
...@@ -97,10 +96,10 @@ MicroPython is committed to maintain minimal binary size for Zephyr port ...@@ -97,10 +96,10 @@ MicroPython is committed to maintain minimal binary size for Zephyr port
below 128KB, as long as Zephyr project is committed to maintain stable below 128KB, as long as Zephyr project is committed to maintain stable
minimal size of their kernel (which they appear to be). Note that at such minimal size of their kernel (which they appear to be). Note that at such
size, there is no support for any Zephyr features beyond REPL over UART, size, there is no support for any Zephyr features beyond REPL over UART,
and only very minimal set of builtin Python modules. Thus, this build and only very minimal set of builtin Python modules is available. Thus,
is more suitable for code size control and quick demonstrations on this build is more suitable for code size control and quick demonstrations
smaller systems. It's also suitable for careful enabling of features one on smaller systems. It's also suitable for careful enabling of features
by one to achieve needed functionality and code size. This is in a one by one to achieve needed functionality and code size. This is in the
contrast to the "default" build, which may get more and more features contrast to the "default" build, which may get more and more features
enabled over time. enabled over time.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment