Apply a few updates to README
@@ -10,16 +10,13 @@ easy software upgrade.
MCUboot is operating system and hardware independent, and relies on
hardware porting layers from the operating system it works with. Currently
mcuboot works with both the Apache Mynewt, and Zephyr operating systems, but
-more ports are planned in the future.
+more ports are planned in the future. RIOT is currently supported as a boot
+target with complete port arriving in the near future.
## Roadmap
-The MCUBoot project was originally taken from the Apache Mynewt operating system,
-which had secure boot and software upgrade functionality instrinsic to it. Currently
-development is heads down on a first release of MCUboot that works across both the
-Zephyr operating system and Apache Mynewt operating system.
-
-For more information on what's being planned, and worked on, please visit:
+The issues being planned and worked on are tracked on Jira. To participate
+please visit:
https://runtimeco.atlassian.net/projects/MCUB/summary
@@ -34,6 +31,7 @@ For more information in the source, here are some pointers:
- [boot/bootutil](https://github.com/runtimeco/mcuboot/tree/master/boot/bootutil): The core of the bootloader itself.
- [boot/boot\_serial](https://github.com/runtimeco/mcuboot/tree/master/boot/boot_serial): Support for serial upgrade within the bootloader itself.
- [boot/zephyr](https://github.com/runtimeco/mcuboot/tree/master/boot/zephyr): Port of the bootloader to Zephyr
+- [boot/mynewt](https://github.com/runtimeco/mcuboot/tree/master/boot/mynewt): Mynewt bootloader app
- [imgtool](https://github.com/runtimeco/mcuboot/tree/master/imgtool): A tool to securely sign firmware images for booting by mcuboot.
- [sim](https://github.com/runtimeco/mcuboot/tree/master/sim): A bootloader simulator for testing and regression
