
Well, that broke faster than I expected.
=>.<=
Basically all of my testing has been with the web-based Xtron Pro emulator built into the Xmaker MakeCode Editor, so it appeared that it was working properly.
Fortunately, I'd managed to get my code to the point of actually having a minimally-playable game, so I wanted to get it onto the actual device so I could play around with it in my hands and see how it performed, and what needed to be improved.
Unfortunately, I ran into problems right away. My file manager defaulted to "trashing" the old file instead of straight-up deleting it, which means that it created a "trash" folder. Which turned out to be full of garbage files and folders. And when I started my new code, it ran for a bit (long enough to land one block to the bottom), then it crashed with a system-level error message.
And refused the boot again after that.
It'll vibrate the pager motor and flash the low-battery LED at appropriate times, but it won't show up as a thumbdrive, nor will the screen light up again.
Oh, and yes, I am in contact with the company that made this device. They're not sure what happened either, and since it's using a microcontroller I don't have debug kit for, I can't do any debugging myself just yet.
(if it was an Espressif brand microcontroller, I'd have the tools, but it's an STM32-series chip, so I can't without their specific programming and debugging tools)
I have been assured that they'll work with me to get it fixed, or replaced if it can't be fixed, but there's a bunch of testing we'll both need to do before that's possible.
I've sent them the file I'd put on the device in the first place, so if there's an error with that, they'll be able to see what might need to be fixed. Otherwise, it would be an issue directly with my module, and I don't know how that all would work.
For the moment, however, it's purely a waiting game. Which isn't helped by the fact that, relative to my timezone, the person I'm working with is usually only on at 4am...