Why was CPU32 core created, and how is it different from 680x0 CPU cores?Why is the Amiga ROM at a high memory location, and RAM in low memory?How did the original Apple Macintosh and Atari ST use protected mode?What limited the use of the Z8000 (vs. 68K and 8086) CPU for 16-bit computers?What was Burst Mode on the 68030 and why didn't the A2630 support it?How does states, bus cycles and clock cycles differ in the M68000?
Shouldn't the "credit score" prevent Americans from going deeper and deeper into personal debt?
Would it be possible to have a GMO that produces chocolate?
When translating the law, who ensures that the wording does not change the meaning of the law?
Vacuum collapse -- why do strong metals implode but glass doesn't?
What is the appropriate benchmark for a Long/Short VIX futures strategy?
How to refer to a regex group in awk regex?
What is this symbol: semicircles facing eachother
On the feasibility of space battleships
Was Switzerland really impossible to invade during WW2?
Why aren't RCS openings an issue for spacecraft heat shields?
Why did MS-DOS applications built using Turbo Pascal fail to start with a division by zero error on faster systems?
Fancy String Replace
Is it possible to create a golf ball sized star?
Why didn’t Doctor Strange stay in the original winning timeline?
What to say to a student who has failed?
Is a butterfly one or two animals?
How much code would a codegolf golf if a codegolf could golf code?
Brexit and backstop: would changes require unanimous approval by all EU countries? Does Ireland hold a veto?
confused about grep and the * wildcard
How to write triplets in 4/4 time without using a 3 on top of the notes all the time
Defense against attacks using dictionaries
Is refusing to concede in the face of an unstoppable Nexus combo punishable?
IndexOptimize - Configuration
Is there such a thing as too inconvenient?
Why was CPU32 core created, and how is it different from 680x0 CPU cores?
Why is the Amiga ROM at a high memory location, and RAM in low memory?How did the original Apple Macintosh and Atari ST use protected mode?What limited the use of the Z8000 (vs. 68K and 8086) CPU for 16-bit computers?What was Burst Mode on the 68030 and why didn't the A2630 support it?How does states, bus cycles and clock cycles differ in the M68000?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am doing a design based on the Motorola 68332 MCU made for embedded applications, which is based on the CPU32 core. The CPU32 core is very similar to the 680x0 CPUs, but there are some subtle differences that I need to know. So for a better understanding, I would like to hear if anybody can help with the questions below.
Why was CPU32 core created, when Motorola had the 680x0 CPU cores already ?
The "M68000 FAMILY PROGRAMMER’S REFERENCE MANUAL" points out a large number of differences between the 680x0 and the CPU32, but the differences are scattered over a long document.
Does anybody know a description of only the differences between a 680x0 CPU core and the CPU32 core?
motorola-68000 motorola-680x0
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
add a comment |
I am doing a design based on the Motorola 68332 MCU made for embedded applications, which is based on the CPU32 core. The CPU32 core is very similar to the 680x0 CPUs, but there are some subtle differences that I need to know. So for a better understanding, I would like to hear if anybody can help with the questions below.
Why was CPU32 core created, when Motorola had the 680x0 CPU cores already ?
The "M68000 FAMILY PROGRAMMER’S REFERENCE MANUAL" points out a large number of differences between the 680x0 and the CPU32, but the differences are scattered over a long document.
Does anybody know a description of only the differences between a 680x0 CPU core and the CPU32 core?
motorola-68000 motorola-680x0
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
add a comment |
I am doing a design based on the Motorola 68332 MCU made for embedded applications, which is based on the CPU32 core. The CPU32 core is very similar to the 680x0 CPUs, but there are some subtle differences that I need to know. So for a better understanding, I would like to hear if anybody can help with the questions below.
Why was CPU32 core created, when Motorola had the 680x0 CPU cores already ?
The "M68000 FAMILY PROGRAMMER’S REFERENCE MANUAL" points out a large number of differences between the 680x0 and the CPU32, but the differences are scattered over a long document.
Does anybody know a description of only the differences between a 680x0 CPU core and the CPU32 core?
motorola-68000 motorola-680x0
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
I am doing a design based on the Motorola 68332 MCU made for embedded applications, which is based on the CPU32 core. The CPU32 core is very similar to the 680x0 CPUs, but there are some subtle differences that I need to know. So for a better understanding, I would like to hear if anybody can help with the questions below.
Why was CPU32 core created, when Motorola had the 680x0 CPU cores already ?
The "M68000 FAMILY PROGRAMMER’S REFERENCE MANUAL" points out a large number of differences between the 680x0 and the CPU32, but the differences are scattered over a long document.
Does anybody know a description of only the differences between a 680x0 CPU core and the CPU32 core?
motorola-68000 motorola-680x0
motorola-68000 motorola-680x0
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
asked Aug 9 at 7:06
EquipDevEquipDev
1584 bronze badges
1584 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I can suggest why it was created. The Wikipedia page for CPU32 says:
The instruction set of the CPU32 core is similar to the 68020 without bitfield instructions, and with a few instructions unique to the CPU32 core, such as table lookup and interpolate instructions, and a low-power stop mode.
The objective for CPU32 seems to have been a processor for embedded uses, rather than a powerful minicomputer/workstation processor, which was the original objective of the 68000. The most important requirement for an embedded processor is usually low cost, followed by low power consumption.
In the 1970s, when the 68000 was first created, bit-field instructions were a popular concept in CISC architectures: the DEC VAX is another example. They've become essentially obsolete in the light of experience with RISC architectures, so taking them out to save chip area, and thus cost, for the CPU32 is reasonable. That makes it no longer 68000-software-compatible, and thus allows more changes to the instruction set.
The table lookup and interpolate instructions are useful for a common trick with embedded systems. Rather than running a complex algorithm, pre-compute its value for a range of inputs, and then use lookups and interpolations.
The low-power stop instruction is definitely for power saving, and is one of the simplest means for that: having a processor consume power when it has no work to do is deadly for battery-powered devices.
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
1
Thanks, so it sounds like the CPU32 is maybe a branch from the 68020 design, and not a brand new design. The CPU32 name was then maybe chosen to indicate that it breaks with the compatibility line of the 680x0 series.
– EquipDev
Aug 9 at 8:38
1
Table lookup will have little to do with streaming media. Lookup tables are very common with embedded systems. Rather than process some complex algorithm you just calculate a table of values before hand and then look one up, or look two up an interpolate. It's much faster in most cases.
– user
Aug 9 at 8:52
4
The story I was told was that the Dragonball design for Palm Pilots mutated into CPU32 as Motorola realised there was a market for embedded M68K SoC designs. I may have an original 68302 reference book somewhere which I think predates the introduction of CPU32 as an idea.
– PeterI
Aug 9 at 11:27
1
@user: Revised - is this accurate?
– John Dallman
Aug 9 at 17:34
@JohnDallman Yep, better.
– user
Aug 10 at 14:33
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "648"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f11986%2fwhy-was-cpu32-core-created-and-how-is-it-different-from-680x0-cpu-cores%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I can suggest why it was created. The Wikipedia page for CPU32 says:
The instruction set of the CPU32 core is similar to the 68020 without bitfield instructions, and with a few instructions unique to the CPU32 core, such as table lookup and interpolate instructions, and a low-power stop mode.
The objective for CPU32 seems to have been a processor for embedded uses, rather than a powerful minicomputer/workstation processor, which was the original objective of the 68000. The most important requirement for an embedded processor is usually low cost, followed by low power consumption.
In the 1970s, when the 68000 was first created, bit-field instructions were a popular concept in CISC architectures: the DEC VAX is another example. They've become essentially obsolete in the light of experience with RISC architectures, so taking them out to save chip area, and thus cost, for the CPU32 is reasonable. That makes it no longer 68000-software-compatible, and thus allows more changes to the instruction set.
The table lookup and interpolate instructions are useful for a common trick with embedded systems. Rather than running a complex algorithm, pre-compute its value for a range of inputs, and then use lookups and interpolations.
The low-power stop instruction is definitely for power saving, and is one of the simplest means for that: having a processor consume power when it has no work to do is deadly for battery-powered devices.
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
1
Thanks, so it sounds like the CPU32 is maybe a branch from the 68020 design, and not a brand new design. The CPU32 name was then maybe chosen to indicate that it breaks with the compatibility line of the 680x0 series.
– EquipDev
Aug 9 at 8:38
1
Table lookup will have little to do with streaming media. Lookup tables are very common with embedded systems. Rather than process some complex algorithm you just calculate a table of values before hand and then look one up, or look two up an interpolate. It's much faster in most cases.
– user
Aug 9 at 8:52
4
The story I was told was that the Dragonball design for Palm Pilots mutated into CPU32 as Motorola realised there was a market for embedded M68K SoC designs. I may have an original 68302 reference book somewhere which I think predates the introduction of CPU32 as an idea.
– PeterI
Aug 9 at 11:27
1
@user: Revised - is this accurate?
– John Dallman
Aug 9 at 17:34
@JohnDallman Yep, better.
– user
Aug 10 at 14:33
add a comment |
I can suggest why it was created. The Wikipedia page for CPU32 says:
The instruction set of the CPU32 core is similar to the 68020 without bitfield instructions, and with a few instructions unique to the CPU32 core, such as table lookup and interpolate instructions, and a low-power stop mode.
The objective for CPU32 seems to have been a processor for embedded uses, rather than a powerful minicomputer/workstation processor, which was the original objective of the 68000. The most important requirement for an embedded processor is usually low cost, followed by low power consumption.
In the 1970s, when the 68000 was first created, bit-field instructions were a popular concept in CISC architectures: the DEC VAX is another example. They've become essentially obsolete in the light of experience with RISC architectures, so taking them out to save chip area, and thus cost, for the CPU32 is reasonable. That makes it no longer 68000-software-compatible, and thus allows more changes to the instruction set.
The table lookup and interpolate instructions are useful for a common trick with embedded systems. Rather than running a complex algorithm, pre-compute its value for a range of inputs, and then use lookups and interpolations.
The low-power stop instruction is definitely for power saving, and is one of the simplest means for that: having a processor consume power when it has no work to do is deadly for battery-powered devices.
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
1
Thanks, so it sounds like the CPU32 is maybe a branch from the 68020 design, and not a brand new design. The CPU32 name was then maybe chosen to indicate that it breaks with the compatibility line of the 680x0 series.
– EquipDev
Aug 9 at 8:38
1
Table lookup will have little to do with streaming media. Lookup tables are very common with embedded systems. Rather than process some complex algorithm you just calculate a table of values before hand and then look one up, or look two up an interpolate. It's much faster in most cases.
– user
Aug 9 at 8:52
4
The story I was told was that the Dragonball design for Palm Pilots mutated into CPU32 as Motorola realised there was a market for embedded M68K SoC designs. I may have an original 68302 reference book somewhere which I think predates the introduction of CPU32 as an idea.
– PeterI
Aug 9 at 11:27
1
@user: Revised - is this accurate?
– John Dallman
Aug 9 at 17:34
@JohnDallman Yep, better.
– user
Aug 10 at 14:33
add a comment |
I can suggest why it was created. The Wikipedia page for CPU32 says:
The instruction set of the CPU32 core is similar to the 68020 without bitfield instructions, and with a few instructions unique to the CPU32 core, such as table lookup and interpolate instructions, and a low-power stop mode.
The objective for CPU32 seems to have been a processor for embedded uses, rather than a powerful minicomputer/workstation processor, which was the original objective of the 68000. The most important requirement for an embedded processor is usually low cost, followed by low power consumption.
In the 1970s, when the 68000 was first created, bit-field instructions were a popular concept in CISC architectures: the DEC VAX is another example. They've become essentially obsolete in the light of experience with RISC architectures, so taking them out to save chip area, and thus cost, for the CPU32 is reasonable. That makes it no longer 68000-software-compatible, and thus allows more changes to the instruction set.
The table lookup and interpolate instructions are useful for a common trick with embedded systems. Rather than running a complex algorithm, pre-compute its value for a range of inputs, and then use lookups and interpolations.
The low-power stop instruction is definitely for power saving, and is one of the simplest means for that: having a processor consume power when it has no work to do is deadly for battery-powered devices.
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
I can suggest why it was created. The Wikipedia page for CPU32 says:
The instruction set of the CPU32 core is similar to the 68020 without bitfield instructions, and with a few instructions unique to the CPU32 core, such as table lookup and interpolate instructions, and a low-power stop mode.
The objective for CPU32 seems to have been a processor for embedded uses, rather than a powerful minicomputer/workstation processor, which was the original objective of the 68000. The most important requirement for an embedded processor is usually low cost, followed by low power consumption.
In the 1970s, when the 68000 was first created, bit-field instructions were a popular concept in CISC architectures: the DEC VAX is another example. They've become essentially obsolete in the light of experience with RISC architectures, so taking them out to save chip area, and thus cost, for the CPU32 is reasonable. That makes it no longer 68000-software-compatible, and thus allows more changes to the instruction set.
The table lookup and interpolate instructions are useful for a common trick with embedded systems. Rather than running a complex algorithm, pre-compute its value for a range of inputs, and then use lookups and interpolations.
The low-power stop instruction is definitely for power saving, and is one of the simplest means for that: having a processor consume power when it has no work to do is deadly for battery-powered devices.
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
edited Aug 9 at 17:33
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
answered Aug 9 at 7:47
John DallmanJohn Dallman
4,6841 gold badge13 silver badges20 bronze badges
4,6841 gold badge13 silver badges20 bronze badges
1
Thanks, so it sounds like the CPU32 is maybe a branch from the 68020 design, and not a brand new design. The CPU32 name was then maybe chosen to indicate that it breaks with the compatibility line of the 680x0 series.
– EquipDev
Aug 9 at 8:38
1
Table lookup will have little to do with streaming media. Lookup tables are very common with embedded systems. Rather than process some complex algorithm you just calculate a table of values before hand and then look one up, or look two up an interpolate. It's much faster in most cases.
– user
Aug 9 at 8:52
4
The story I was told was that the Dragonball design for Palm Pilots mutated into CPU32 as Motorola realised there was a market for embedded M68K SoC designs. I may have an original 68302 reference book somewhere which I think predates the introduction of CPU32 as an idea.
– PeterI
Aug 9 at 11:27
1
@user: Revised - is this accurate?
– John Dallman
Aug 9 at 17:34
@JohnDallman Yep, better.
– user
Aug 10 at 14:33
add a comment |
1
Thanks, so it sounds like the CPU32 is maybe a branch from the 68020 design, and not a brand new design. The CPU32 name was then maybe chosen to indicate that it breaks with the compatibility line of the 680x0 series.
– EquipDev
Aug 9 at 8:38
1
Table lookup will have little to do with streaming media. Lookup tables are very common with embedded systems. Rather than process some complex algorithm you just calculate a table of values before hand and then look one up, or look two up an interpolate. It's much faster in most cases.
– user
Aug 9 at 8:52
4
The story I was told was that the Dragonball design for Palm Pilots mutated into CPU32 as Motorola realised there was a market for embedded M68K SoC designs. I may have an original 68302 reference book somewhere which I think predates the introduction of CPU32 as an idea.
– PeterI
Aug 9 at 11:27
1
@user: Revised - is this accurate?
– John Dallman
Aug 9 at 17:34
@JohnDallman Yep, better.
– user
Aug 10 at 14:33
1
1
Thanks, so it sounds like the CPU32 is maybe a branch from the 68020 design, and not a brand new design. The CPU32 name was then maybe chosen to indicate that it breaks with the compatibility line of the 680x0 series.
– EquipDev
Aug 9 at 8:38
Thanks, so it sounds like the CPU32 is maybe a branch from the 68020 design, and not a brand new design. The CPU32 name was then maybe chosen to indicate that it breaks with the compatibility line of the 680x0 series.
– EquipDev
Aug 9 at 8:38
1
1
Table lookup will have little to do with streaming media. Lookup tables are very common with embedded systems. Rather than process some complex algorithm you just calculate a table of values before hand and then look one up, or look two up an interpolate. It's much faster in most cases.
– user
Aug 9 at 8:52
Table lookup will have little to do with streaming media. Lookup tables are very common with embedded systems. Rather than process some complex algorithm you just calculate a table of values before hand and then look one up, or look two up an interpolate. It's much faster in most cases.
– user
Aug 9 at 8:52
4
4
The story I was told was that the Dragonball design for Palm Pilots mutated into CPU32 as Motorola realised there was a market for embedded M68K SoC designs. I may have an original 68302 reference book somewhere which I think predates the introduction of CPU32 as an idea.
– PeterI
Aug 9 at 11:27
The story I was told was that the Dragonball design for Palm Pilots mutated into CPU32 as Motorola realised there was a market for embedded M68K SoC designs. I may have an original 68302 reference book somewhere which I think predates the introduction of CPU32 as an idea.
– PeterI
Aug 9 at 11:27
1
1
@user: Revised - is this accurate?
– John Dallman
Aug 9 at 17:34
@user: Revised - is this accurate?
– John Dallman
Aug 9 at 17:34
@JohnDallman Yep, better.
– user
Aug 10 at 14:33
@JohnDallman Yep, better.
– user
Aug 10 at 14:33
add a comment |
Thanks for contributing an answer to Retrocomputing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f11986%2fwhy-was-cpu32-core-created-and-how-is-it-different-from-680x0-cpu-cores%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
