Casio BN-20 ROM dump is in progress. 52 jumper wires is a mess. We seem to have a couple of address bits flipped, because the data looks ALMOST right but not quite, with every 16 bytes out of order.

Our programmer/flasher tool only has 40 pins, so we're dumping upper/lower byte separately.

I guess we'll continue tomorrow, because it's a bad idea to do precise operations when tired, with a risk of destroying the only copy of the chips
And we've struck gold with the ROM. 2 megabyte of ROM, what did Casio put in there? Well, loads of screenshots and a bunch of UI stored as bitmaps, of course.... thread
more bitmaps from teh ROM!
and more, it just doesn't end. You'd expect there's a UI builder, but when you have 2 MB of ROM on an x86 device, you might as well just pre-render everything
the ROM is seemingly endless, why so many images are stored in it, are you a real OS or just a combination of mocks with transitions between the images
@nina_kali_nina There are certainly UIs out there like that. I know of at least one in-car touch screen system, and I suspect most, maybe all, are like that.
Seems to be the preference for embedded stuff where I assume it's more predictable and uses less energy. Of course, they don't need to share design aesthetics between independent apps, either. Or support custom skins!
I guess power might be the reason for Casio, too?
Although some of those images are quite surprising.
@nina_kali_nina oh, I'll just note I've now seen a similar thread here: https://tech.lgbt/@nina_kali_nina/115981342994868948