Closed microbit-carlos closed 3 years ago
@microbit-mark do you have an up-to-date list of all the error codes? We need to pick a new error to indicate "this hex is only valid on a v2"
@jaustin @microbit-carlos
This is a zip of private repo https://github.com/martinwork/v1error, including a built hex.
I have used the error code I see on V2 for a MakeCode BLE project (927).
Thanks Martin. I cannot access that repo, I'm afraid. How different is the codebase to the existing SAEP? Would it make any sense to have a 'v1' and 'v2' version or folder in this repo?
If not, I can create a new repo on the Foundation account that you can push to.
I've tried the hex on my v1 and no suprrises it worsk fine! Does it have the same ability to change the code as the v2 hex? Michal might want to know that.
I think it will be simpler and cleaner to make a separate repo. The only common code is the font file. The version number is not exported. The stated purpose didn't seem to require that. It would be easy enough to add on.
I have invited @jaustin and @microbit-carlos to the repo, but please do create a foundation repo I can copy to.
@jaustin and @microbit-carlos Created and merged PR https://github.com/microbit-foundation/stand-alone-error-v1/pull/1
To have a minimal v1 Intel Hex that could be included in a universal hex file with programs that are only meant for v2.
This way the file size increase would be minimal and the hex would still do something in a micro:bit v1 (show an error).