Update docs to reflect pfalcon fork.

Author: peterhinch

README.md

@@ -19,18 +19,19 @@ This GitHub repository consists of the following parts:
  boards to communicate without using a UART. Primarily intended to enable a
  a Pyboard-like device to achieve bidirectional communication with an ESP8266.
 
-# 2. Installation of uasyncio
+# 2. Version and installation of uasyncio
 
-Firstly install the latest version of `micropython-uasyncio`. To use queues,
-also install the `micropython-uasyncio.queues` module. A `Lock` synchronisation
-primitive is provided by `micropython-uasyncio.synchro`.
+This has become more involved owing to the development of Paul Sokolovsky's
+fork. At the time of writing this fork supports `uasyncio` version 2.0, which
+requires the build of firmware from his repository. The version on PyPI is
+V2.0.
 
-Instructions on installing library modules may be found
-[here](https://github.com/micropython/micropython-lib).
+Until the situation becomes clearer I plan to support the official firmware.
+Hence these docs, code samples etc. are based on `uasyncio.core` V1.7.1 which
+is in [micropython-lib](https://github.com/micropython/micropython-lib).
 
-On networked hardware, upip may be run locally. The
-[tutorial](./TUTORIAL.md#installing-uasyncio-on-bare-metal) has instructions
-for methods of installation on non-networked baremetal targets.
+See [tutorial](./TUTORIAL.md#installing-uasyncio-on-bare-metal) for
+installation instructions.
 
 # 3. uasyncio development state
 

TUTORIAL.md

@@ -22,38 +22,22 @@ features.
 
 # Installing uasyncio on bare metal
 
-MicroPython libraries are located on [PyPi](https://pypi.python.org/pypi).
-Libraries to be installed are:
-
- * micropython-uasyncio
- * micropython-uasyncio.queues
- * micropython-uasyncio.synchro
-
-The `queues` and `synchro` modules are optional, but are required to run all
-the examples below.
-
-The oficial approach is to use the `upip` utility as described
-[here](https://github.com/micropython/micropython-lib). Network enabled
-hardware has this included in the firmware so it can be run locally. This is
-the preferred approach.
-
-On non-networked hardware there are two options. One is to use `upip` under a
-Linux real or virtual machine. This involves installing and building the Unix
-version of MicroPython, using `upip` to install to a directory on the PC, and
-then copying the library to the target.
-
-The need for Linux and the Unix build may be avoided by using
-[micropip.py](https://github.com/peterhinch/micropython-samples/tree/master/micropip).
-This runs under Python 3.2 or above. Create a temporary directory on your PC
-and install to that. Then copy the contents of the temporary direcory to the
-device. The following assume Linux and a temporary directory named `~/syn` -
-adapt to suit your OS. The first option requires that `micropip.py` has
-executable permission.
-
-```
-$ ./micropip.py install -p ~/syn micropython-uasyncio
-$ python3 -m micropip.py install -p ~/syn micropython-uasyncio
-```
+As discussed in the [main README](./README.md) these instructions assume the
+official build of MicroPython firmware. Accordingly the `uasyncio` files from
+the [official library](https://github.com/micropython/micropython-lib) are
+required. At the time of writing the PyPI repository contains `uasyncio` V2.0
+which is incompatible with that fimware so `upip` cannot be used.
+
+The aim is to create a `uasyncio` directory on the device's filesystem
+containing the following files:
+
+[__init__.py](https://github.com/micropython/micropython-lib/blob/master/uasyncio/uasyncio/__init__.py)  
+[core.py](https://github.com/micropython/micropython-lib/blob/master/uasyncio.core/uasyncio/core.py)  
+[queues.py](https://github.com/micropython/micropython-lib/blob/master/uasyncio.queues/uasyncio/queues.py)  
+[synchro.py](https://github.com/micropython/micropython-lib/blob/master/uasyncio.synchro/uasyncio/synchro.py)
+
+These modules may be frozen as bytecode in the usual way, by placing the above
+`uasyncio` directory in the port's `modules` directory and rebuilding.
 
 ###### [Main README](./README.md)