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
With a V1 connected, and a program too big to fit in V1, on clicking Download for V2 only in the dialogue below, there is a big red banner error showing the same message as in the console output.
The saved hex file does not generate the expected error 927 display on a V1 - just a blank display. It's not a universal hex.
Sometimes, there is an error and console message "Download failed, please try again", instead. I think that's about WebUSB. In any case, it is also inappropriate at this stage because the download proceeds to save the file as expected.
Expected behavior
No error message after choosing Download for V2 only, unless there is a problem saving the file.
Saved hex file should generate error 927 on V1
Screenshots
micro:bit version (please complete the following information):
V1.5
Desktop (please complete the following information):
OS: [e.g. iOS] Windows 10
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22] 130
The text was updated successfully, but these errors were encountered:
The saved hex file does not generate the expected error 927 display on a V1 - just a blank display. It's not a universal hex.
Yes, essentially this.
I had a look at the downloaded file and it does contain some Universal Hex features, like using the Other/Metadata Data record to include the MakeCode project data, but the rest of the file is "normal" Intel hex, which saves the V2 programme into the micro:bit flash even if it's a V1.
@abchatra in this cases it'd be recommended for MakeCode to generate a full Universal Hex, where the micro:bit V1 portion simply shows error 927.
Describe the bug
With a V1 connected, and a program too big to fit in V1, on clicking Download for V2 only in the dialogue below, there is a big red banner error showing the same message as in the console output.
The saved hex file does not generate the expected error 927 display on a V1 - just a blank display. It's not a universal hex.
Sometimes, there is an error and console message "Download failed, please try again", instead. I think that's about WebUSB. In any case, it is also inappropriate at this stage because the download proceeds to save the file as expected.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error message after choosing Download for V2 only, unless there is a problem saving the file.
Saved hex file should generate error 927 on V1
Screenshots
micro:bit version (please complete the following information):
V1.5
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: