From 121170109501ed6d8cf8b66b304834d7bc569133 Mon Sep 17 00:00:00 2001 From: Per Lindgren <per.lindgren@ltu.se> Date: Sun, 28 Feb 2021 20:03:29 +0100 Subject: [PATCH] added exercises --- CHANGELOG.md | 8 ++++---- README.md | 6 +++++- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e0ac539..90320ee 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,10 +2,10 @@ ## 2021-02-28 -- examples/bare2.rs, raw timer access. -- examples/bare3.rs, timing abstractions. -- examples/bare4.rs, a simple bare metal peripheral access API. -- examples/bare5.rs, write your own C-like peripheral access API. +- examples/rtic_bare2.rs, raw timer access. +- examples/rtic_bare3.rs, timing abstractions. +- examples/rtic_bare4.rs, a simple bare metal peripheral access API. +- examples/rtic_bare5.rs, write your own C-like peripheral access API. ## 2021-02-26 diff --git a/README.md b/README.md index 2e79586..803b502 100644 --- a/README.md +++ b/README.md @@ -79,7 +79,11 @@ Using `vscode` just press F5 to launch and debug the program in the currently ac Bare metal programming: -- `bare1.rs`, in this exercise you learn about debugging, inspecting the generated assembly code, inline assembly, and about checked vs. unchecked (wrapping) arithmetics. Provides essential skills and understanding of low level (bare metal) programming. +- `examples/rtic_bare1.rs`, in this exercise you learn about debugging, inspecting the generated assembly code, inline assembly, and about checked vs. unchecked (wrapping) arithmetics. Provides essential skills and understanding of low level (bare metal) programming. +- `examples/rtic_/bare2.rs`, in this exercise you learn how to measure execution time using raw timer access. +- `examples/rtic_bare3.rs`, here you learn more about RTIC timing semantics and timing abstractions. +- `examples/rtic_bare4.rs`, in this exercise you will encounter a simple bare metal peripheral access API. The API is very unsafe and easy to misuse. +- `examples/rtic_bare5.rs`, here you will write your own C-like peripheral access API. This API is much safer as you get control over bit-fields in a well defined way, thus less error prone. --- -- GitLab