Update for 2021.06

Signed-off-by: David Abdurachmanov <[email protected]>

README.md

@@ -34,7 +34,7 @@ This needs to be done every time you want a clean setup based on the latest laye
 
 ```bash
 mkdir riscv-sifive && cd riscv-sifive
-repo init -u git://github.com/sifive/meta-sifive -b 2021.05 -m tools/manifests/sifive.xml
+repo init -u git://github.com/sifive/meta-sifive -b 2021.06 -m tools/manifests/sifive.xml
 repo sync
 ```
 
@@ -120,15 +120,17 @@ There are two disk image targets added by meta-sifive layer:
 
 By default disk images do not include debug packages. If you want to produce disk images with debug packages append `-debug` (e.g. `demo-coreip-cli-debug`) to the disk image target.
 
-There are two machine targets currently tested:
-
-- `qemuriscv64` - RISC-V 64-bit (RV64GC) for QEMU virt machine.
+There are several machine targets defined:
 
+- `qemuriscv64` - RISC-V 64-bit (RV64GC) for QEMU virt machine (**recommended for QEMU target**).
+- `qemuriscv64_b`- RISCV-V 64-bit (RV64GC) with B extension (not ratified yet) for QEMU virt machine.
+- `qemuriscv64_b_zfh` - RISC-V-64-bit (RV64GC) with B and Zfh extensions (both not ratified yet) for QEMU virt machine.
+- `qemuriscv64_v` - RISC-V 64-bit (RV64GC) with V extension (not ratified yet) for QEMU virt machine.
 - `freedom-u540` - SiFive HiFive Unleashed development board.
-
 - `unmatched` - SiFive HiFive Unmatched development board.
 
-> It's not possible to use disk images built for `freedom-u540` with QEMU 4.0 and instructions provided below.
+The QEMU machines with the additional extensions (i.e. beyond RV64GC) do not affect how packages or/and disk images are built. This means the toolchain might not provide support for the new extensions. By default packages are not built with the new instructions enabled.
+
 > 
 > Building disk images is CPU intensive, could require <10GB of sources downloaded over the Internet and <200GB of local storage.
 
@@ -255,6 +257,15 @@ resize2fs /dev/mmcblk0p4
 sync
 ```
 
+### Support TensorFlow Lite tflite_runtime Python library
+
+You can deploy your TensorFlow lite model by importing the Tensorflow Lite interpreter. There is a sample code `mnist.py` avaliable to demostrate how to deploy model and test MNIST hadwritten digits.
+
+```bash
+cd /usr/share/doc/python3-tensorflow-lite-demo/example
+python3 mnist.py
+```
+
 ## Contributions & Feedback
 
 If you want to file issues, send patches and make feature/enhancement requests use [meta-sifive](https://github.com/sifive/meta-sifive) or [freedom-u-sdk](https://github.com/sifive/freedom-u-sdk) repositories on GitHub.

ReleaseNotes/2021.06.md

@@ -0,0 +1,25 @@
+# Release Notes for 2021.06.00
+
+This release includes major changes compared previous Freedom U SDK (FUSDK). The main changes include:
+
+- Layers (`openembedded-core`, `meta-openemedded`, `meta-riscv`, `meta-clang`) were updated to their latest revisions.
+- `stress-ng` was updated to 0.12.10.
+- `mesa` was updated to 21.1.2.
+- `udev-extraconf` was removed.
+    + Issues were reported if the system was booted from microSD or NVMe, and USB storage device was auto-mounted. This resulted in random errors related to storage. Manual mounting works fine. This is a temporary removal until the issue can be understood.
+- Enabled `spell` PACKAGECONFIG for `mousepad` to avoid warnings at the build time.
+- `opensbi_0.9` from `openembedded-core` layer was added to BBMASK to avoid BitBake parsing issues.
+- New QEMU MACHINE targets were added (see below). These MACHINE options do not currently affect how packages or/and disk images are built. The toolchain might not provide support for these extensions yet. Currently this only allows to boot into QEMU virt machine with particular extensions (not ratified) enabled.
+    + `qemuriscv64_b` - RISCV-V 64-bit (RV64GC) with B extension (not ratified yet) for QEMU virt machine.
+    + `qemuriscv64_b_zfh`- RISC-V-64-bit (RV64GC) with B and Zfh extensions (both not ratified yet) for QEMU virt machine.
+    + `qemuriscv64_v`- RISC-V 64-bit (RV64GC) with V extension (not ratified yet) for QEMU virt machine.
+
+
+## Known Issues
+
+1. Newer OE/Yocto buildtools could cause build issues for `nspr-native` package. Use `-r yocto-3.2_M2 -t 20200729` as described in README file if you are using OE/Yocto buildtools. See Yocto bug [#14112](https://bugzilla.yoctoproject.org/show_bug.cgi?id=14112)
+2. We have found an issue with SanDisk "A2" microSD cards and thus do not recommend them.
+3. If the desktop is unresponsive/frozen (i.e. the keyboard doesn't work or/and the mouse doesn't work, the clock is not updating, etc.) try `systemctl restart display-manager` from the serial console.
+4. If the keyboard or/and mouse is not responsive/frozen check if the input device is available under `libinput list-devices` and if events are registered by `libinput debug-events` in the console. If events are registered try the command from #6 above otherwise manually unplug and plug the keyboard or/and mouse.
+5. If your desktop is very slow check Mesa OpenGL rendered (`glxinfo | grep OpenGL`). If it is `OpenGL renderer string: llvmpipe` restart the system. In rare cases Mesa might fallback to `llvmpipe`, but restart usually resolved the issue.
+6. Restart is not implemented in software for HiFive Unmatched.