Arduino Alvik / Compatibility
Arduino Alvik MicroPython compatibility: the version pair that matters
“Supports MicroPython” is not enough information when the host library and robot-side firmware move independently. Alvik gives us a concrete example of why robot compatibility should be recorded as a version tuple.
At a glance
Key details
Why the pair matters
A library update can add commands or assumptions that older carrier firmware does not understand. Updating only one side can therefore produce a problem that looks like broken hardware even when the robot itself is fine.
Record the known-working pair before changing either component. It gives you a rollback target and makes troubleshooting much less speculative.
A safer update routine
Treat the library and carrier firmware as one compatibility unit. Check the release notes for both, update deliberately, and test one small movement or sensor example before changing anything else.
- Write down the currently working library and carrier versions.
- Change one layer at a time where possible.
- Re-test a small known-good example before moving back to your main project.
Related
Sources