Use DAPLink vendor command for serial#103
Merged
Merged
Conversation
In Brave we can fail to parse the serial and therefore to tell the board version (it anonomises the device serial number) and we need this information to flash the correct hex. This matches MakeCode's approach. I confirmed that identical serials are found in Chrome for V1 and V2 via this and the old method. I don't think the fallback should come into play but leaving it for now. This feature has been in DAPLink since WebUSB support has been in DAPLink. Tweak format command to be less verbose.
microbit-matt-hillsdon
force-pushed
the
use-daplink-serial
branch
from
March 3, 2026 10:53
c28eedc to
f053460
Compare
Deploying microbit-connection with
|
| Latest commit: |
f053460
|
| Status: | 🚫 Build failed. |
Contributor
Author
|
Confirmed I can connect in Brave (on Mac, but that repro'd it before) with all settings reset to defaults. |
microbit-matt-hillsdon
added a commit
to microbit-foundation/python-editor-v3
that referenced
this pull request
Apr 29, 2026
This contains the pre-1.0 breaking API changes and USB serial re-work. We'll run this on Python beta for a bit to build confidence as the BLE code has had far more real use than the USB changes. This should improve serial issues after first physical connection + flash and extra serial from previous programs leaking into subsequent ones. Relevant fixes: - Workaround for the bad response issue - microbit-foundation/microbit-connection#72 - Use DAPLink vendor command for serial number - microbit-foundation/microbit-connection#103 - Inline CMSIS-DAP code, fix and test serial issues - microbit-foundation/microbit-connection#110 - Fix UICR not updated during WebUSB partial flashing - microbit-foundation/microbit-connection#113
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In Brave we can fail to parse the serial and therefore to tell the board version (it anonomises the device serial number) and we need this information to flash the correct hex.
This matches MakeCode's approach.
I confirmed that identical serials are found in Chrome for V1 and V2 via this and the old method.
I don't think the fallback should come into play but leaving it for now. This feature has been in DAPLink since WebUSB support has been in DAPLink.
See #57