-
Notifications
You must be signed in to change notification settings - Fork 16
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 #4
Comments
@bennytheshap - Are you able to look at this ticket? |
If be happy to once I get one of the new boards. Jonny asked me to send over my address a while back. I did, but so far, no board. Nor have the boards I ordered from Sparkfun shipped... I'd love to get this working on the new hardware! |
@bennytheshap - We have been waiting for new hardware to arrive, it arrived on Friday. I'll pop a board in the post out to you today. |
Excellent. Thank you. |
@bennytheshap - Could you drop my your address at pauline@microbit.org please |
@bennytheshap - Hi Ben, did you receive your V2? I have a user on support with issues on BlockyTalky. Just wanted to check that you had received your board and have time to look at this issue? |
I have. Thank you. I've been swamped with other work, and haven't yet been able to work on this. But soon, I hope.
…On Mon, Feb 15, 2021, at 8:12 AM, microbit-pauline wrote:
@bennytheshap <https://github.com/bennytheshap> - Hi Ben, did you receive your V2? I have a user on support with issues on BlockyTalky. Just wanted to check that you had received your board and have time to look at this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA5ZSFGFYS4NE7NZU52GVTS7FBWJANCNFSM4T2BHF2A>.
|
@bennytheshap have you had a chance to look at the extension update? Had another person get in touch on micro:bit support requesting this. |
@bennytheshap any progression on the issue? |
@microbit-mark @microbit-pauline This has been a difficult year for me due to a combo of work and health stuff. I don't know when I'll be able to get to this. I'd gladly accept a PR. Or, alternatively, perhaps we could pair up to work on it together? |
Hi @bennytheshap, I am reviewing open support issues, do you happen to know if this issue was ever resolved? |
1 similar comment
Hi @bennytheshap, I am reviewing open support issues, do you happen to know if this issue was ever resolved? |
Hi @LaboratoryForPlayfulComputation,
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: