Uploaded May 2020 | Updated September 2026, 1 week ago
When developing your project in multiple installations or across multiple boards, its always useful to be able to tell what version on-board ties up with which code build. Links and More Information below....
We have all lost track of which firmware is on which board, and what changes were in it, often leading to a lot of wasted time and confusion...
Using a few simple techniques you can embed the date / time, as well as any other externally generated information, directly into your project at build time, every time. This also allows your Version Controlled Check-ins to be tied up quickly with running firmware, saving your time and energy when trying to identify a fix, or if it has already been fixed.
This works with any Version Control System, and some tools provide additional Command Line tools which are perfect for this purpose, when combined with the build.hooks available. (e.g. Tortoise Git uses GitWCRev can be used to generate more detailed information)
Don't forget to Like and Subscribe to stay up to date with new videos and feature updates...
Our Website:
visualmicro.com
Project Used in this Example:
visualmicro.com/downloads/VerifiableBoardFirmware.zip
Arduino Build Hooks:
arduino.github.io/arduino-cli/platform-specification/#pre-and-post-build-hooks-since-arduino-ide-165
#Arduino #VisualStudio
When developing your project in multiple installations or across multiple boards, its always useful to be able to tell what version on-board ties up with which code build. Links and More Information below....
We have all lost track of which firmware is on which board, and what changes were in it, often leading to a lot of wasted time and confusion...
Using a few simple techniques you can embed the date / time, as well as any other externally generated information, directly into your project at build time, every time. This also allows your Version Controlled Check-ins to be tied up quickly with running firmware, saving your time and energy when trying to identify a fix, or if it has already been fixed.
This works with any Version Control System, and some tools provide additional Command Line tools which are perfect for this purpose, when combined with the build.hooks available. (e.g. Tortoise Git uses GitWCRev can be used to generate more detailed information)
Don't forget to Like and Subscribe to stay up to date with new videos and feature updates...
Our Website:
visualmicro.com
Project Used in this Example:
visualmicro.com/downloads/VerifiableBoardFirmware.zip
Arduino Build Hooks:
arduino.github.io/arduino-cli/platform-specification/#pre-and-post-build-hooks-since-arduino-ide-165
#Arduino #VisualStudio
