Slashdot Mirror


Developer Creates DIY 8-Bit CPU

MaizeMan writes "Not for the easily distracted: a Belmont software developer's hand-built CPU was featured in Wired recently. Starting with a $50 wire wrap board, Steve Chamberlin built his CPU with 1253 pieces of wire, each wire wrapped by hand at both ends. Chamberlin salvaged parts from '70s and '80s era computers, and the final result is an 8-bit processor with keyboard input, a USB connection, and VGA graphical output. More details are available on the developer's blog."

125 of 187 comments (clear)

  1. I can do 2^1 better by physicsphairy · · Score: 5, Funny

    I own a two-bit computer. My dad gave it to me. I know it is two bits because before he gave it to me he would often remark "I hate this ******* two bit computer."

    (Yes, it is also reproductive.)

  2. But does it run Vista? by VampireByte · · Score: 2, Funny

    Sorry, I just had to ask.

    --

    Run and catch, run and catch, the lamb is caught in the blackberry patch.

    1. Re:But does it run Vista? by dunkelfalke · · Score: 2, Informative

      not a single version of windows was designed to run on 8 bit cpus.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    2. Re:But does it run Vista? by NusEnFleur · · Score: 1

      None, ran 8 bits cpus. As for the design itself, I am not so sure anymore.

    3. Re:But does it run Vista? by Anonymous Coward · · Score: 5, Insightful

      Why does this question keep coming up? Of course it does. It's turing-complete, so it's just a matter of writing the software. Not for the impatient users, obviously.

    4. Re:But does it run Vista? by Vanders · · Score: 5, Informative

      According to the fine article it has a 24bit address bus and an 8bit data bus, but presents everything via. a 16bit ISA. It's a bit like a 8088.

      Of course the ISA is probably nothing like an x86, so it still wouldn't run [MS|PC|DR|Free]-DOS anyway. Apparently it does have a C compiler, so perhaps you could port Bochs or Qemu to it and then run DOS on that. Emulated. On a TTL CPU running at 2Mhz (2Mhz slower than the original IBM PC). Maybe not then.

    5. Re:But does it run Vista? by morgan_greywolf · · Score: 4, Interesting

      Well, your response applies slightly more to Linux (one would just have to implement a Linux kernel on the 8-bit CPU, which isn't likely to happen to anytime soon) and doesn't really apply to Vista at all. MIcrosoft would have to implement Vista, and unless there is sufficient market demand for this 8-bit CPU, they'll never do it, since the incentive for them to write an 8-bit Vista is approximately zero.

      While it may be possible to write a Linux kernel for an 8-bit processor, this, too, is not likely, at least not a complete Linux kernel. Linux was pretty much designed and written from the ground up on a 32-bit processor with built-in low-level support for multitasking.

      So, IOW, while you are theoretically correct, from a practical standpoint implementing Vista or Linux or any other modern OS, with the exception of FreeDOS, is virtually impossible. Hence, the GP's joke retains its original humor.

    6. Re:But does it run Vista? by Anonymous Coward · · Score: 3, Insightful

      any Turing machine can emulate any other. an 8 bit CPU can do a 128 bit calculation, it just has to do it in small steps. you would probably need a lot of disk space.

      for example you store on disk the input and output of every transistor in a core2duo. then you iterate through each transistor and set the output according to the input. it may take a billion clock cycles to emulate one core2duo clock cycle, but its possible.

    7. Re:But does it run Vista? by morgan_greywolf · · Score: 1

      Okay, so you could write an emulator to make it run Vista. Very, very, very slowly. So it would take, what? Two weeks to boot?

    8. Re:But does it run Vista? by Anonymous Coward · · Score: 1, Insightful

      i think 2 weeks is optimistic :-)

    9. Re:But does it run Vista? by CarpetShark · · Score: 1

      Well, that and another lifetime or so hand-crafting 1GB+ of memory chips, yeah.

    10. Re:But does it run Vista? by Krneki · · Score: 4, Insightful

      Good enough for Space Invaders.

      --
      Love many, trust a few, do harm to none.
    11. Re:But does it run Vista? by uglyduckling · · Score: 3, Informative

      He didn't say it's a Turing Machine, he said it's Turing-complete, which means that (in theory) it can ran any conceivable program, with the obvious limits of RAM/Disk.

    12. Re:But does it run Vista? by the+person+standing · · Score: 1

      Emulating virtual address space would eat up most of the time. Besides the patience, the users lifespan might be the limiting factor.

    13. Re:But does it run Vista? by Zero__Kelvin · · Score: 3, Funny

      "not a single version of windows was designed to run on 8 bit cpus."

      Which is only logical, given that no version of Windows was developed to run on 32 bit or 64 bit CPUs either. Which versions of Windows were designed to crash on various CPUs is another matter ;-)

      (Lighten up over-sensitive Windows Weeinie's with mod points. It is a joke)

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    14. Re:But does it run Vista? by wisty · · Score: 2, Funny

      Are we still talking about 8 bit machines?

    15. Re:But does it run Vista? by thethibs · · Score: 1

      Turing-complete is not enough if you have a user interface.

      --
      I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
    16. Re:But does it run Vista? by zombie_monkey · · Score: 1

      I would love to run somethign like Contiki on it.

    17. Re:But does it run Vista? by astralpancakes · · Score: 1

      Hence, the GP's joke retains its original humor.

      Too bad it still isn't funny.

    18. Re:But does it run Vista? by Anonymous Coward · · Score: 1, Insightful

      You vote republican, don't you?

      Ivory tower is their favorite buzzword. Intelligence is not a negative, nor is high education. Show some respect for people who better themselves, you high school dropout.

    19. Re:But does it run Vista? by Anonymous Coward · · Score: 1, Informative

      if you want to be practical then you just need sufficient storage. it if can be connected up to a 1TB hard disk then that would probably be fine.

    20. Re:But does it run Vista? by jlarocco · · Score: 1

      Sure it is. Input and output is nothing more than reading and writing to the proper memory locations.

  3. Probably not. by Philip_the_physicist · · Score: 1

    Crysis, OTOH, is fine

  4. Re:A lenient definition of "make" by jcr · · Score: 4, Funny

    The functional components are all off-the-shelf TTL ICs.

    Well, he is only one person, after all. Even if he was studly enough to build it from vacuum tubes, he probably wouldn't be winding his own filaments.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  5. But does it run Minix 1? by Celeste+R · · Score: 1

    After all, it has to be better than MS-DOS!

    --
    There are no perfect answers, only the right questions. More questions at http://foresightandhindsight.blogspot.com/
  6. It must be early.... by Bentov · · Score: 1, Offtopic

    Not one "but does it run linux" ? I'm sooooo disappointed...

    1. Re:It must be early.... by David+Gerard · · Score: 2, Interesting

      You might, however, be able to adapt LUnix to it!

      --
      http://rocknerd.co.uk
  7. I would love to do that. by jcr · · Score: 1

    If only I had a time machine and a highly extended lifespan, so I could spare a couple thousand hours on it...

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  8. Re:A lenient definition of "make" by Anonymous Coward · · Score: 4, Insightful

    That's the way it used to be done: I wouldn't claim that DEC engineers did not "make" the PDP-1 because it was constructed from wire-wrap discrete components. The only other sensible option for someone who wants to "make" their own CPU at home would be to program an FPGA, which is certainly less interesting than what this guy has done.

  9. Re:A lenient definition of "make" by grolschie · · Score: 5, Interesting

    ...Even if he was studly enough to build it from vacuum tubes, he probably wouldn't be winding his own filaments.

    Uh, maybe not. :-)

  10. Correct! Six thousand cores by Dachannien · · Score: 5, Funny

    built his CPU with 1253 pieces of wire

    Farnsworth: Let me show you around. That's my lab table, and this is my work stool, and over there is my intergalactic spaceship. And here is where I keep assorted lengths of wire.
    Fry: Whoa! A real live space ship!
    Farnsworth: I designed it myself. Let me show you some of the different lengths of wire I used.

  11. That's how we used to make all hobby computers by thomasdz · · Score: 5, Insightful

    Yeah, baby...
    Back before the days of the 4004, 8008, and 8080, when we built computers, we REALLY built computers.
    None of this: take a pre-built-motherboard, add a pre-built-power-supply, add a pre-built graphics card...

    oblig: get off my lawn

    --
    Karma: Excellent. 15 moderator points expire sometime.
    1. Re:That's how we used to make all hobby computers by hughbar · · Score: 5, Interesting

      Exactly, I used to burn little holes in my shirts with the ferric chloride http://en.wikipedia.org/wiki/Iron(III)_chloride that we were using to etch circuit boards (they were masked with wax or aluminium paint). My mother was not pleased with this.

      Then, as a private project, I built a half adder with washing machine relays but it never worked properly because of power supply problems (which was the 12v transformer from my train set).

      As parent already said (but they're so PESKY and disrespectful): Hey you kids, GET OFF MY LAWN

      --
      On y va, qui mal y pense!
    2. Re:That's how we used to make all hobby computers by frdmfghtr · · Score: 3, Funny

      Then, as a private project, I built a half adder with washing machine relays but it never worked properly because of power supply problems (which was the 12v transformer from my train set).

      Did you try using the "permanent press" cycle?

      --
      Government's idea of a balanced budget: take money from the right pocket to balance...oh who am I kidding?
    3. Re:That's how we used to make all hobby computers by earthforce_1 · · Score: 3, Interesting

      The ROM in the computer on the moon lander used ferrite rope memory that was hand strung from bins of cores pre-programmed as '1's and '0's. The assemblers literally had a bin full of 1's and 0's.

      Those where the days when assembly programming really meant just that.

      http://en.wikipedia.org/wiki/Apollo_Guidance_Computer

      --
      My rights don't need management.
    4. Re:That's how we used to make all hobby computers by thomasdz · · Score: 2, Funny

      Ummmm... whoever modded me funny: I was being serious. (except for the "get off my lawn" part)
      I cringe whenever I hear a young whippersnapper say "I built my own computer over the weekend" because "building a computer" to me doesn't mean slapping together pre-built parts.
      (yeah, yeah, and I'm sure someone will respond to my thread saying when they were young, they built their own transistors from the sand in their backyard and smelted their own copper wires and I should get off THEIR lawn. :-)

      --
      Karma: Excellent. 15 moderator points expire sometime.
    5. Re:That's how we used to make all hobby computers by mikael · · Score: 1

      Look at some of the early SGI workstations or PC's with graphics accelerator boards - every separate function (video RAM to analog RAMDAC, pixel processing, motherboard bus interface) was a separate ASIC with some other chips to handle communication.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    6. Re:That's how we used to make all hobby computers by fuzzyfuzzyfungus · · Score: 1

      I hope that the 0 bin has been enshrined with proper respect as the mother of all /dev/zero's.

    7. Re:That's how we used to make all hobby computers by oliderid · · Score: 1

      Excuse me but back in my days we used sheeps to compute. (simple one living sheep 1, one dead sheep 0) http://www.youtube.com/watch?v=ZDAM5lSPCwk

  12. Watchout Intel by mgblst · · Score: 5, Funny

    It is about time that Intel has some competition.

  13. Re:A lenient definition of "make" by Vanders · · Score: 1

    The difference is a lot of menial work and big mess of wires, but nothing fundamental: Buy a couple of logic gates, connect them to form a CPU.

    The "connect them to form a CPU" is sort of the trick there though isn't it? I could buy a bunch of TTL chips and "connect them up" but it sure as hell wouldn't do anything other than let the smoke out. It certainly wouldn't be a CPU.

    Neither approach will produce a working CPU when one morning you wake up on a deserted island.

    My chances of waking up on a deserted island are probably slim, but lets say I did: unless that desert island happens to have a small power generating facility, a couple of hundred working computers, a dozen CPU designers and fully working ASIC fab. complete with a fully trained work force, I don't think anyone is going to be making their own CPUs, no matter how you might try to do it.

  14. Eek! Wire wrapping! by Sponge+Bath · · Score: 3, Insightful

    All the board level products I designed in the early 90s had to be prototyped with wire wrapping. Even if you are careful, by the time you do hundreds of connections it is almost inevitable there is some flaw. You might miscount a row of pins and attach to the wrong pin. The process of layering multiple connection to a single pin might damage a wire at the bottom. Wires might break or make a shaky connection that comes or goes.

    I would not ever want to go back to that, but it did two useful things: The plodding physical process of "I'm now connecting this to that." forced a slow, comprehensive walk through of your design which can reveal design mistakes. The other is honing debugging skills of intermittent problems: "Is this a design flaw or a wire making poor contact?".

    1. Re:Eek! Wire wrapping! by Animats · · Score: 1

      Wire wrapping isn't that big a deal. I still have a wire wrap gun, although I haven't used it in years. You buy precut, wire in different standard lengths, and it comes with the right amount of insulation pre-stripped at each end. You have a wire list (A-15 to C-42, etc., and you just follow the wire list. It's usual to sort the wire list by length, so that you do the longest wires first. It's time-consuming, but not difficult. Far easier than ordinary hand-wiring.

      Fully automatic wire wrap machines go back to the 1960s. That's how IBM mainframes were built. "Semi-automatic" wire wrap machines are still around; the human does all the work, and the machine checks them. If the wire wrap gun is in the wrong place, it won't wrap.

  15. Er... WTF? by brunes69 · · Score: 5, Insightful

    To have fun is not a good enough reason to do something?

    I guess you would be happier if he was just another fat slob who "has fun" by watching American Idol?

    This is quite possibly the most asinine comment I have seen on Slashdot in a long time.

    1. Re:Er... WTF? by Vanders · · Score: 1

      I'd be happier if his people skills came close to matching his geek skills.

      What? All he said was "I don't know". It's an honest answer. You are the one who's being an ass about it.

    2. Re:Er... WTF? by Vanders · · Score: 1

      Go fuck yourself.

      I'm busy ironing at the moment but I'll be sure to fuck myself later.

      Here's an idea, maybe you wouldn't get modded down so often if you didn't act like an ass?

    3. Re:Er... WTF? by X0563511 · · Score: 1

      Children! Do I need to pull this internet around and take us all home?!

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    4. Re:Er... WTF? by Vanders · · Score: 1

      Sorry Dad.


      Are we there yet?

  16. Done before... in 16-bits by Elledan · · Score: 5, Interesting

    Magic-1, a 16-bit TTL-based, wire-wrap PCB computer.

    Slashdot posted an article on Magic-1 when it was completed years ago as well.

    --
    Site & blog: http://www.mayaposch.com
  17. Re:College Project by jacquesm · · Score: 1

    errmmm. pics or ... ;)

    a 68020 !! That's a pretty impressive feat. What kind of chips did you build it from ? Regular series ttl or cmos or something at a higher level of integration ? Did it work ?

    Given the fact that the chip was originally named (the 68000) for it's transistor count even if you were using fairly large 'blocks' it would likely have spanned many boards.

    What clock speed did you get it to run on ?

  18. Real dedication! by JohnMurtari · · Score: 1

    I remember a grad class that went into circuit design and register transfer language. I was amazed how opcodes could be made to twiddle bits. We just had a software simulator to try our designs -- I admire this guy for building it. Cool!

  19. Re:A lenient definition of "make" by morgan_greywolf · · Score: 3, Funny

    I'm gonna get off his lawn for sure!

  20. Fantastic! by adosch · · Score: 5, Interesting

    There needs to be more Steve Chamberlin's in the world. Personal (or enterprise, for that matter) computing hardware has hit a mass exploitation mark; computers today have such an abundance of resources, storage and processing power, any developer I've had to work with in the last half of decade sees the computer, much like Steve mentioned in TFA, as "...like black boxes... and understand what they do, but not how they do it." which leads to blatant disregard for anything, really sloppy ways of coding and development, zero ideology or best practice on how to truly harness and control resources efficiently. I don't expect anyone to have a physics background or be some die-hard electrical engineer, but there's definitely something to be said for growing up and working with early computer models where you had to give two shakes about that stuff. This is very cool, indeed.

    1. Re:Fantastic! by Vellmont · · Score: 3, Insightful


      which leads to blatant disregard for anything, really sloppy ways of coding and development, zero ideology or best practice on how to truly harness and control resources efficiently.

      I see lots of sloppy coding practices, but they have about nothing to do with hardware efficiency. (Think buginess and maintainability). Unless you're writing for specialized environments, the days of worrying about a few cycles of CPU, or a few kilobytes of memory are over (and good riddance).

      The world has changed and the challenges have changed. It's great to design your own CPU, and I'm sure he learned an enormous amount. But to pretend that we should all be thinking like it's still 1979 is absurd.

      --
      AccountKiller
  21. .. so some slashdot halfwit could criticises him by Anonymous Coward · · Score: 2, Insightful

    slashdot is really sucking hard these days.

    the guy makes an off-the-cuff comment about his motivation, and some braindead moron on slashdot criticizes him for it.

    HE MADE A FUCKING COMPUTER, YOU MOUTH-BREATHING DIPSHIT.

    of course he had motivation! how could you sum up the motivation in just a couple of words?

    what worthless piece of shit you are

  22. Re:A lenient definition of "make" by nurb432 · · Score: 1

    Tho you were being funny, one really could build this out of discrete semi conductor diodes quite easily.

    People have been known to make their own tubes too ya know -> http://www.eetimes.eu/consumer/205801104

    --
    ---- Booth was a patriot ----
  23. Re:Why? by scotch · · Score: 1

    To vex morons like yourself.

    --
    XML causes global warming.
  24. Re:A lenient definition of "make" by pHus10n · · Score: 1, Interesting

    Thank you for linking this video. Wow! This guy is the REAL Doc Brown lol. I watched every moment of it in awe. So that's how ol' school electronics was done :) Really, thanks!

  25. newsworthy? by SolusSD · · Score: 3, Informative

    This sounds like the kind of project any computer engineering undergrad curriculum would cover. Myself, I have had to design/build 4 different processors of varying complexity (basic mips, pipelined, superscalar, etc) during my years as an undergrad. Its cool nonetheless and by no means "easy".

    1. Re:newsworthy? by Bill,+Shooter+of+Bul · · Score: 1

      Did you really build them on a real physical wirewrap? Or just in software? Neither one is easy, but I think this story is about the lengths that the guy took to actually do it with the wirewrap.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
  26. Love that it is on wired by WindBourne · · Score: 2, Funny

    Sounds like the right mag for this project, though make is the more appropriate one.

    --
    I prefer the "u" in honour as it seems to be missing these days.
  27. Re:Why did he do all this? by Capt.+Skinny · · Score: 1

    I can just imagine what my wife would think... (She'd let me, she's great that way...).

    She'd let you? And that's a virtue? Damn, man.

  28. Re:A lenient definition of "make" by m50d · · Score: 1
    The only other sensible option for someone who wants to "make" their own CPU at home would be to program an FPGA, which is certainly less interesting than what this guy has done.

    I'm not at all convinced. Sure, it'd be less likely to put your name on slashdot, but the part doing it on the FPGA removes - connecting all the wires together - isn't actually interesting; by and large, it's tedious manual labour. It's certainly worth knowing how to, but honestly once you've wired ten chips up you've pretty much "done them all". To my mind using an FPGA makes it easier to concentrate on the actually interesting part, the processor design, rather than getting caught up in the endless "wire A into hole B".

    --
    I am trolling
  29. Re:Why did he do all this? by syousef · · Score: 1

    She'd let you? And that's a virtue? Damn, man.

    When you are time poor and share financial responsibility for a family, and you're the bread-winner, decisions like that are joint decisions. I know that's a difficult concept for some to grasp and you think that just means I'm under the thumb, but you know what, I couldn't do what she does for our child. We only have one child he's still an infant and he doesn't sleep much. She's had it very rough, gets very little sleep etc. So, yes, she's entitled to have some input into how I spend my time and our money. And yes, it is a virtue that she'll let me spend that time and money doing something she doesn't agree with or sees as pointless.

    So you know what, if you want to belittle a guy for not being a selfish piece of fuck when he's got a family, go fuck yourself.

    --
    These posts express my own personal views, not those of my employer
  30. LBA-complete by tepples · · Score: 2, Informative

    He didn't say it's a Turing Machine, he said it's Turing-complete, which means that (in theory) it can ran any conceivable program, with the obvious limits of RAM/Disk.

    The limits of memory make the proper term "LBA-complete", where the required memory varies linearly with the size of the input, rather than "Turing-complete". But in practice, "Turing-complete" means LBA-complete.

    1. Re:LBA-complete by TheLink · · Score: 1

      But what if it's networked? Then humans and other stuff can send it all sorts of stuff.

      The same input today could produce a very different output tomorrow.

      --
    2. Re:LBA-complete by tepples · · Score: 1

      But what if it's networked?

      In computational complexity theory, a "program" is most often taken to mean a subroutine that doesn't perform input or output. If you have input or output, such as network packets, the program ends, and it starts again after receiving the next packet. Two programs communicating over a network link are coroutines, but I'm not aware of any generalizations of complexity theory to cover coroutines.

    3. Re:LBA-complete by retchdog · · Score: 1

      Doesn't communication complexity try to model this?

      http://en.wikipedia.org/wiki/Communication_complexity

      --
      "They were pure niggers." – Noam Chomsky
    4. Re:LBA-complete by tepples · · Score: 1

      neither term really applies to hardware with a fixed amount of memory.

      LBAs have a fixed amount of memory, proportional to the size of the input. For a larger input, you use a larger LBA.

  31. Re:A lenient definition of "make" by moonbender · · Score: 1

    Fantastic video, thanks for the link.

    --
    Switch back to Slashdot's D1 system.
  32. Re:Why did he do all this? by Capt.+Skinny · · Score: 1

    touche

  33. Re:A lenient definition of "make" by confused+one · · Score: 1

    The "make your own chip" approach is usually done in FPGAs these days. You can still buy a 6502, as a verilog program for an FPGA, if you really want it. As to actually processing your own silicon wafer, that can be done in your garage workshop, but is much harder.

  34. Re:Why did he do all this? by Zero__Kelvin · · Score: 1

    I see your posts all of the time, and it baffles me that more people don't respond to you and tell you to go fsck yourself the way the parent poster did! You are constantly posting ridiculous diatribes that often contradict each other. You are the scourge of Slashdot, and I really hope they cancel your account!

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  35. Re:A lenient definition of "make" by digitalunity · · Score: 1

    Good luck with that.

    Nothing about your garage is similar to a clean room and god forbid you actually meet the requirements for a class 10 clean room, you wont have enough room left for any equipment!

    --
    You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.
  36. Re:A lenient definition of "make" by goombah99 · · Score: 1

    Wow! thank you for that link. made my month.

    --
    Some drink at the fountain of knowledge. Others just gargle.
  37. Re:A lenient definition of "make" by hattig · · Score: 2, Funny

    Damn right, the lazy fucker should have dug the iron ore up himself, then dug up the coal to fire his home-built kiln so that he could create his own iron. Of course he would have had to hand-build bellows to create steel, and maybe he should have home built EVERYTHING ELSE in the production pipeline, including hunting his own food every night from his homebuilt house. Luckily he invented his own language to communicate with other people so that he could coordinate things!

  38. Re:A lenient definition of "make" by Jesus_666 · · Score: 1

    A clean room isn't that important when you use an 80 mm process.

    --
    USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
  39. Re:A lenient definition of "make" by cheftw · · Score: 1

    his homebuilt house

    I think you have a chicken-and-egg problem with that one.

    --
    Always back up, never back down. ---- Think you're cool 'cos your uid is prime? Take mine, modulo the one digit integers
  40. Re:A lenient definition of "make" by Bill,+Shooter+of+Bul · · Score: 1

    No its cool, but not as cool as if he had done more with lesser equipment. I used to work for a pioneering arcade manufacturer. I loved going through their museums. From the earliest prototypes, you can literally see the struggles and sweat that went into making the product : tons of wires going everywhere huge heat sinks and capacitors everywhere. Then as you go through time to later modules some of the wires disappear thinks slowly start to shrink, until the latest version is just a small pc board with industry standard connectors for everything. I mean yeah it also had a FPGA that had some pretty cool stuff in it, but you couldn't tell that by just looking at it. I remain more impressed with the earlier advances, than the latter ones.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
  41. Where does it say that? by argent · · Score: 3, Informative

    The article mentions "Z-80" among the parts used. The Z-80 itself is an 8-Bit CPU.

    The blog says "Build the CPU from scratch, primarily using basic 7400-series logic. No 6502, Z-80, etc."

    That's the only reference to the Z80 I can find in either the article or the blog.

    1. Re:Where does it say that? by nuckfuts · · Score: 1

      Thanks for correcting me on that. I misread "No 6502" as "Number 6502".

    2. Re:Where does it say that? by argent · · Score: 1

      Making me feel old. :)

      6502 vs 8080/z80 was THE big home computer war back in the late '70s. Apple vs Radio Shack. "crapple" vs "trash 80".

    3. Re:Where does it say that? by zmollusc · · Score: 1

      6809 FTW! 8 bit multiply, bitches!!

      --
      They whose government reduces their essential liberties for temporary security, receive neither liberty nor security.
    4. Re:Where does it say that? by metaforest · · Score: 1

      I still have a MC6809 in my part stash.... Nifty little CPU...

    5. Re:Where does it say that? by argent · · Score: 1

      Oh yes, I thought the 6809 was a very tasty little chip. I didn't have an opportunity to do anything with it, alas.

      On the other hand, have you ever worked on the 1802?

  42. Re:A lenient definition of "make" by confused+one · · Score: 3, Insightful

    Clean rooms are needed at some level. Cleanliness is the key factor. If you're doing this in a garage workshop you'll not be doing 45nm process. You'll be closer to 45um (1/20mm), along the lines of the medium scale and large scale integration done in the '60's and '70's. If you're willing to accept losses and low yield, you can accomplish this using simple bench top equipment. Having done something similar in a university lab back in the '80s, I can assure you it CAN BE DONE.

  43. But Russians did it first! by argent · · Score: 1

    Back in the '80s there was a rumor of a Russian version of the Apple II with the CPU implemented in wire-wrap, because they couldn't get actual 6502s in Russia.

  44. Re:Why did he do all this? by htdrifter · · Score: 1

    You do it for the same reason you climb a mountain.
    Because it's there.

  45. Re:But does it run Vista by MillionthMonkey · · Score: 1

    I tried writing a virtualization in Z-80 assembler of a 32-bit system meeting Microsoft's specifications for Vista.

    Unfortunately it couldn't actually run Vista because Microsoft underballed the requirements.

  46. Intel 4004 schematics by MillionthMonkey · · Score: 1

    Just look at all the embroidery in a 4-bit CPU.

    1. Re:Intel 4004 schematics by metaforest · · Score: 1

      the 68000 was the last CPU that Motorola laid out by hand. They had a 'print-check' room that was the size of a high school gymnasium that's sole purpose was to allow the engineering team to walk around on massive photo-plots of the schematic and later the process layers. Shoes were removed. Engineers padded around on the plots in their socks.

      Later processors were compiled from RTL and pre-verliog HDL descriptions.

      I myself ran early Apple //e code compatibility tests on pre-silicon prototypes of the Apple //gs. The pre-VLSI prototypes were the size of a medium sized conference room table and there were only three of them made. at any given time only 1 was operational. The final post-VLSI //gs mobo was about the same area as a modern ATX mobo.

  47. Re:A lenient definition of "make" by JakartaDean · · Score: 1

    That was, in a very geeky way, incredibly beautiful. Thanks for posting. Whenever I think artisinal craftsmanship is dead, someone like you comes along and restores my faith.

    --
    The subject who is truly loyal to the Chief Magistrate will neither advise nor submit to arbitrary measures (Junius)
  48. I love this stuff by strags · · Score: 1

    Some time ago (nearly 10 years - wow!) I made a microcontroller-based homebrew MP3 player: http://codepuppies.com/~ben/sens/pic/mp3 . My big mess of wires was a tiny fraction of the size of his, and it caused me enough headaches - tracking down signal noise, random glitches, etc... Hats off to this guy.

    I'd also recommend this book: http://en.wikipedia.org/wiki/The_Soul_of_a_New_Machine to anyone who finds the Wired article of interest. It doesn't get too technical, but it describes the trials and tribulations of bringing a new machine to life, initially on wire-wrap boards - as well as some of the politics involved in a corporate environment.

  49. Re:Correct! Six thousand cores by linzeal · · Score: 1

    I've known many engineers like this, forest for the trees folk who can work for years on a sub-assembly and greatly ignore the totality of the project.

  50. Slashdotted? by argent · · Score: 1

    Can't see the video... 404 compliant.

    1. Re:Slashdotted? by grolschie · · Score: 1

      hmmm... the link works for me.

  51. That reminded me of a Microsoft joke... by RudeIota · · Score: 2, Funny

    "Windows: A thirty-two bit extension and graphical shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor which was written by a two-bit company that can't stand one bit of competition."

    --
    Fact: Everything I say is fiction.
  52. What about CP/M? by NervousNerd · · Score: 1

    What about CP/M? That ran on systems similar to that, and I believe it is open source these days.

  53. 74181/74182 by dido · · Score: 1

    I can't seem to find a parts list, but well, I wonder if he used a 74181 Arithmetic Logic Unit and 74182 carry lookahead generator. That would provide quite a few of the arithmetic and logical instructions that one might expect in 8-bit CPUs common in the 1980s in just three packages (the 74181 ALU is a 4-bit ALU, but it can be cascaded, and the 74182 can be used to provide carry lookahead for up to four 74181s). However, you'll also need an instruction decoder, and that, unless you use a programmable logic device of some sort (in which case you're actually doing microprogramming), will need quite a few logic gates...

    --
    Qu'on me donne six lignes écrites de la main du plus honnête homme, j'y trouverai de quoi le faire pendre.
    1. Re:74181/74182 by jeffb+(2.718) · · Score: 1

      Yep, the 181 shows up in the layout diagram on his site. I'm a little surprised, actually -- if you compromise enough to use GALs (programmable logic), it's kind of pointless to brag about being "TTL-based". If I build something out of a fistful of PICs, and hook them together with TTL-level signals, can I claim the same thing?

      I built a "video card" for a TRS-80 as a hobby project about 25 years ago -- 50 or so chips, 8 or 10 solderless breadboards, and a baking sheet for support/ground-plane. 30 rows, 100 columns, 8x16 pixels per character, memory-mapped, and the only thing that wasn't SS/MS-TTL was the RAM for the display buffer and the character lookup table. I guess I spent six months or so building it up piece-by-piece -- the bus interface, then the clock and divider chain, then the character RAM, then the display RAM, then the driver. I'm still kind of amazed that I pulled it off. I actually used the whole thing as a terminal for a year or two, because 100x30 was so much more pleasant than 64x16. And once I wrote a VT52 emulator and a serial driver that could keep up with a 1200-baud modem, I could actually do visual editing from my dorm room -- the height of luxury, I'm telling you.

  54. Re:A lenient definition of "make" by artor3 · · Score: 1

    Um, no. I'm saying doing it with wirewrap TTL is more interesting than doing it by programming an FPGA. It's more interesting and requires more skill. If I was suitably motivated I could learn enough Verilog to build a simple 8bit CPU on an FPGA, but it would take me significantly longer to learn the EE required to do it with TTL.

    It really isn't much harder. I guarantee that you could learn to wire up some TTL chips just as easily as you could learn Verilog. Is "assign x = y" really so much easier than connecting pin X to pin Y with a wire?

    The tricky parts in digital electronics are always the various hazards (race conditions, glitching, metastability, etc...), and they will happen regardless of whether you're using wired discrete components or an FPGA. That's where the real electrical engineering work is.

    In fact, I'd say that starting on an FPGA without understanding those hazards would actually be more difficult, because you won't understand what is causing them. You'll say that x = (~a && ~b) || (a && c), and you won't understand why x glitches when moving from ABC = 001 to ABC = 101.

  55. Re:A lenient definition of "make" by tuxicle · · Score: 1

    Initially, I was quite surprised he could squeeze enough stuff to build a computer capable of running a BASIC interpreter on a single Augat board, given his claim of only using 7400 logic.

    Scroll down to the Board Layout on his blog, you'll find that many of the supposed "7400" logic chips are actually 20V8 and 22V10 PALs. Programmable logic heresy, I tell you!

    The actual 7400 logic chips I found so far are: 74LS74 (Flip flops), 74LS139 (dual 1:4 decoder), 74LS161 (dual 4-bit counter), 74LS163 (dual 4-bit counter), 74LS181 (ALU), 74LS244 (Bus transceiver), 74LS377 (octal D flip flop).

    Given that mix, I would say this falls somewhere in the MicroVAX era, which had a similar mix of low-density PALs and 7400 logic. My colleague at work used to make stuff on similar boards. Some examples include a color display driver (for a VAX) and an antenna positioner (again, for a VAX). The display driver has long been replaced by Linux boxes, but the antenna positioner (and VAX) still lives on.

    Steve, if you're reading this, we still have lots of Augat boards kicking around, along with lots of boxes of 7400 logic (sorry, no 22V10s!)

  56. Re:A lenient definition of "make" by Tacvek · · Score: 1

    On the other hand good design practice for anything but ultra high speed devices makes glitching moot. You use flops, not latches, and all outputs are registered, so the outside world always sees clean signals. And that is a terribe example, since it is quite likely for no glitching to occur with that, depending on the design of the lookup table used in the fpga.

    Oh and these days sythesis tools have gotten pretty darn good. "assign a=b*c;" is certainly a hell of a lot easier than building a combinational multiplier from, ttl chips. (Granted, a combinational multiplier is often not a great idea, but occasionally it is called for.)

    --
    Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
  57. The PDP-1 was soldered, not wire wrapped by phage434 · · Score: 1

    Wire wrapped construction was a great step forward in reliability from the solder of the PDP-1 and PDP-6 computers.

  58. Re:Why did he do all this? by mutube · · Score: 1

    You do it for the same reason you climb a mountain.

    Because you're being chased by goats?

  59. Re:Why did he do all this? by Zero__Kelvin · · Score: 1

    WWHHHOOOOSSSHHHH!

    ROTFLMAO

    What makes you think I was replying to you instead of the post from "Anonymous Coward" to which I clearly did reply? Do you not know how to follow a thread? I was replying to "Anonymous Coward" and pretending like I thought that was 1 single person, making a joke that obviously went over your head. What is perhaps more baffling is that you are the one who told someone to fuck off, so you would think that would have been a pretty big hint that I was not referring to you. In the words of Bill Murray in the hilarious movie Stripes, Lighten up Francis!

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  60. Fine you drive an early car then by SmallFurryCreature · · Score: 1

    One where you had to give a rat arse about the ambient temperature to set the fuel mix, where you had to handcrank to get an idea what compression really means. Real manly brakes, none of this ABS crap that required you to anticipate as it would take a while to bring several tons of metal to a full stop. Etc etc. Personally, I love the modern age, where we can concentrate on what we want to achieve not being limited by the tools.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:Fine you drive an early car then by smoker2 · · Score: 1

      While all you said is fair enough, sometimes not knowing the basics can get you in trouble. When steering wasn't so positive, or your brakes weren't as efficient, you learned how to handle several tons of metal. So when you threw it into a corner, you could feel the car lean into the corner, and you knew instinctively when it was likely to break away from you. These days, you just point and shoot, and the result is lots of cars hitting each other or leaving the road.

      Plus the ease of use of modern vehicles means that they are mechanically abused beyond anything an older car would be. People use brakes for everything, don't bother to drop down a gear when slowing down or when speeding up again (yes you can do that on autos) and generally treat it like a funfair ride. Together with the ICE which prevents you from hearing your engine, or that of other vehicles, modern driving has become an insular past-time, which does not promote cooperation and mutual respect on the roads.

      And ABS doesn't mean you stop quicker - it just removes the chance of skidding, so you can retain steering ability. Any decent driver wouldn't need to be hitting the brakes that hard in the first place. Most deceleration manoeuvres can be accomplished simply by dropping the throttle earlier, and changing down a gear. Observation is the key.

      If you prefer not being limited by the tools, you still have to bear in mind that they are still limited to what is possible or safe. Unless you understand that, you will end up going wrong, and you won't be able to push those limits responsibly.

  61. The LCD on the front probably has more CPU by noidentity · · Score: 1

    The LCD panel on the front of the case probably has more processing power in its internal controller than the rest of this project, heh.

  62. Re:A lenient definition of "make" by fuzzyfuzzyfungus · · Score: 1

    See here for said simple benchtop equipment.

  63. Re:Why did he do all this? by syousef · · Score: 1

    If you were replying to a/c, I apologise. I've been getting some shit lately here.

    Have a good one.

    --
    These posts express my own personal views, not those of my employer
  64. Re:Why did he do all this? by Zero__Kelvin · · Score: 1

    Since you apologized, I will graciously accept. It is good to see that kind of maturity here on /.

    As you are no doubt aware, such mature behavior is not nearly as common as one would expect from a site ostensibly frequented by professionals.

    Peace and Blessed Be ...

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  65. Not to mention... by Lead+Butthead · · Score: 1

    The LCD panel on the front of the case probably has more processing power in its internal controller than the rest of this project, heh.

    Not to mention that despite the back lighting, the LCD panel probably uses but 1/100th of the power consumed by all the discrete logic.

    --
    ELOI, ELOI, LAMA SABACHTHANI!?
  66. just use a not dirty room by dlenmn · · Score: 1

    I've done lithography outside of a cleanroom before. The person who ran the facility put it this way (when telling me why they require clean shoes or shoe covers): we don't pretend that this is a cleanroom, but we do try to keep it a not dirty room.

  67. Re:A lenient definition of "make" by X0563511 · · Score: 1

    Wow, 8cm resolution. I think I could do better with a chisel and hammer!

    (I know what you meant, but i couldn't help myself)

    --
    For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
  68. Re:A lenient definition of "make" by religious+freak · · Score: 1

    Wow. Awesome vid, I just wish I understood more of it.

    --
    If you can read this... 01110101 01110010 00100000 01100001 00100000 01100111 01100101 01100101 01101011
  69. Re:A lenient definition of "make" by schamberlin · · Score: 1

    I am reading this, and if that was an offer to pass on some old Augat boards, I'd *love* to have them! They're getting tough to find! My email address is on the stevechamberlin.com website if you want to contact me.

    If I ever said Big Mess o' Wires was only 7400 logic, it was a lie. My original goal was to use mostly 7400 logic. In the end there were also quite a few 22v10 PALs as you noticed, and two LSI chips related to audio and video RAMDAC.

  70. Re:Why? by Hucko · · Score: 1

    One can be critical, just not a luddite and wet blanket.

    --
    Semi-automatic amateur armchair Australian philosopher; conjecture ready at any moment...
  71. Re:College Project by metaforest · · Score: 1

    When I was 16 or 17 my father gave me a "green-wire" board that had been tossed. This was a 68000L8 'GMAP' processor board designed by Granger & Assoc. back in the early 80's this particular prototype board never ran and the engineering staff couldn't figure out why. I ended up with the board, a set of schematics and the PCB wiring plots. When I got a little more hardware savvy I was able to figure out why it didn't run.... and why this particular spin of the board design had FAIL written all over it.

    One of their 'green-wire' fixes had left a TTL inverter faced backwards near the bottom of the system clock chain, thus feeding the CPU an effective clock of about 50 MHz... This had a strange effect on the poor 68000L8.... This extreme over-clocking caused the 68000 to sequence the address pins sequentially counting up from 0x000000 to 0xFFFFFF... I wonder if that was a test mode for the processor?

    In the end I was able to get it to run code. I removed the errant gate from the clock chain and the 68K sprung to life and began executing code.

    Before I stopped messing with it I was able to adapt a 68030 and 68882 FPU daughter card to the board and get it to run at about 30Mhz reliably.

    Most of the I/O sections were horribly mangled by a truly disastrous interaction between the schematic layout artist and the PCB layout artist. Which lead to none of the I/O actually being serviceable. In the end, I chucked the board in around 1995 after having learned all I could learn from it.

    The most valuable lessons being: This is how to design a large format embedded controller... NOT!

    All code written for the system was developed and debugged on a Mac SE30 via Apple's MPW IDE and the 68K assembler. The resulting binary image was then sneaker-netted to an Apple //gs that had an EPROM burner plugged into one of it's card-slots. The binary image was then split into The high and low EPROM images using a custom AppleSoft BASIC program, and loaded into the hires video memory of the Apple //. The EPROM burner could only be accessed via the monitor ROM (CALL -151) The resulting EPROMS were then socketed into the GMAP and power applied.... 5 LEDs on the board supplied debugging and status/ code progress info....

  72. Congrats & respect. by MxMatrix · · Score: 1

    Unbelieveable COOL !. I'm thrilled by the idea people still want to build their own design and put real effort in making it WORK. Congrats and my respect Steve Chamberlin. There is live beyond (W)intel and (L)AMD.

    --
    Bach says it all.
  73. Re:A lenient definition of "make" by ChrisMaple · · Score: 1

    The glass-forming equipment isn't unreasonable -- propane torch and such -- and the spot welder is within the realm of an enthusiastic mechanics hobbyist. What blew me away was the induction heater.

    --
    Contribute to civilization: ari.aynrand.org/donate
  74. Re:A lenient definition of "make" by ChrisMaple · · Score: 1

    Look at the devices, you'll see a large portion of them are 22V10. These are primitive programmable logic devices, midway between gate logic and FPGA. If he had actually made a design with gate ICs and flipflops, it would have been much bigger.

    --
    Contribute to civilization: ari.aynrand.org/donate
  75. Re:A lenient definition of "make" by ChrisMaple · · Score: 1

    I was disappointed to see that the clock is 8 MHz divided down to 2 MHz, which I assume is the fastest possible instruction rate. Given that the design is microcoded, most instructions probably are many cycles. Ah, well... optimizing for speed means a more complicated and difficult design.

    --
    Contribute to civilization: ari.aynrand.org/donate
  76. FLOPS? by averner · · Score: 1

    Out of curiosity how many FLOPS (floating operations per second) does this processor do? I know it's probably not a lot but I am still really curious. If it doesn't do floating operations then I am still wondering how many integer operations is does. In fact any rough indicator of speed would be nice!

    --
    Member of the 7 Digit UID Club
  77. Re:A lenient definition of "make" by BoothbyTCD · · Score: 1

    Reminds me of 'A Tale in the Desert'

    --
    snig