in reply to Hack: Building a computer platform
The first semester was digital logic and small-scale integration. You have lectures and laboratory.
The whole second semester was learning how to use A, X and Y registers, a stack, page zero addressing, and all of the other opcodes.
What really blew my mind was the synergy: if I wanted to know what an opcode really did, I just read the corresponding line of the "source code" that implemented the microprocessor! We learned the chip-design language, and we could see that each line was just an opcode. Some opcodes took more than one clock to execute, but that was okay, because they took more than one line of source code.
(This also explained to me how someone figured out and published the "missing opcodes" of the 6502. They were just doing the last clock's worth of work for a larger opcode. Sort of like adding a goto label in the middle of a line of a program, then using it.)
I saw today that there's a resurgence of people building Apple I computers (6502, anybody?) just for the sheer enjoyment and education of knowing every circuit in a whole computer intimately. That was one of the last processors that anyone sufficiently interested could really learn and understand inside and out.
--
[ e d @ h a l l e y . c c ]
|
|---|