1. Keep CPU designin the simulated world
Many builders warn that moving from Logisim/Verilog to physical chips introduces tedious, invisible problems (timing glitches, bad wiring, etc.) that drain the fun out of design.
"I always applaud homebrew cpu designs but after doing so many myself I would reaaaaly advice to stay away from dip chips/breadboards/wirewraps and any attempts to put it into real physical world. ... these are not challenges, just mundane dull work." â artemonster
2. How early computers were actually programmed
The discussion reflects on manual methodsâplugboards, toggle switches, punch cards, and maskâprogrammed ROMsâshowing that âprogrammingâ once meant rewiring hardware or entering code by hand. > "Plugboards! Think telephone exchange but used as a ROM." â jacquesm
"Actual application code was hardwired, entered manually with switches and lights, or with punch cards... Later, when ICs were sufficiently advanced, maskâprogrammed ROMs/PLAs." â moring
3. Community enthusiasm & practical implementation tips
Homebrew CPU projects are celebrated, and contributors share concrete hardware tricks (e.g., simple microcode memory, chipâlevel signal routing).
"CPU's microcode can be surprisingly simple: ... The microcode can be just a memory where the input signals are the memory address and the output is the control signals." â mrgaro
"To get both blinkenlights for registers and triâstate for bus driving, use two â574 chips in parallel rather than a â377 behind a â245." â p_nuts