Intel C8744-8 Engineering Sample – Early 1983

In 1980 Intel released the MCS-51 family of microcontrollers, a design that would go on to become one of the pillars of the 8-bit MCU market.  Initially the family consisted of the 8051, which included 4KBytes of on-chip ROM (or UV-EPROM in the case of the 8751) and 128 bytes of RAM as well as the 8031 which did not include the ROM, all program memory was off chip.

The 8051 was a wild success with Intel struggling to meet demand.  Intel did not have the fab capacity to produce both the 8051, and the very in demand 8088 (thanks to IBM).  In 1984 Intel opened a new fab in Albuquerque, New Mexico to build other chips, freeing up production space in the California fab for more 8051s.  Even so, an $8 8051 was routinely scalped for over $200 on the grey market and waiting periods of up to a year were common in order to receive orders, with many companies on allocation.  Intel licensed the design to both AMD (who built a fab in Austin to make it) as well as Signetics in an effort to keep up with demand.  The hardest to get part in the industry, was the 8051 from 1983-1984.

P8344 – A ROMLess 8044, so essentially an 8031 + SDLC controller.

So in the midst of this insatiable demand for an MCU that they did not have the capacity to produce, Intel releases the RUPI-44 (Remote Universal Peripheral Interface). The RUPI-44, also known as the 8044, is an 8051 with an additional 64 bytes of RAM and a full serial communication co-processor on die.  Specifically it was an 8051 that handled the SDLC (Synchronous Data Link Control) protocol in hardware.  Intel had an SDLC controller, known as the 8273, but it was limited to 64kbps, the 8044 could handle data transfers of up to 2.4Mbps due to the 8051 core’s high speed and close coupling of the serial controller.

SDLC was developed in 1975 by IBM and was generally used as a way for mainframes to communicate with various peripherals and terminals.  It supports error correction and multi-point, point to point, and loop connections.  In 1979 SDLC was standardized as HDLC (High-Level Data Link Control) which the RUPI-44 also supports.  While popular in the 70’s and 80’s its use has faded out, though it achieved some long lived use in Europe running the Intel derived BITBUS protocol well into the 90’s.

Read More »

Original PENTIUM California License (number) plate

This California license plate came through the museum on its way to a collector in Sweden.  I get many items in that are unusual and rare but this was the first processor relates plate I have seen.  The best part? It came with some history.

It was ordered as a vanity plate by a salesman at Intel around 1995.  He was later hired by AMD as a sales person but his car still said “Pentium” which obviously was a bit of a problem.  As a token of commitment to his new company he gave it to his manager at AMD, despite the fact that he was offered $3000 for it from an employee at Intel.  It likely sat on a desk for some time until it was sold on eBay (for the low price of $100) where it was spotted by a collector in Sweden who asked me to purchase it for him.

It now resides with the collection of CPU Collection.SE

Part 2 of my abbreviated biography of Chuck H. Moore’s processor designs.  Part 1 covered the early days of Novix, and the RTX2000.

Patriot Scientific IGNiTE – Based on the Sh-Boom

Moore was not content to just create one processor design, or one company.  In the 1980’s he also ran Computer Cowboys, a consulting/design company.  In 1985 he designed the Sh-boom processor with Russell H. Fish III.  This was a 32-bit stack processor, though with 16 general purpose registers, that was again designed with Forth in mind.  It was capable of running much faster then the rest of the system so Moore designed a way to run the processor faster then the rest of the board, and still keep things in sync, innovative at them time, and now standard practice.  The Sh-Boom was not a particularly wide success and was later licensed by Patriot Scientific through a company called Nanotronics, which Fish had transferred his rights to the Sh-Boom to in 1991.  Patriot rebranded and reworked the Sh-Boom as the PSC1000 and targeted it to the Java market.  Java byte code could be translated to run in similar fashion as Forth on the PSC1000 and at 100MHz, it was quick.  In the early 2000’s Patriot again rebranded the ShBoom and called the design IGNITE.  Patriot no longer makes or sells processors, concentrating only on Intellectual Property (Patent licensing).

