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

Download for V2 only shows inappropriate error messages and the V2 only hex doesn't show error 927 on V1 #6010

Open
martinwork opened this issue Nov 13, 2024 · 1 comment

Comments

@martinwork
Copy link
Contributor

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.
Image

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:

  1. Go to https://makecode.microbit.org/_XiqCMEWEK1gk
  2. Click on Download
  3. Click Download for V2 only
  4. See error

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
Image

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
@microbit-carlos
Copy link
Collaborator

microbit-carlos commented Nov 15, 2024

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.

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