Tinymovr Firmware 2.3.1

What's Changed

• Make the scheduler state volatile by @eufrizz in #327
• Use checkboxes for bool values in Studio by @yconst in #333
• External Sensor support (prerelease) by @yconst in #338
• Enable adaptive updates in studio app by @yconst in #339
• Demote schedule reentrance error to warning by @yconst in #340
• Configurable sensor rate by @yconst in #341
• Fix manifest and tests by @yconst in #344
• GUI improvements by @yconst in #346
• Improve AMT22 reliability by @yconst in #348
• Refactor CAN bus infrastructure in Studio by @yconst in #350
• Add GUI console by @yconst in #347
• Studio/fix logging by @yconst in #352
• Add update rate and time window adjustments by @yconst in #353
• Improve error reporting for pole pair calibration by @yconst in #354
• Use shared ram for dfu setting by @yconst in #355
• Fix can initialization/setup by @yconst in #356
• Add motor resistance and inductance limitations table by @yconst in #357
• Fix transform derivation by @yconst in #358
• Use wildcards in manifest by @yconst in #359
• add flag for forcing device flashing by @yconst in #360
• add test cases by @yconst in #361
• Docs/add ma7xx figure by @yconst in #362
• Validate data written to nvm by @yconst in #363
• Pre CL checks by @yconst in #364
• Abnormal calibration voltage check by @yconst in #365
• Support for Tinymovr R53 by @yconst in #366

Full Changelog: 1.6.7...2.3.1

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:

1. 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.
2. 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 to Auto Program. This method is applicable to boards with the old bootloader.
3. 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.3.1 with this firmware release.
• Documentation for this release is available on Readthedocs in the develop branch

Tinymovr Firmware 2.3.0a1

What's Changed

• Pre Closed Loop checks by @yconst in #364
• Abnormal calibration voltage check by @yconst in #365

Full Changelog: 2.2.3a1...2.3.0a1

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:

1. 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.
2. 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 to Auto Program. This method is applicable to boards with the old bootloader.
3. 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.3.0a1 with this firmware pre-release.
• Documentation for this release is available on Readthedocs in the develop branch

Tinymovr Firmware 2.2.3a1

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:

1. 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.
2. 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 to Auto Program. This method is applicable to boards with the old bootloader.
3. 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

2.2.1a1

What's Changed

• Refactor CAN bus infrastructure in Studio by @yconst in #350
• (feat) Add GUI console by @yconst in #347
• (bug) Studio/fix logging by @yconst in #352
• (feat) Add update rate and time window adjustments by @yconst in #353
• (feat) Improve error reporting for pole pair calibration by @yconst in #354
• (bug) Use shared ram for dfu setting by @yconst in #355
• (bug) Fix can initialization/setup by @yconst in #356
• (docs) Add motor resistance and inductance limitations table by @yconst in #357
• (bug) Fix transform derivation by @yconst in #358

Full Changelog: 2.0.1a1...2.2.1a1

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:

1. 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.
2. 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 to Auto Program. This method is applicable to boards with the old bootloader.
3. 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.0.0a2 with this firmware pre-release.
• Documentation for this release is available on Readthedocs in the develop branch

Tinymovr Firmware 2.0.1a1

What's Changed

• GUI improvements by @yconst in #346
• Improve AMT22 reliability by @yconst in #348

Full Changelog: 2.0.0a2...2.0.1a1

Documentation for this release

Notes

(1) 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:

1. 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.
2. 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 to Auto Program. This method is applicable to boards with the old bootloader.
3. 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.0.0a2 with this firmware pre-release.
• Documentation for this release is available on Readthedocs in the develop branch

2.0.0a1

What's Changed

Features

• External Sensor support (1) (prerelease) by @yconst in #338

• Make heartbeat optional (reset upon restart)

• Configurable sensor rate by @yconst in #341

• Enable adaptive updates in studio app by @yconst in #339

• Use checkboxes for bool values in Studio by @yconst in #333

• Add raw sensor angle reporting 8e86d26

• Demote schedule reentrance error to warning by @yconst in #340

Docs

Add transform documentation and calibration instructions 1a43b34

• Add M5.2 pinouts by @yconst in #325
• Add pdf and epub builds fefef8e

