Andre Weissflog

Hmm, sorry I'm afraid I can't help much with debugging at the moment. I need to find some time to get back into emulator coding, but at the moment I'm...

Just a headsup, this will take longer to fix, because there's some tricky places in chips/ui_dbg.h where I'm assuming that the 'read-pointer' always advances one byte forward, see here: https://github.com/floooh/chips/blob/093ca02eae3d7d36eb1a38d75b7fc9e913f2a9b3/ui/ui_dbg.h#L345-L353...

The tape emulation worked at one point, but you're right, it appears to be broken currently (in the C64 at least, since this should work: https://floooh.github.io/tiny8bit/c64-ui.html?file=c64/boulderdash_c64.tap ), most likely when...

> not sure why the c1530_play() function would also clear the MOTOR pin though it appears that the "old code" (search for the c64_start_tape function here: https://github.com/floooh/chips/commit/362d41f27f546fcb557e67f778b418917e9ebf6c#diff-9936031ddd3b8f394a5ea4d8c278df21) also switched the...

Yes this looks like a bug, good catch! I'm hesitant to merge this now though. I would prefer to do this in my next emulator coding "phase" (don't know yet...

That's a good idea, in YAKC (https://floooh.github.io/virtualkc/) I had a general onscreen keyboard UI, but this is hardwired to one computer model (the KC85/3), using the information in the keyboard...

I agree, while the current way host system keys are mapped to the target system keys is quite convenient for regular text input, it fails for target-specific keys. I want...

> The real chip draws TWO pixels per clock cycle, effectively it is like drawing ONE pixel at twice the clock speed; so I think the MC6847_TICK_HZ constant should be...

Hi @hoglet67, this is awesome stuff :) I'll try to have a close look when I have some time, I definitely want to improve the Atom emulation and merge your...

Hi, FYI: I'm going to merge changes to the Atom emulation soon which changes the emulators tick function. Basically, the remaining chips in the Atom (i8255 and MC6847) had their...