| Age | Commit message (Collapse) | Author |
|---|
|
This transmits a frame via the Serial Line Internet Protocol (SLIP).
|
|
The term EUI-64 is more commonly known (see Wikipedia about MAC
addresses [1]). The term UID-64 was introduced because of ST
documentation.
[1]: https://en.wikipedia.org/wiki/MAC_address
|
|
The shell should not be used anyway since the USB UART port is required
for communication with the software.
Emitting 0xC0 as termination byte of the Serial Line Internet Protocol
(SLIP) every second triggers output in the SLIP-receiving software.
|
|
|
|
This implements to decode the Serial Line Internet Protocol (SLIP). It
splits the continuous byte stream into frames. Based on these frames the
rest of the data link layer and upper layers can be implemented.
|
|
|
|
|
|
Go channels help to decouple the communication layers defined by the OSI
model [1]. The physical layer can be abstracted by an RX and TX byte
channel and the data link layer by two frame channels.
[1]: https://en.wikipedia.org/wiki/OSI_model
|
|
Logging the bytes is not really readable because of time stamp prefixes.
|
|
This new type bundles the whole communication stack. This is easier to
use than handling types for each layer on the user side of the
communication package.
|
|
This validates that the code is able to get data from the serial port.
|
|
|
|
This allows generating Golang source code based on iot-protocol protobuf
definitions.
|
|
This folder will contain the Go software which runs on the iot-core
device.
|
|
This repository contains protocol definitions. Since every planned IoT
device should get its own repository it is useful to add a central
repository to define the interface between these devices.
|
|
This demonstrates that the readout of the 64 bit MAC address from the
STM32WL55 microcontroller works and is useful to recognize used devices.
|
|
|
|
This is enough to validate that the firmware is running by using the
Zephyr shell.
|
|
|
