iot-core, branch mainCentral device for an Internet of Things networkhttps://cgit.xengineering.eu/iot-core/atom?h=main2024-06-01T10:48:44Zfirmware: Minimal frame encoding2024-06-01T10:48:44Zxengineeringme@xengineering.eu2024-06-01T10:48:44Zurn:sha1:7d7280a5b162800ef72d48a8a3d2afb4f0496b85
This only covers the correct frame size, setting the buffer to 0 and
copy the payload over.
Missing is:
- copy destination address
- copy source address
- set frame type
- calculate and add CRC32 checksum
firmware: Rename frame to payload2024-06-01T10:08:57Zxengineeringme@xengineering.eu2024-06-01T10:08:57Zurn:sha1:010cf768c20c71603172ae4c300ce3d571863141
This array does not really contain the whole frame.
firmware: Fix missing include guards2024-06-01T10:07:24Zxengineeringme@xengineering.eu2024-06-01T10:07:24Zurn:sha1:71f05dc68f31e01b01bbd47d1d7454719b19cce4firmware: Assert presence of EUI-64 MAC address2024-06-01T10:04:57Zxengineeringme@xengineering.eu2024-06-01T09:17:50Zurn:sha1:df38994a4a784cc7b794c3f2a3c7f08172ef51ad
Without that address comunication is not possible.
firmware: Separate data link related code2024-06-01T08:25:12Zxengineeringme@xengineering.eu2024-05-31T08:33:56Zurn:sha1:ff3fa235236f2d6d92f7869fb4f55e3655b0502afirmware: Add end and escape byte to UART output2024-05-31T08:09:55Zxengineeringme@xengineering.eu2024-05-31T08:09:55Zurn:sha1:bb029aacf08983ad6c1a6360d988e89394fc4d85
These special bytes of the Serial Line Internet Protocol are contained
inside the payload to validate that the escaping is working correctly.
software: Fix unslip() implementation and test2024-05-31T08:04:51Zxengineeringme@xengineering.eu2024-05-30T20:55:52Zurn:sha1:a3cbf0dd580a5bc51c4cfccbdf69be5fff23303a
Both the implementation and the unit test had bugs which were blocking
the test execution forever. This is fixed with this commit. Furthermore
the new unslip() implementation is refactored and more readable.
software: Add protobuf dependency2024-05-31T07:41:17Zxengineeringme@xengineering.eu2024-05-31T07:39:31Zurn:sha1:41072be6c6af48f3066daf60552eba5191bfad7d
This was not present because the Go tool detects this dependency only in
the case of the generated discovery package. This package was not
present during the last `go mod tidy` and `go mod vendor` cycle.
software: Refactor unit test for unslip()2024-05-30T20:53:58Zxengineeringme@xengineering.eu2024-05-30T20:53:37Zurn:sha1:9a1f97a671d80df29c309b3aae8ad66755bef42f
This allows to easily add test cases.
firmware: Implement send_frame()2024-05-30T20:45:41Zxengineeringme@xengineering.eu2024-05-30T20:45:41Zurn:sha1:b1206aaa1f6bc4a04509149024402dea9da12e27
This transmits a frame via the Serial Line Internet Protocol (SLIP).
firmware: Rename from uid64 to eui642024-05-30T20:12:34Zxengineeringme@xengineering.eu2024-05-30T20:06:31Zurn:sha1:b8147bcba2e8dfef419ba14053285bc9750dc319
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
firmware: Replace shell by empty frame emitting2024-05-30T18:42:20Zxengineeringme@xengineering.eu2024-05-30T18:42:20Zurn:sha1:17008662c08e8e99aefc1814dd80d366872d7ded
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.
firmware: Fix missing imports2024-05-30T18:20:30Zxengineeringme@xengineering.eu2024-05-30T18:08:09Zurn:sha1:d9c7e352d9268e12f6c1d19dbc68c047842acdf1software: communication: Implement unslip()2024-05-30T18:06:23Zxengineeringme@xengineering.eu2024-05-30T18:00:44Zurn:sha1:922d2a0cbd1406c0b437c0a062a8c04129d7dda4
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.
software: communication: Make receive private2024-05-30T18:06:23Zxengineeringme@xengineering.eu2024-05-30T16:33:51Zurn:sha1:85dc84ab0e8f5bf2fc02ad8881c7a7247bdb492bsoftware: communication: Split setup and start2024-05-30T18:06:16Zxengineeringme@xengineering.eu2024-05-30T16:21:27Zurn:sha1:a4705ffdb76d412bbc3999877843f886cbd41f4csoftware: communication: Use Go channels2024-05-30T15:37:44Zxengineeringme@xengineering.eu2024-05-30T15:37:44Zurn:sha1:0f62b35cb1a1ff69e8c29285322a251010cf5ee1
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
software: Switch back from .Log() to .Cat()2024-05-30T15:10:08Zxengineeringme@xengineering.eu2024-05-30T15:10:08Zurn:sha1:034c8209f6e6f17bf5b6f265e2a3ef58f05b2c80
Logging the bytes is not really readable because of time stamp prefixes.
software: communication: Add SerialInterface2024-05-30T14:48:39Zxengineeringme@xengineering.eu2024-05-30T14:47:29Zurn:sha1:96d159114af675d55fe0d7c0f22a69d65e9563fc
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.
software: Implement serial port printout2024-05-30T14:13:04Zxengineeringme@xengineering.eu2024-05-30T14:13:04Zurn:sha1:0cfd378394b6c5d90e00c217b12113e0c3284031
This validates that the code is able to get data from the serial port.
software: Implement serial port detection2024-05-30T14:00:32Zxengineeringme@xengineering.eu2024-05-30T14:00:32Zurn:sha1:b8ef4d11fe0d00ce0884ccf982675845b20c3ce9scripts: Add folder and generate.sh2024-05-28T18:28:46Zxengineeringme@xengineering.eu2024-05-28T17:35:35Zurn:sha1:eab833271eeaa8d54991c11eccec9445f662a191
This allows generating Golang source code based on iot-protocol protobuf
definitions.
software: Add folder and go.mod2024-05-28T17:12:44Zxengineeringme@xengineering.eu2024-05-28T17:12:44Zurn:sha1:e6b74069e18736e6f2d3acb14c18013a7bd4c464
This folder will contain the Go software which runs on the iot-core
device.
Add iot-protocol submodule2024-05-28T17:07:12Zxengineeringme@xengineering.eu2024-05-28T17:07:12Zurn:sha1:313abb1513db61e82ecb5354f4c5918133c13b48
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.
firmware: Add 64 bit MAC to shell prompt2024-04-21T10:26:00Zxengineeringme@xengineering.eu2024-04-20T20:08:08Zurn:sha1:96f2358caadfd55d6fd3b888ef5d21f22fc2439c
This demonstrates that the readout of the 64 bit MAC address from the
STM32WL55 microcontroller works and is useful to recognize used devices.
firmware: Customize shell prompt2024-04-20T20:04:41Zxengineeringme@xengineering.eu2024-04-20T20:04:41Zurn:sha1:9a713b06c3f776684dd026646c916b6daea7b25bfirmware: Add minimal Zephyr application2024-04-13T19:21:54Zxengineeringme@xengineering.eu2024-04-13T19:21:54Zurn:sha1:fedaacedd29b4b61fc138e381aad2cf4be08f31d
This is enough to validate that the firmware is running by using the
Zephyr shell.
Add README with brief description2024-04-13T18:47:30Zxengineeringme@xengineering.eu2024-04-13T18:47:30Zurn:sha1:31bdbcf1a38f0d513ca3327441432a281a5ce6d8