Bug fixes

• Make the scheduler state volatile by @eufrizz in #327
• Fix protocol hash incompatibility in the latest release by @yconst in #326
• Fix length of returned version string 997d260
• Restore DWT counter. 7bed2fe

Full Changelog: 1.6.5...2.0.0a1

Documentation for this release

Notes

(1) 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:

1. 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.
2. 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 to Auto Program. This method is applicable to boards with the old bootloader.
3. 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.0.0a2 with this firmware pre-release.
• Documentation for this release is available on Readthedocs in the develop branch

Tinymovr Firmware 1.6.5

What's Changed

• Docs/change theme by @yconst in #319
• add m5.2 board version by @yconst in #320
• Update CAN ID docs by @yconst in #321
• Extended CAN ID hash by @yconst in #322
• update bootloader
• add version info to DFU mode
• improve function safety in DFU mode
• update DFU script
• add optional protocol hash check to every message in ext arbitration id
• fix trimmed version string
• improve DFU tests

Full Changelog: 1.6.4...1.6.5

Notes

• There are three methods for flashing:

1. 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.
2. 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 to Auto Program. This method is applicable to boards with the old bootloader.
3. 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 1.6.7 with this firmware release.

Tinymovr Firmware 1.6.2

What's Changed

• Improve angle sensor docs by @yconst in #290
• Misc fixes in docs by @yconst in #291
• Ensure copied directory name in docs by @yconst in #292
• Calibration Fixes by @yconst in #293
• Studio GUI timer improvements and bug fixes by @yconst in #295
• Add bus, channel and bitrate arguments to DFU util by @yconst in #297

Full Changelog: 1.6.0...1.6.2

Notes

• This release offers the option to upgrade the Tinymovr bootloader, along with the firmware, to support CAN bus DFU, but for existing boards this is only possible using JLink with the VSCode environment.
• As such there are two methods for flashing:
  1. 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 to Auto Program.
  2. 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 1.6.2 with this firmware release.

Tinymovr Firmware 1.6.0

What's Changed

• New CAN-based DFU mode by @yconst in #279

• DFU validation and recovery mode by @yconst in #287

• Add dialog for inputting function arguments by @yconst in #284

• Add remote JLink debug server flash/debug VSCode action by @yconst in #273

• User and technical documentation and devtools improvements by @yconst in #274

• Add models for all new hardware by @yconst in #270

• Update servo kit models and drawings by @yconst in #281

• Add M5 gimbal motor bracket model by @yconst in #275

• Improve docs for firmware upgrade, add DFU using CAN by @yconst in #285

• Docs hotfixes by @yconst in #283

• Version 1.6.0 by @yconst in #286

Full Changelog: 1.5.0...1.6.0

Notes

• This release offers the option to upgrade the Tinymovr bootloader, along with the firmware, to support CAN bus DFU, but for existing boards this is only possible using JLink with the VSCode environment.
• As such there are two methods for flashing:
  1. 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 to Auto Program.
  2. Via JLink & VSCode: This method enables comprehensive upgrade of both bootloader and firmware, but it requires specialized hardware (JLink) and hardware connections. After downloading the correct "release" firmware according to your board revision (R3.x, R5.x or M5.x), follow the instructions in our documentation.
• Please use Tinymovr Studio 1.6.0 with this firmware release.

Tinymovr Firmware v1.5.0

What's Changed

• Sensorless homing by @yconst in #259
• Cleanup legacy Eclipse files by @yconst in #261
• Add uart port warning by @yconst in #263
• Add M5 hardware info by @yconst in #264
• Fix bandwidth value for encoder observer and current control by @yconst in #265
• Support for Tinymovr R5.2 by @yconst in #267
• Update hardware diagrams by @yconst in #268

Full Changelog: 1.4.0...1.5.0

Notes

• When flashing this release with the ActiveFlashLight app, please select the Full Erase option, next to Auto Program, otherwise a verification error may occur.
• There are several versions of this firmware. Download the correct one according to your board revision (R3.2, R3.3, R5.x or M5.x).
• Do not download the "z_testbed_fw.bin" file. This is for internal testing purposes.
• Follow the bootloader flashing instructions in the documentation.
• Please use Tinymovr Studio 1.5.0 with this firmware release.