Skip to main content

Introduction

This blog is intended to showcase my electronics and computer projects, as well as educating about related concepts. I currently have an ongoing project consisting of an 8-bit computer I call Zephyr (because I'm bad at coming up with names). Details as follow:

CPU: Zilog Z80 rated to 10MHz (Currently running at 625KHz)
Memory: 8KB of ROM, 32KB of RAM with room for expansion
I/O: Serial

Currently it doesn't do anything since I need to create an EEPROM programmer, which I plan to make using shift registers and a controller of some variety.

I also have plans to create another 8-bit computer project called CosNaut (Again, bad at names) using an RCA 1802 'COSMAC' CPU, though anything else is not set in stone.

Will post updates as necessary.

Comments

Post a Comment

Popular posts from this blog

HP-125 Floppy Drive Emulation

A 'back burner' project I have in mind is to repair an old HP-125 computer I picked up at a thrift shop quite a while ago. This computer has no onboard storage drives, instead coming paired with an HP-82901M floppy drive unit , which communicates over HPIB/GPIB/IEEE-488 (whatever you want to call it). These drives are either pure unobtanium, or are downright bankrupting, so I need to find a way to emulate it. My requirements are as follows: Standalone operation, not requiring another computer to emulate Low cost parts, or using mostly parts I have on hand (Optional) Multiple uses, I don't want this to be a one-trick pony While I've learned how the GPIB protocol works, I have no idea what the command set is that either the HP-125 and/or HP-82901M speaks. I've found mention of the HP-82901M using the Amigo command set, as introduced with the HP-300 "Amigo", on this page about emulating an Amigo-compatible drive with a modern PC . That project requir...
1 comment
Read more

EEPROM Programmer Pt.3

Well, this post contains both good news and bad news: Good News part 1. I spent the later half of yesterday wiring up the arduino to the EEPROM board proper. I then began to check basic functionality such as proper voltages, proper and state of the EEPROM control lines. Everything checked out, so I decided to test with an NVRAM that has an identical pinout. I encountered a few errors in the software in this process. The controller was not allowing the device to complete a read or write cycle before moving on to the next byte, fixed by adding a 1ms delay between pulling the read or write lines low, and pulling them back up. I accidentally left out a = in the test part of some if statements, so it would read as 'if(Error=1)' instead of 'if(Error==1)'. This caused the send/receive portions of the write and dump routines to fail out, thinking the Xmodem packet was being improperly received or sent. The first 128 bytes of the NVRAM was being rewritten with data from the ...
Post a Comment
Read more