-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with micro:bit v2 #2
Comments
This is now fixed in release 1.1.1. But I can't test it "for real" because of the Panic 927 that you've introduced. This Panic is descibed as "You are trying to use a feature designed for micro:bit V2 on a V1 board." which clearly doesn't match what this is. Please remove the Panic 927 for BitCommander |
Great, thanks for fixing! The list is managed by Microsoft, and I'm unable to change it. Please could you create an issue in |
Issue fixed - just waiing on Microsoft to remove from the fail list |
Issue fixed - just waiing on Microsoft to remove from the fail list |
The extension got disabled very quickly. But trying to get it re-enabled seems to take much longer :( |
Hi @4tronix ,
As you might have seen from microsoft/pxt-microbit#3506 this extension is currently not compiling against the latest version of Micro:bit CODAL. This means it will not work with micro:bit V2.
Software for micro:bit V2 boards is built using CODAL rather than the DAL, and no longer includes the mbed layer. We’ve implemented the most frequently used mbed classes to support easy porting of existing extensions, but there may still be corner cases with this compatibility layer.
As your extension is currently not building, it will be disabled for micro:bit V2. People attempting to use your extension with a micro:bit V2 board will get error 929. This extension will only be re-enabled on micro:bit V2 once it is fixed.
There are details on how to ensure extensions work on both version of the micro:bit here (lancaster-university/codal-microbit-v2#31).
Looking at your extension source I believe that your extension falls under this category:
The text was updated successfully, but these errors were encountered: