The original first generation of Amigas such as the A500, A600, A1000 and A2000 all used a Motorola designed 68000 CPU inside. Many Amiga users eventually upgraded theirs to have an accelerator, usually based on the 68020 or 68030 CPU. But there is a contender that is a drop-in replacement for the 68000, and for some things it can be quite a bit faster.
The 68010 is a minor revision to the standard 68000, it includes a few fixes, but also a few features. The majority of these are around rudimentary memory virtualisation, this is useful for users of WHDLoad in particular as it allows the key to break out of games to work properly.
On top of this was another feature called “loop mode”. This was basically a CPU cache that would work for pieces of code that ran loops with a single instruction within the loop. For example, moving blocks of memory around. These loops would be around 50% faster as a result of this.
When seen in benchmarks, this only equates to a small increase, only around 10%. But in certain games the performance increase is quite visible. Many games by the Bitmap Brothers were coded so that as much code as possible would be portable between platforms. For the 68000 CPU this meant that it had to run on Atari ST as well as Amiga. The two platforms did not have the same custom chipset, so these ended up very CPU heavy games. As such they typically benefit from a 68010 when there are a lot of sprites on the screen.
The video example below shows Xenon II running on my Commodore CDTV with both a 68000 and a 68010. In the intro you can see the 68000 starting to run a few frames behind, but when I’m playing a section of the game with lots of sprites the slowdown is very noticeable for the 68000. The game runs quite smooth throughout on the 68010, this is even more noticeable when playing the game.
I recently acquired an Amiga 1200 motherboard in a spares/repairs condition for about £100 recently.…
Whilst I do like working with STM32 development boards, some basic information I need can…
When I last left this blog series, the first of Stoo Cambridge's A4000s had gone…
At the beginning of November, I started working for wolfSSL. Now that I'm a week…
In my previous post, I had the Amiga 4000 known as Jools mostly repaired, there…
In my last post, I created a list of things I needed to repair on…
View Comments
Minor mistake early in article...
"a drop-in replacement for the 68010" should be 68000
Another...
"The 68010 is a minor revision to the standard 68010"
Thanks, corrected both things. Typing the numbers in a lot caused me to start mixing them up :)
Hi. Too bad that some demos do not work with a 68010 in the Amiga 500, like Razor 1911’s Voyage. I didn’t notice it was that faster when I had one, before my Pistorm’X.
Most demos use custom chips quite heavily rather, so the features of the 68010 would probably not help.
Great article. These loops would be around 50%… needs to say faster.
Good call, fixed! :)
Nice, but... why do you write in past tense? Have all Amiga 500s suddenly blown up? Has "loop mode" all of the sudden stopped working?
Also, "the key to break out of games to work properly" is really hard to understand. Escaping keys?
Finally, links to some reliable resources selling 68010 CPUs would be useful for all readers. Thank you.
Hi,
Past tense for the items because they are no longer manufactured. For the tests because they are finished.
I welcome a suggestion for a replacement for the sentence you couldn't parse.
I do not know a reliable source of 68010s with which I'm confident enough in them to promote. Certainly not one that would be around longer term.
Actually your video doesn't explain theoretical advantages 68010... Too short... I can't say if any of CPU better
You'll see on the 68000 that the frame rate drops quite significantly when there are lots of sprites, particularly at the 1 minute mark of the video. This doesn't happen on the 68010. You can definitely feel the difference when playing the game.
You are of course welcome to make a longer comparison video. I had time constraints as to how long I could spend capturing and editing.