Re:Pineapple ONE: open-source 32 bit RISC-V CPU that you can...
by ReactiveJelly on Sunday September 17, 2023 @04:24PM
(#37548959)
Very cool! Someone else mentioned breadboard vs. PCB density of course.
So if it's real, maybe I'll get one.
Re:Pineapple ONE: open-source 32 bit RISC-V CPU that you can...
by mips_r4300i on Monday September 18, 2023 @03:20AM
(#37553284)
Thanks for pointing this out.
In the olden days it used to be fairly common to use eeproms (or just proms) with a few latches as a state machine. This way it was possible to accomplish many of the things you'd need a CPU for, but without needing one at all.
It's not too far to add an ALU and some control flow after that, hehe.
Re:Pineapple ONE: open-source 32 bit RISC-V CPU that you can...
by segfaultbuserr on Monday September 18, 2023 @03:50AM
(#37553452)
The use of microcode in CPUs began like this too. Originally, people replaced random logic in a CPU's Control Unit with a Mask ROM or a PLA. The goal was simply to avoid the trouble of building decoders from gates one by one. Although it's a form of programmable logic, few would describe these simple ROM lookup tables as "programs". Later, people pushed the idea further to build a small state machine to control the ALUs, and the microcode in ROM would then be used in turn to control that state machine. This marked the birth of "micro-sequencers". In addition to the internal use in integrated circuits, they also found applications as universal blocking blocks for custom discrete CPUs in the 1980s, examples included the AMD Am2900, Am29100 and Am29300 series chips. Building a CPU became as easy as connecting these logic blocks together and writing some microcode for the micro-sequencer. Continue the development of microcode further, and you eventually get the final form, which is a CPU within a CPU, and you may argue that the CPU is not really hardware anymore, but is driven by software.
At which point does the use of microcode makes a CPU software rather than hardware? There's really no clear boundary, so the microcode always exists on the blurring line between hardware and software. This issue was also a heavily-contented subject in several lawsuits that involved cloning CPUs, as hardware is not covered by copyright, but software is.
Furthermore, the control unit is entirely in EEPROM, which means all the discrete components needed for random logic are largely eliminated, consolidating possibly hundreds (or thousands?) of gates into just 3 chips [1][2]. In fact it's sufficient to design a functional CPU entirely using RAM and ROM with just 15 chips in total. [3] You may as well argue that EEPROMs are the most rudimentary form of programmable logic device that can implement arbitrary combinational logic, making it an ad-hoc FPGA (especially when modern EEPROMs are so large, 64 K for 16-bit chips). But the use of ROMs and PLAs in Control Units is a legitimate and standard way to design discrete-logic CPUs even back in the 70s, so I won't call it "cheating".
[1] https://github.com/pineapple-one/hardware-eagle
[2] https://github.com/pineapple-one/hardware-eagle/blob/main/co...
[3] https://bailleux.net/pub/ob-project-gray1.pdf