After designing the Sh-Boom, and the Novix series, Moore developed yet another processor in 1990 called the MuP21.  This was the beginning of a what would be a common thread in Moore’s designs.  MISC (Minimal Instruction Set Computer), which is essentially an even simpler RISC design, multiprocessor/multicore, and efficiency have become the hallmarks of his designs.  The MuP21 was a 21 bit processor with only 24 instructions. At 20MHz performance was 80 MIPS as it could fetch four 5-bit instructions in a 20 bit word.  It was manufactured in a 40 pin DIP on a 1.2 micron process with 7000 transistors.

In 1993 Moore designed the F21, again a 21 bit CPU based on the MuP21, designed to run Forth, and including 27 instructions.  It was fab’d by Mosis on a 0.8u process.  The F21 microprocessor contains a Stack Machine CPU (with a pair of stacks like the NC4000), a video i/o coprocessor, an analog i/o coprocessor, a serial network i/o coprocessor, an parallel port, a real time clock, some on chip ROM  and an external memory interface. Performance was 500 MIPS (this was an asynchronous design, so ‘clock speed’ is a bit of a misnomer) and transistor count had risen to about 15,000.  The F21 was made up through 1998, however the design continued to evolve.  A version of the F21 was developed called the i21, originally for Chuck Moore’s iTV Corporation, which was one of the very first set top Internet appliance companies.  It integrated additional featured such as infrared remote interface, modem DMA interface and a keyboard DMA interface. The F21 scaled well, and was tiny, remember, only 15,000 transistors, which at 0.18u takes up a VERY small die, and allowed performance to hit 2400MIPS @ 1.8V.  One could put a very large amount of these on a single die…..

Read More »

In coin collecting often times an example is valued not because of its perfection, but because of its imperfections.  An off-center print, the obverse being printed upside down, or the double strike, where a coin doesn’t get cleared form the die and gets hit twice.

Such appears to be the case with this Intel A80386DX-33.  It clearly went through the engraver twice. A similar example (from the same exact lot) is fine, so clearly this one, made in early 1992, was a mistake that was not caught.  I have seen mis-aligned prints, off center etc, but this is the first example i have seen that was engraved twice.  It is interesting that even within the same lot, the spacing of the markings varied somewhat.  Notice that on the right side of the chips the sets of markings line up but they diverge towards the left.  It appears the stepper motors moving the tooling or the chips were a bit sloppy or out of calibration.

Have you seen any other double engraved comments? Let us know in the comments.

NRAO Radio Telescope

There are many greats of the CPU industry, some, such as Federico Faggin (designer of the 4004 and worked on the 8008, then founded Zilog) are fairly well known.  Others include Gelsinger and Meyer (of x86 fame) perhaps even Gordon Moore, of which a  ‘law’ is named.  Chuck Peddle and Bill Mensch designed the ubiquitous 6502 processor, but there were more, many more. Engineers whose names have been oft forgotten, but whose work has not.  The 1970’s and 80’s were the fast and the furious of processor designs.  Some designs were developed, sold, or canceled in weeks, months; years were not a period of time that was available to these designers, for in a year, a new technology would dictate a new design.

One of these designers is Charles H. Moore. (aka Chuck Moore).  Chuck is perhaps best known for inventing the FORTH programming language in 1968, originally to control telescopes.  It was a stack based language, and lended itself well to small microcomputers and microcontrollers.  Some microcontrollers even embedded a FORTH kernel in ROM.  It was also designed to be able to be ported to different architectures easily.  FORTH continues to be used today for a variety of applications.  However Chuck did not just invent a 1970’s programming language.

Read More »

Usually we find vintage processors here at the CPU Shack Museum, however, from time to time, we get our hands on something very new, and usually significant.  If by significant one means the processor from a Top500 supercomputer then yes, it is significant.

IBM 51Y7638 – Produced Early 2012 – Blue Gene/Q 1.6GHz 18 Core PowerPC-A2

This is a Compute card from an IBM Blue Gene/Q (specifically the 6 rack BG/Q running at England’s Science & Technology Facilities Council Daresbury Lab in Cheshire).  A Blue Gene/Q system is made up of these cards, 32 per ‘Node Card’, and 1024 per rack. This doesn’t count the I/O board which use a similar design and contains 8 Compute cards per rack.

BlueGeneQ ASIC die shot

Each of the Compute cards contains a large ASIC (the large chip in the middle).  This ASIC contains 18 PowerPC-A2 processor cores running at 1.6GHz.  16 of them are ‘User’ cores, 1 is for system management (handles interrupts  message passing, etc) and the 18th is a spare, for increased fault tolerance. The ASIC also contains 32MB of shared L2 cache and a dual 1.3GHz memory controller for the 16GB of DDR3 memory on the card.   All said this 45nm chip contains 1.47 Billion transistors, but only dissipates 55Watts, granted, that adds up when you have thousands of them.

A ‘basic’ system contains 4 racks, so 4096 compute cards (4128 if you count the the I/O boards). Together this is 65,536 user cores and consumes upwards of 85kW of power (this actually makes it one of the most efficient super computers available).

So how do these cards become available?  Simply put when you have so many in a system, statistically you are going to have failures, and somewhat frequently.  IBMs target failure rate, based on a 96 rack system (which is massive) is 70 hours.  That’s one failure  every 3 days.  At this point the common reaction is to express shock at the dismal reliability of such a system, however, lets put it another way, that’s one failure out of 98,000+ Compute cards (yes there are other failure points but for the sake of argument we’re using just the compute cards).  If you run an IT department that services nearly 100,000 computers and you only have to fix something twice a week, there is a good chance you should get a raise.

Mask ROM

Users of the Python programming language often say it can do anything, and that may just be true.  Microcontrollers through out their history have had a variety of ways to store the programs they run.  Unlike a microprocessor, a microcontroller typically has a fixed, or somewhat fixed, program that it runs.  This program is often referred to as firmware (its not software, as its cant easily be changed, and its not hardware as it isn’t discrete chips, thus firmware).

There are several common ways to store firmware:

• UV-EPROM: The microcontroller has a UV-EPROM as part of its die (or in some cases separate but on the same package).  This can be programmed using higher voltages, and erased/updated, albeit not in the field.  This was popular in the 80’s for prototyping work.
• Flash (or EEPROM):  This replaced UV-EPROM program storage as it was update-able in circuit, allowing for such things as user BIOS upgrades, updating firmware on CD/Hard Drives etc.  This has become fairly standard for any firmware that is likely to need to be upgraded in the future.
• 

  Intel B2616 – Unless you clean the paint off

  OTP: One Time Programmable Read Only Memory is useful for medium to large scale production runs.  This allows the code to be ‘burnt’ onto a chip prior to shipping. Often all these were were UV-EPROM chips in a plastic package.  Early Intel’s even used UV-EPROM chips, and simply painted over the window.  a 2708 UV-EPROM became a 2608 PROM with the simple application of some nail polish.  There has been some experimentation and success in erasing/reusing these with the use of X-Rays. (they can penetrate the plastic package).

• Mask ROM: A Mask ROM is just as it sounds, the program code is actually added to the actual mask itself when making the microcontroller die.  This is the most economical  and reliable for very large production runs.  Obviously one wants to make very sure the code is correct before cutting a mask with it, masks are expensive, and manufacturers are not keen on giving do overs.   In 1978 Intel charged $1000 Mask fee, and a minimum order of 100 units for an 8k ROM (~$10).   By 1986 that Mask fee had risen to $3000 and min units to 1000.

So what happens when 20+ years later you need to figure out whats ON a mask ROM?  The paper tape, 8″ floppy or punch card the program original was stored on is long since gone.  Being that its a mask ROM one can actually SEE the connections, so its possible to decap a device, and visually determine the code, albeit with a lot of tedious work.  Adam Laurie of Aperture Labs developed a Python script to automate some of it, and wrote an article explaining it, which covers some every interesting Mask ROM info.  Not to mention some very nice pictures, so check it out.

Click for much larger

