summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Friesel <daniel.friesel@uos.de>2022-09-17 11:44:26 +0200
committerDaniel Friesel <daniel.friesel@uos.de>2022-09-17 11:44:26 +0200
commitdf0948fd219807bc271f874649519575ba5eefaa (patch)
treed794eb4520001331da8b9a24dd1f6503b0f0e41f
parent2501cd668a26bf6d4e9153f18a6e14695c4b5ed1 (diff)
README: update introduction
-rw-r--r--README.md24
1 files changed, 12 insertions, 12 deletions
diff --git a/README.md b/README.md
index b413ad5..6191088 100644
--- a/README.md
+++ b/README.md
@@ -1,17 +1,15 @@
# multipass - a multi-architecture library operating system
-**multipass** is a C++ Library Operating System for a few embedded
-architectures. As such, it does not provide multi-threading support or similar
-conveniences. Its objective is similar to the Arduino environment: provide a
-simple framework for embedded application/driver development and evaluation,
-and get out of the way as much as possible. It favors simplicity over
-performance and abstraction. Re-using components outside of multipass should
-be fairly easy.
-
-Application, architecture, and drivers are configured using `make config` (X11,
-kconfig-qconf) or `make nconfig` (Terminal, kconfig-nconf). Each application
-must implement `int main(void)` and do everything itself from that point on.
-When the loop feature is enabled, `void loop(void)` must be implemented also.
+**multipass** is a C++ Library Operating System for a few embedded architectures optimized for hardware evaluation and performance modeling.
+It does not provide multi-threading support or similar conveniences.
+Its objective is similar to the Arduino environment:
+provide a simple framework for embedded application/driver development and evaluation, and get out of the way as much as possible.
+It favors simplicity over performance and abstraction.
+Re-using components outside of multipass should be fairly easy.
+
+Application, architecture, and drivers are configured using `make config` (X11, kconfig-qconf) or `make nconfig` (Terminal, kconfig-nconf).
+Each application must implement `int main(void)` and do everything by itself from that point on.
+When the *loop* feature is enabled, `void loop(void)` must be implemented as well.
## Getting Started
@@ -55,6 +53,8 @@ Hardware features:
### MSP430FR5969, MSP430FR5994 (MSP430FR59xx Launchpad)
+Requires proprietary TI MSP430 GCC and MSP430Flasher.
+
Peripheral communication:
* I²C on eUSCI\_B0 (FR5969) / eUSCI\_B1 (FR5994) (master only, interrupt-driven)