Tinymovr Firmware 2.2.3a1
Pre-release
Pre-release
What's Changed
- add flag for forcing device flashing by @yconst in #360
- add nvm test case by @yconst in #361
- Docs/add ma7xx figure by @yconst in #362
- Validate data written to nvm by @yconst in #363
Full Changelog: 2.2.2a1...2.2.3a1
Documentation for this release
Notes
External sensor support works for the M series boards only. The upcoming Tinymovr R5.3 will also support external sensors.
- There are three methods for flashing:
- Via Tinymovr DFU: After downloading the correct "upgrade" firmware according to your board revision (R3.x, R5.x or M5.x), connect your device to CAN bus as usual and follow the instructions in our documentation. This is available to boards with fw 1.6.0 or later, featuring the new bootloader.
- Via ActiveFlashLight: After downloading the correct "upgrade" firmware according to your board revision (R3.x, R5.x or M5.x), connect your device to ActiveFlashLight and follow the instructions in our documentation, selecting the
Full Erase
option, next toAuto Program
. This method is applicable to boards with the old bootloader. - Via JLink & VSCode: This method enables comprehensive upgrade of both bootloader and firmware, but it requires specialized hardware (JLink) and hardware connections. Follow the instructions in our documentation, observing correct hardware revision, and choosing the Release target.
- Please use Tinymovr Studio 2.2.3a1 with this firmware pre-release.
- Documentation for this release is available on Readthedocs in the develop branch