summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2024-05-30software: communication: Use Go channelsxengineering
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
2024-05-30software: Switch back from .Log() to .Cat()xengineering
Logging the bytes is not really readable because of time stamp prefixes.
2024-05-30software: communication: Add SerialInterfacexengineering
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.
2024-05-30software: Implement serial port printoutxengineering
This validates that the code is able to get data from the serial port.
2024-05-30software: Implement serial port detectionxengineering
2024-05-28scripts: Add folder and generate.shxengineering
This allows generating Golang source code based on iot-protocol protobuf definitions.
2024-05-28software: Add folder and go.modxengineering
This folder will contain the Go software which runs on the iot-core device.
2024-05-28Add iot-protocol submodulexengineering
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.
2024-04-21firmware: Add 64 bit MAC to shell promptxengineering
This demonstrates that the readout of the 64 bit MAC address from the STM32WL55 microcontroller works and is useful to recognize used devices.
2024-04-20firmware: Customize shell promptxengineering
2024-04-13firmware: Add minimal Zephyr applicationxengineering
This is enough to validate that the firmware is running by using the Zephyr shell.
2024-04-13Add README with brief descriptionxengineering