Every now and then I will get a chip in that I cannot ID.  This is a particularly perplexing one.  It looks like it should be something fairly well known, but I cannot determine what.  By the dates its a 2005 vintage IBM, MCM, on a fairly large ceramic package with 1077 lands.  It contains a pair of Infineon HYB39S256160DT-7 256Mbit (4Mbitx16bit) DRAMs which are 7ns 143MHz max, commonly used on PC133 SDRAM.   That works out to 64MB.  Also on the package is a IBM0436A8ACLAB 8Mbit (256Kx36) 4.5ns (222MHz) 1Mbyte SRAM.

IBM MCM die

Markings on the die are:
0FE45000L3
AKESXEX0
1 10-10
09K2262

If you have any ideas what it is, or what it may be, post a comment.  I may just give you one.  These came in with a lot of HP PA-RISC processors, so perhaps related?

UPDATE (10/20/2016): Mystery solved. These are processors from a Cadence Palladium emulator system. Read more about them here

PIC17C766/CL ES

If there is anything a Microchip PIC is known for typically ‘large’ is not what comes to mind.  PICs were originally developed in the 1970s as a peripheral controller and ended up finding uses in products of every sort, for 35 years and counting.  The PIC17 series extended the original 12 bit architecture to 16 bits (16 bit instructions, ALU and registers are still 8-bit).  It added many new instructions (58 total) and an 8×8 hardware multiplier. Max clock speed was 33MHz. It was considered the ‘high end’ of the PIC line but now has been replaced by the PIC18 line.  Most of the PIC17s produced were in the 40-68 pin range. Many designers considered the PIC17 to be a less then great processor and in 2000 Microchip replaced it with the much better PIC18 line.

This PIC17C766/CL was one of only 7 variants in the line (17C42,43,44, 752,756,762 and 766) compared to the many dozens in the PIC16 or 18 lines.  Produced in an 84 pin CLCC with UV EPROM window (for its 16k EPROM) the 17C766 provided 66 I/O lines, more then enough for any project.  It was used in some PIC development systems and emulators which were some of the few systems that really needed a PIC with 84 pins.  This particular example also happens to be an Engineering Sample and was produced in mid-2001, AFTER the introduction of the PIC18, it seems there was still at least some demand and use for the PIC17 a decade after its introduction.

Intel 486 With new logo – 2007

Intel introduced the 486 in 1989, 24 years ago so it may be a bit surprising to see a 486 with the more modern Intel non-‘dropped e’ logo.  Intel began using the current logo in 2006, well after the height of the 486 market.  However Intel continued to make several 486 processors clear up through 2007.  These went to supply many embedded applications (medical, industrial, etc) that had originally been designed with a 486 and remained in production.  These types of devices either did not need a better processor or due to regulatory reasons, could not use one.  This is actually a common issue with medical devices, once designed, they are certified by the FDA (in the US, other agencies in the EU, Canada etc).  This certification is very specific to that exact hardware.  Often you cannot even change the S-spec/revision of the processor.  If it was built/certified with an SX911 A80486DX2-66 that’s what it must continue to use.  Re-certification is very expensive and time consuming.  It may seem overkill but these type of applications are often life sustaining, a failure could mean more then a reboot and lost game of Doom.  This is why Intel (and other companies) will choose a few products out of each line to be long-term production, this helps engineers select a product to design into their device, that has a guaranteed production life.  Currently Intel’s long term products guarantee a 7-year production.

Original DX2 Late 1994

This particular chip was made in April 2007. Intel announced it would be discontinued by the end of 2007 so this is truly one of the last (Intel) 486s ever made.  It is a SX911 &E5V2X version which is an SL Enhance (&E) 5 Volt Mobile (2X) processor.  The 2X means that the processor requires 2 external clocks, typically one would be used for when a laptop was plugged in (full speed, 33MHz in this case) and a second, which could be anything lower, for battery operation.  Obviously these can be implemented in any application, not just a laptop.  Registers contents, interrupts  etc are all preserved when the processor switches clock frequency so this is done on the fly, just like today’s processors.  The SX911 spec, which first was released in 1994, came in both 1X (desktop) and 2X (mobile) versions.  Throughout its 13 years of production it remained on a 150mm (6-inch) wafer process at 0.8u.