You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// The micro:bit board version can be determined from the USB device serial number.
// See https://support.microbit.org/support/solutions/articles/19000084312-micro-bit-motion-sensor-hardware-changes-for-editor-developers
varid=usbSerialNumber.slice(0,4);
if('9900'==id)return'1.3';
if('9901'==id)return'1.5';
if('9903'==id)return'2.0';
if('9904'==id)return'2.0';
return'unrecognized board';
}
We also need to fix the Firmware Version reported by the firmware programme, as the DAL_VERSION macro does not get a valid version number in CODAL (lancaster-university/codal-microbit-v2#138):
send2Bytes(major, minor); // firmware version (vs. Firmata protocol version)
sendStringData((constchar *) s);
sendByte(SYSEX_END);
}
The "Board Version" property is only provided from the JS firmware library, which uses the USB ID to identify the board. @JohnVidler we should consider if we also want to provide that info from the micro:bit firmata programme, as it could be included (only as V1 or V2, no need to query DAPLink to identify V2.0 or V2.2) in the "Firmware Version" string form.
The text was updated successfully, but these errors were encountered:
There is already a "Board Version" property in the JS side that is used to identify the board, but needs be updated for V2.2 support anyway:
microbit-firmata/firmataClient.md
Lines 26 to 30 in 3b057a8
microbit-firmata/client/MBFirmataClient.js
Line 200 in 3b057a8
microbit-firmata/client/MBFirmataClient.js
Lines 231 to 240 in 3b057a8
We also need to fix the Firmware Version reported by the firmware programme, as the
DAL_VERSION
macro does not get a valid version number in CODAL (lancaster-university/codal-microbit-v2#138):microbit-firmata/firmware/source/mbFirmata.cpp
Lines 310 to 330 in 3b057a8
The "Board Version" property is only provided from the JS firmware library, which uses the USB ID to identify the board.
@JohnVidler we should consider if we also want to provide that info from the micro:bit firmata programme, as it could be included (only as V1 or V2, no need to query DAPLink to identify V2.0 or V2.2) in the "Firmware Version" string form.
The text was updated successfully, but these errors were encountered: