aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKlaus Goger <klaus.goger@theobroma-systems.com>2023-11-28 12:20:20 +0100
committerQuentin Schulz <quentin.schulz@theobroma-systems.com>2023-11-28 16:21:47 +0000
commit78b8c41cef467d76d7b19c305b554c219414e6d8 (patch)
tree8ce64de5c6809895c10c6d728eb686733a184454
parent79fa6994b8a1147f9d5507afc3ec00c8f22a8a34 (diff)
mule-attiny: bitbang_updi_reset: update README for meson
As we now have a meson build file we need to describe it in the README. Because we now have an install target remove the ./ prefix of the usage examples. Signed-off-by: Klaus Goger <klaus.goger@theobroma-systems.com>
-rw-r--r--mule-attiny/bitbang_updi_reset/README.md15
1 files changed, 12 insertions, 3 deletions
diff --git a/mule-attiny/bitbang_updi_reset/README.md b/mule-attiny/bitbang_updi_reset/README.md
index 7e2e28b..e94b033 100644
--- a/mule-attiny/bitbang_updi_reset/README.md
+++ b/mule-attiny/bitbang_updi_reset/README.md
@@ -14,20 +14,29 @@ when doing the hardware design.
This project depends on:
- `gcc`
+- `meson`
- `libgpiod`
# Compilation
```
-make build
+meson setup build
+meson compile -C build
```
The outcome is a binary executable called `updi_reset`.
+# Installation
+
+```
+meson install -C build
+```
+
+
# Running instructions
```
-nice --20 ./updi_reset <gpiochip_index> <gpio_index>
+nice --20 updi_reset <gpiochip_index> <gpio_index>
```
Since this is doing a GPIO bit-banging version of the UPDI reset, a GPIO needs
@@ -46,7 +55,7 @@ priority to increase the likelihood of timings to be precise enough. This can be
achieved by using `nice`:
```
-nice --20 ./updi_reset <gpiochip_index> <gpio_index>
+nice --20 updi_reset <gpiochip_index> <gpio_index>
```
# Notes