I don’t know why, but after 40+ years, I have been making some revisions to…
October 16, 2025 · First shared in the Apple II Enthusiasts Facebook group
I don’t know why, but after 40+ years, I have been making some revisions to the custom Corvus firmware I wrote in 84. Back to burning EPROMs to test the new code, with many erase and reprogramming cycles. I guess it’s a chance to remember what a colossal effort it was to develop firmware in the early days without having aids like modern debuggers. The old tricks like storing debug information in the bottom of the stack come back quickly though. I had forgotten so many things about this project. Things like the original Corvus firmware being hard coded for slot 6… who uses the BIT instruction? No one but the Corvus engineer who wrote the hard coded slot 6 dependency. 😆 I guess I have finally learned my lesson about having sparse comments in my own code, making someone’s life (my own 😆), difficult in the future. I guess it’s a chance to add some comments, and to figure out a few things that still didn’t work quite right. A fun remembrance of my glory days as an assembly language programmer in the 8 bit days before I moved to C and the dark side of Windows 3.x programming
https://www.facebook.com/share/p/17Etqu8aMa/

No bit,x address modes, so few used the instruction, especially for device firmware

Nice being CRC error free today

Labeled the original firmware so I don’t misplace it and erase the EPROM by mistake

Reinstalled the mirror board in the working 11MB drive

Burn, test, debug, erase, try again…

6502, Z80, NEC 7811, i8051, i8088 were some of the instruction sets I coded to the metal back in the day
Tags: corvus, history, hardware, software