Uzebox Forums

I tried to take a look at this and found something really weird. In the IKD.uze downloadable from the opening post as of now, at https://github.com/Uzebox/uzebox/blob/master/kernel/uzeboxVideoEngineCore.s#L387 , there is a "cpi ZL, 251" instruction, where the only larger difference begins ...

Gave the game a small update (over weeks, eh, not making progress too fast here), now it has a title screen and some end-game sounds. And very few ROM bytes left. Will still give this some polish before I would say release ready (once there will of course set up its Wiki, and also post it to a few p...

The flickering seen in Uzem I believe emerges from this line: https://github.com/danboid/IKD/blob/main/IKD.c#L632 I see that the title screen is redrawn in every frame here https://github.com/danboid/IKD/blob/main/IKD.c#L174 (Indentation is a bit jumbled up around there, but it is clear enough that ...

Yes, there is something clearly going on here. Now it seems like it behaves differently on real HW (a channel apparently missing), Uzem (flickering) and CUzebox (audio and video seemingly as it would be intended). The CUzebox emulator tracks the video refresh rate with audio frequency to keep both i...

Trying to do C++ on the Uzebox has just the same caveats like trying to do C++ on other similarly constrained embedded environments. There are a fair few around (including 32 bits) where inattentive use of C++ would cause issues like quickly running out of ROM or RAM, or possibly not being able to j...

Some ideas for debugging: Probably the simplest if suspecting some ALU or timing issue, assuming this is mostly C code, is to tweak compiler settings, to see whether it changed anything. Some compiler settings for example could be more prone to produce some instruction combination which the emulator...

There is some idea of a game there screenshot.png Looking at it, as it was left off it could be worked on further in the sense it isn't as big as it seems by the result. The build places the tileset in it four times (which includes a full Mode 3 ASCII font, that alone repeated four times uses up 24 ...

Did some experimenting. Below 500Hz the real hardware feels quite strongly cutting off compared to the emulator (which just passes the signal to the PC's audio system), the ~50Hz-100Hz range on the real hardware (EUzebox) feels fairly low on the real thing compared to how loud it gets above 500Hz.

It is no room to put these without stuff getting in the way. I have a 15.6" TV packed away, which I now dug up. Listening it I am not sure. I know on the real hardware frequency response is different, the Uzebox audio output isn't too refined. The signal might be there, but frequency components...

Took a quick look at it, but it is code I am unfamiliar with. The emulators (both) are cycle-perfect for the ALU and key peripherals, and as far as my knowledge of the AVR ALU goes, they should be accurate (the UzeBurn thing I did also does a very throughout ALU test). An ALU bug would be a lot more...