Skip to content
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 #11

Closed
microbit-sam opened this issue Nov 18, 2020 · 2 comments
Closed

Compatibility with micro:bit v2 #11

microbit-sam opened this issue Nov 18, 2020 · 2 comments

Comments

@microbit-sam
Copy link

Hi @bsiever ,

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:

  1. Use of mbed APIs that are not included in the compatibility layer, or microbit-dal APIs that need different constructors
/home/build/prjclone/pxtapp/microbit-pxt-timeanddate/timeanddate.cpp:61:28: error: 'us_ticker_read' was not declared in this scope
@bsiever
Copy link
Owner

bsiever commented Nov 19, 2020

Thanks @microbit-sam --- I believe my current fix/release will take care of the problem (I hope). Could you please confirm and, if resolved, close the issue here? (And if there are still problems could you post a follow up with some guidance?)

Thanks!

@bsiever
Copy link
Owner

bsiever commented Nov 21, 2020

I believe this is good-to-go (seems to compile in Beta anyway)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants