And a display-shield project
Yes we can use the standard makecode site it is just the arcade one that we seem to be stuck with
alright, i believe i’ve figured it out. the online flashing tool doesn’t like how we append the source code at the end of the file after the EOF marker in the hex file. this isn’t an issue for hex files that include both hardware variants (v1 and v2) because we move the EOF to the end of the file in a bit of post processing in the pxt-microbit target https://github.com/microsoft/pxt-microbit/blob/master/compiler/combiner.ts#L17
the reason you and i were seeing different results @martinwork was because i was using a hex file that only compiled the v2 hardware variant, so it had the same issues with the EOF being in the wrong place.
luckily, it seems like we already have a compiler flag for moving the EOF to the actual end. i’ll see about enabling that for the compiler in pxt-arcade
2 Likes
alright, unfortunately moving the EOF marker just causes the hex parser in the flashing tool to get caught on the non standard record type that we use to encode the source in the file.
i’ll keep poking at this from my side, but @martinwork i think the proper fix would be to fix the hex file parser so that it ignores everything after the EOF marker
1 Like
Thanks to Matt and Carlos, the hex download tool has been updated to work with Arcade files.
Thanks to @Lissa91 for reporting, and @richard and everyone, for analysing!
3 Likes
Thank you @martinwork , Matt, Carlos and @richard without your help we would never have been able to give our pupils this opportunity!
I’m looking forward to showing them that it works next week - I have tested it on a microbit and it seems to work - but sadly did not bring the Kitronik pack home!
Thanks again all your help has been much appreciated!
2 Likes