|
|
|
|
|
by petschge
2514 days ago
|
|
But then you get crappy breadboards that once in a while gives a bad connection. Without any visual clue. That can be very hard to debug, especially for the hardware newbie Ben Eater is teaching. Spending an extra $50 to make the process hassle free and enjoyable is money well spent. |
|
I'm currently working on a homebrew Z80 computer. I'm at the stage of moving the preliminary designs to PCBs, but from my experience, wirewrapping is a lot better than breadboarding when you start building circuits with many signal wires. Breadboards are quick and simple at first when you can "plug and play", but it would quickly become a nightmare when the number of connections and wires exceed 200. It may be a less concern for a modern microcontroller as i2c and SPI are serial interfaces, but on a 8-bit computer, you'll hit this number really quickly, because the system bus is 24-bit (16-bit addr, 8-bit data), parallel. A bus driver using two unidirectional buffer has 24 x 2 + 8 = 56 wires, two RAM chips have 48 wires, a ROM has another 24 wires, it's already 148 wires now for a bare-minimum system without even an I/O port. It will get out of control soon. Also, a 16-bit machine will become a nightmare even quicker as they have 32-bit bus.
On wirewrapped boards, you'll never get a bad connection without any visual clue, the connection is as solid as soldering, and there are no jumper wires hanging in the mid-air to stop you from probing it using an oscilloscope. Strongly recommended, to learn more, search keywords "wirewrap electronics" at YouTube.