thepit.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance populated by the denizens of #bikeDC, #bikeVA, #bikeMD, and various other friends and communities. Share opinions, news, photos of your bike, food takes, and memes. There may be some horsing around. In this house, we #bancars. All hail The Pit!

Administered by:

Server stats:

63
active users

#z80

7 posts5 participants1 post today
Continued thread
I wrote a very stupid and ugly #z80 #assembly to try it (I'm sure it is filled of errors and I will need a lot of debugging with the #logicprobe), but I could not write it to the #EEPROM . The #minipro errors out while checking the first byte after writing it. That's strange, because I'm using the same programmer and the same eeprom chip as before, and always worked. But in the meanwhile I changed computer, operating system and USB cable, so... troubleshooting time! Yay!
Continued thread
The "parallel terminal", as I call it, reads the data when the #Z80 writes to a specific bus port and writes to the bus when the Z80 is reading. Then sends/receive the same bytes via the #Arduino #UART to the computer. So you can connect to the Arduino with a terminal and interact with the Pat80 computer. This is how I took the screenshot on the repository readme.
[continues]
I tried to assess the situation of the #Pat80 #Z80 #homebrew #computer (https://git.ichibi.eu/penguin86/pato-z80-home-computer)
A computer to be useful should be able to:
- load a program and/or data
- execute the program on the data
- present the resulting data
It already does all that, but in a very janky way: its only way to input/output stuff is via a temporary terminal interface I made with an Arduino directly hooked to a IO port. [continues]
Ichibipato-z80-home-computerPat80 Home Computer is an attempt to develop the simplest possible Zilog Z80 based computer in 2021
Progress!
I've got a basic #emulator working for my #Pat80 #homebrew #zilog #z80 #computer !
This should ease the os development as I can test the changes without having to: remove the #eeprom from the computer (without bending the pins), program it in the #TL866 programmer, place it again on the computer (aligning pins correctly), test, notice it's not working and have no idea why, start debugging with the logic probe on the #address and #data pins, swear in arcane languages... 😅

https://git.ichibi.eu/penguin86/pato-z80-home-computer/commits/branch/c-emulator

After much testing and code comparison, the new Feb 2025 Release of #Vezza - my #z80 high speed #zmachine is ready! Took way longer than expected to synchronize across all of the code bases, particularly making sure that all optimizations made it across all platforms - TRS-80 model 1, TRS-80 model 3, TRS-80 model 4, the CP/M versions (~18 platforms), the embedded versions (Spectrum tape, TEC-1G), and slowly pushing into the Agon Light version (which has even more updates still in progress). Lots of individual tweaks, and some major rethinks and rewrites have come together to accelerate game play.

The hardest part of rewriting in this update involved rewriting the dictionary search code. I ended up going back to the original jzip interpreter, written in C for Unix waaay back when. Jzip provided much of the logic that went into ZXZVM, which provided the base for #M4ZVM #M3ZVM and #Vezza. Going back to Jzip made sense as Jzip has an even longer history; and is highly tested and stable and still maintained. This research gave me the confidence that the streamlining and changes I was making to such a fundamental part of the game would work, making all inputted dictionary searching more efficient.

To work around how CP/M stores executable files I spent a lot of time re-organising the memory map to make the executable smaller. This involved rearranging where the initialization code was stored inside the increasingly complex layout. Support across multiple versions means I needed to break up variable sized code and strings to sit inside variable sized gaps, while still compiling all the CP/M versions from the same interconnected set of source files. It needed quite a few manual checks to ensure that it all worked.

What this all means is that your favourite #infocom #punyinform and other text adventures will all play on your favourite z80 #retrocomputing platforms even faster than before!

More details in the devlog and downloads can be found at:
#TRS80 versions sijnstra.itch.io/m4zvm
#CPM #CPM80 versions sijnstra.itch.io/vezza

I'd like to resume my #zilog #z80 based #homebrew #computer project, the " #Pat80 ":
https://git.ichibi.eu/penguin86/pato-z80-home-computer/src/branch/c-emulator

When I left it, some years ago, I had no idea what I was doing.

Now, I have absolutely no idea what I am doing AND I don't remember where I left, but apparently I've written a decent enough documentation...

Anyway, apparently I decided the old python #emulator was too janky and started writing a new one in C, language i do not know and never use.

This will be fun
Ichibipato-z80-home-computerPat80 Home Computer is an attempt to develop the simplest possible Zilog Z80 based computer in 2021
Continued thread

Climbing out of the CPM/Zork rabbit hole for now...

I have fixed and reformatted the Z80 Z-Code Interpreter source, and successfully assembled it for RunCPM... And it works.

Going to play the game for a while, and then get back into my Kim-1 rabbit hole.

Anyway, all my CPM/Zork efforts are here:

github.com/ilneill/MyInfocom

Enjoy!

#CPM
#RunCPM
#Z80
#Zork
#Infocom

GitHubGitHub - ilneill/MyInfocom: All my Infocom discoveries and learning... CPM, Zork and beyond!All my Infocom discoveries and learning... CPM, Zork and beyond! - ilneill/MyInfocom

Having a break from other "rabbit holes" to return to #CPM, and I'm away from my hardware, so it's emulation only.

Got #runCPM up my laptop and had to get #Zork running. Found the eblong Infocom archive and the #Z80 the Z Interpretator source (+ Zork Z3 file).

Fixed some issues and it assembled with #z80asm but when I ran it the text display was not right. I recognised escape code issues. Dug into the Z80 code and found the problem. Hours later I found the reason.

Wyse codes, not VT100/ANSI 😉

Random memory: Some 45-50 years ago, my dad sold and serviced #CPM machines, specifically #GeminiMicrocomputers from the #UK. His customers seemed to be primarily people connected to printing and the press. One guy represented a printing house, which I believe also doubled as a #Buddhist #monastery, and visited my dad's shop quite frequently.

The thing that triggered this memory, was that apart from #Buddhism and printing, my dad's customer - friend if I'm not mistaken - also did a bit of recreational programming. He was in fact the author of a Danish #Pacman clone called "Gufferen" which translates to something along the lines of "the muncher". At the time, it was a breath taking action game in 80x25 character resolution, and I'm absolutely gutted that I will probably never see it again.

Good times.