Vic Chwe

Tested official Windows build inside Wine. It's tricky to get working, but once configured properly it works as expected. In addition to "2048 bytes long; expected 16384 bytes" bug, I was not able to use command line to launch FUSE, it constantly says "couldn't find ROM 'uspeech.rom", and no, full path did not help. I'll post all details on SC forums shortly. TL;DR: configure ROMs using GUI and only after that turn on uSpeech.

I think it still works. At least for me. It was the first thing I tried once I've got 1.7.0 flatpak installed. It needs ROMs, and I think the name for sp0256 ROM has changed slightly, but once they provided it works. I'll see if I can get to SC forums. The best way to test would be something like (assuming both ROMs are in the current directory): fuse -m 48 --tape Booty.tzx.zip --uspeech --romsp0256 sp0256-al2.rom --romuspeech uspeech.rom $ sha256sum Booty.tzx.zip 68f87e7f94f36cd7e054d179279dff42ce0cc978ea0f76896c1cce4bb763d612...

I have totally missed the fact that IF1 ULA detects the falling edge of the byte leader pulse, thus providing hardware synchronisation for every byte. With that in mind, "playback" works and broadcast transmissions are working, too. Code is nice and clean and I like it. However, there is a significant (~5 msec) delay before the receiving machine sees inbound data and it breaks everything because at the time receiver sends ACK back to the sender the sender has already started re-transmission. Latest...

Most of the programmes (I've seen so far) utilising CMD18 and CMD25 seem to expect Z-Controller SD card interface, and those appear to be using quite a lot of SPI mode commands. Next revision of the patch, adds basic support for CMD16 and CMD59.

SD Card: multiple block read/write support

Unfortunately, at the moment I do not fully understand all the subtleties of IF1 protocol and I could not get a (reliably) working prototype. I am publishing my changes in case if someone is able to pick it up. Updated 2024-09-28: Cleaned up code, slightly easier to read (and smaller)

All configuration options can be changed via command line arguments. Those override anything found in config file. Unfortunately, it means that changing configuration file location using a command line argument is not that simple. A while ago I thought I needed that option anyway, so I created a naive implementation. I have not used it for a while and it MAY NOT work with all build targets! That is why I am not creating a separate patch ticket and simply attaching my changes here.

Unfortunately, at the moment I do not fully understand all the subtleties of IF1 protocol and I could not get a (reliably) working prototype. I am publishing my changes in case if someone is able to pick it up.