Live data from Hacker News

The Visual ARM1

blog.visual6502.org

11–16 of 16 posts

Re: The Visual ARM1

#11

This is probably really amazing if you know what you're looking at. I have no idea what any of the parts do and what code is being run. I would love to see someone give a "guided tour" though all the parts of the CPU, and step through some assembly to see how the things works. I can see from the picture there are distinct areas, and large arrays of gates that might be memory or adders or I don;t know. It would be ama…

You could try to work through "Code, the hidden language" http://www.charlespetzold.com/code/

EDIT: The Art of Electronics has an accompanying book called the Student Manual, which will walk you through the process of (eventually) building a small computer.

Re: The Visual ARM1

#13
slightly off topic, but...

> Credit goes to ... Lee Smith for spotting the variable record format used to encode the file (an artifact of the VMS on Acorn's VAX that at first appeared to be widespread corruption of the file),

These days, thanks to Unix and C I suppose, a file is just a collection of bytes. That wasn't always the case. Consider Pascal, where a file is a file of something (records, integers, etc).

So, on VMS, you had streaming files (just a collection of bytes) but also RMS -- Record Management System -- files, which were files of records. There were fixed length records (the record size was probably stored in the file metadata) and variable size records (record size was stored inline, as a byte or word prefix before the record). You might think you're just writing data to a file, but you're writing records (the OS adds the prefix for variable records or 0-pads for fixed length). Then when reading, you might request xx bytes but it will only read one record at a time. (Kind of like how fgets() will stop reading when it finds a newline or a tcp socket will stop reading when it finds a PUSH.)

There are advantages and disadvantages to this but if you're dealing with a VMS RMS file, you need to be aware or it will look corrupted.

Re: The Visual ARM1

#15
I'm amazed at how small and (relatively) simple it all looks, that you can literally see the registers on that picture. Just 25K transistors for a whole 32-bit CPU with a 3-stage pipeline.

For those who would like a bit more detail about the feature of this CPU: http://everything2.com/title/ARM1

One thing I was curious to know is whether the ARM1 had a hardware multiply instruction, whether they could fit that in this tiny CPU. It does not.

Re: The Visual ARM1

#16

I'm amazed at how small and (relatively) simple it all looks, that you can literally see the registers on that picture. Just 25K transistors for a whole 32-bit CPU with a 3-stage pipeline. For those who would like a bit more detail about the feature of this CPU: http://everything2.com/title/ARM1 One thing I was curious to know is whether the ARM1 had a hardware multiply instruction, whether they could fit that in thi…

ARM2 had hardware multiply & more shadow registers and came in at 30k transistors according to Wikipedia. Everything2 thinks the ARM2 came in at just over 25k transistors though, with the ARM1 using less than 25k.
Post reply on HN