blob: c292eb586efffc444465f7dec2876948032933ce (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
# iot-contact
iot-contact is an IoT device to check if doors and windows are closed or open.
Furthermore roller shutter motors should be controlled.
Currently two boards are supported:
- `native_sim/native/64` without bootloader
- `nucleo_f767zi` with bootloader
## Usage
To build the firmware a firmware signing key is required. It is generated with
the `imgtool.py`.
```
mkdir -p ~/mcuboot
./imgtool.py keygen --key ~/mcuboot/key.pem --type ed25519
```
The content of this repository can be build with CMake and Ninja. The
application firmware will be built for the simulation board to easily use it
without special hardware.
The bootloader is built for `nucleo_f767zi` since the simulation board is
currently not supported.
```
cmake -Bbuild -GNinja -DKEY=~/mcuboot/key.pem
ninja -C build
```
To run the simulated firmware a virtual network interface `zeth` and a router
advertisement daemon have to be provided with an embedded script. Root rights
are required for that (prefix e.g. with `sudo`).
```
./fw/simulate-network.sh
```
With the firmware built and the network being prepared the simulated firmware
can be run.
```
./build/fw/zephyr/zephyr.exe
```
To build the firmware in a clean `nucleo` build folder, flash it and open a
serial interface another script can be used for convenience.
```
./fw/nucleo.sh
```
Next to the firmware artifacts the exported files related to the printed
circuit board (PCB) can be found in the build folder.
```
tree build/pcb
```
|
