The Developing Dev · Software Engineering & Infra · November 2026
Furber recalls a 1983 visit to the company designing the 6502's successor. Seeing how small the operation was made chip design look less intimidating, and helped convince Acorn's first-time team to design what became the ARM processor.
…ARM chip had a three-level pipeline, which meant it could do fetch, decode, execute, and complete one instruction per tick. Not all the instructions were single tick, but most were. And yeah, it's just a lot of the industry was slow to recognize this and then slow to work out what to do with it.
When you were deciding. To build ARM. I understand that when you also visited America. What was the difference in the work cultures in computing between the UK and the US and your perspective?
Our visit to the States, I think was in October 83, was to the Western Design Center in Phoenix, Arizona, where I think it was just Sophie and I went and we were expecting to find the usual gleaming American business office block. And what we found was the Western Design Center was operating out of two bungalows in the Phoenix suburbs. These bungalows had some fairly unusual equipment around them, but they were getting school kids in over the summer to design cell libraries. And our main interest there was they were developing a successor to the 6502, which was the 65C816, if I remember right, which had a bit of an address extension, so it would address more memory than the 6502. And Acorn did use that in some of their products subsequent to the BBC Micro. But it wasn't the big step forward, it was an incremental improvement. And we came away from seeing those bungalows, which were sort of much less professional than we were anticipating, let's put it that way. And that was one of the things that the causes think, well, if they can design a processor, maybe we can too.
Did Acorn ever consider building their own fab for these chips?
No.
And why is that?