AerospaceNU / AerospaceNU/stm32-avionics
Implement SW version and board serial number in radio, or otherwise uniquely identify boards
- Langage dominant
- C
- Étoiles
- 5
- Forks
- 0
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
In GitLab by @matthew.morley.ca on Mar 19, 2023, 12:25
Currently, both are hard coded to 0, which makes figuring out which FCB radio messages coming from hard.
STMs come with a hard coded 96 bit UID, we could hard code UID->SN associations?
We have git_info, we could hash the tag to generate a software version string? Or periodically send the full git describe output? I'm not convinced that the software version in every single radio message is _actually_ helpful unless we are making lots of breaking radio changes and keeping old FCBs around with out of date packet structures?
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Évaluation
Cette issue n'a pas encore été évaluée.