Talk:MCS-51: Difference between revisions
No edit summary |
|||
| Line 17: | Line 17: | ||
The 8051 is considered a Harvard Architecture machine because it has separate code and data spaces. Depending on the implementation however, it can be either Harvard or von-neumann. Older versions of the 8051 are more often van-neumann in that the CPU takes several clock cycles to fetch each operand/instruction individually. Newer single-cycle 8051s are often Harvard so they can get higher performance. The Harvard architecture allows the Instruction and the operands to be fetched in the same cycle. [[Special:Contributions/68.189.241.68|68.189.241.68]] ([[User talk:68.189.241.68|talk]]) 14:28, 24 February 2008 (UTC) |
The 8051 is considered a Harvard Architecture machine because it has separate code and data spaces. Depending on the implementation however, it can be either Harvard or von-neumann. Older versions of the 8051 are more often van-neumann in that the CPU takes several clock cycles to fetch each operand/instruction individually. Newer single-cycle 8051s are often Harvard so they can get higher performance. The Harvard architecture allows the Instruction and the operands to be fetched in the same cycle. [[Special:Contributions/68.189.241.68|68.189.241.68]] ([[User talk:68.189.241.68|talk]]) 14:28, 24 February 2008 (UTC) |
||
:At least with the ROM based variants, the original 8051 could be considered Harvard (and was described as such in the microprocessors course I took in college) in that you could not read from the program address space with normal data read instructions. It was its own address space, and one presumes there was a separate, dedicated path for program fetches. There are special "table lookup" instructions that allow you to read data from the program space, though. Also, on external fetches, the original 8051 CPU would indicate whether it was fetching program or data, so you could continue to keep those address spaces separate even for external memory. That said, once accesses go over the external bus, program and data busses are merged and so are no longer separate busses, and so it does look von Neumann-ish at that point. If a given design ignores the program/data indicator, the two address spaces merge for those external fetches, like in any other von Neumann-style architecture. Note that I limit my comments to the original 8051. I haven't used any of the modern variants so I cannot comment on them. --[[User:Mr z|Mr z]] ([[User talk:Mr z|talk]]) 07:03, 3 September 2008 (UTC) |
:At least with the ROM based variants, the original 8051 could be considered Harvard (and was described as such in the microprocessors course I took in college) in that you could not read from the program address space with normal data read instructions. It was its own address space, and one presumes there was a separate, dedicated path for program fetches. There are special "table lookup" instructions that allow you to read data from the program space, though. Also, on external fetches, the original 8051 CPU would indicate whether it was fetching program or data, so you could continue to keep those address spaces separate even for external memory. That said, once accesses go over the external bus, program and data busses are merged and so are no longer separate busses, and so it does look von Neumann-ish at that point. If a given design ignores the program/data indicator, the two address spaces merge for those external fetches, like in any other von Neumann-style architecture. Note that I limit my comments to the original 8051. I haven't used any of the modern variants so I cannot comment on them. --[[User:Mr z|Mr z]] ([[User talk:Mr z|talk]]) 07:03, 3 September 2008 (UTC) |
||
8051 has a von Neumann architecture nad not the Harvard architecture |
|||
Revision as of 19:32, 7 December 2008
 | Computing Unassessed | |||||||||
| ||||||||||
64k of memory, eh?
How is it possible to adress 64k each of RAM and ROM (that would equal 128k in total) with a 16 bit adress bus? Is there a line on the control bus or something to deal with a simple bank-switch kind of thing? Wilsonsamm (talk) 20:08, 2 October 2008 (UTC)
The 8051 has a Harvard architecture. Please follow the corresponding link in the article. --89.15.178.202 (talk) 20:48, 26 November 2008 (UTC)
8051 architecture
Is 8051 a CISC or RISC machine? Is 8051 a Harvard architecture? —The preceding unsigned comment was added by 61.17.44.86 (talk) 08:05, 29 January 2007 (UTC).
The 8051 is defintiely a CISC machine. It's instruction set is wide and varied with lots of addressing modes and only a few registers. RISC machines typically have a much smaller instruction set and a bank of 16 or 32 registers. RISC machines typically only operate on data in the registers and have a "load/store" architecture. The 8051 instruction set mostly operates on the Accumulator and values in memory. Thus, the 8051 is CISC.
The 8051 is considered a Harvard Architecture machine because it has separate code and data spaces. Depending on the implementation however, it can be either Harvard or von-neumann. Older versions of the 8051 are more often van-neumann in that the CPU takes several clock cycles to fetch each operand/instruction individually. Newer single-cycle 8051s are often Harvard so they can get higher performance. The Harvard architecture allows the Instruction and the operands to be fetched in the same cycle. 68.189.241.68 (talk) 14:28, 24 February 2008 (UTC)
- At least with the ROM based variants, the original 8051 could be considered Harvard (and was described as such in the microprocessors course I took in college) in that you could not read from the program address space with normal data read instructions. It was its own address space, and one presumes there was a separate, dedicated path for program fetches. There are special "table lookup" instructions that allow you to read data from the program space, though. Also, on external fetches, the original 8051 CPU would indicate whether it was fetching program or data, so you could continue to keep those address spaces separate even for external memory. That said, once accesses go over the external bus, program and data busses are merged and so are no longer separate busses, and so it does look von Neumann-ish at that point. If a given design ignores the program/data indicator, the two address spaces merge for those external fetches, like in any other von Neumann-style architecture. Note that I limit my comments to the original 8051. I haven't used any of the modern variants so I cannot comment on them. --Mr z (talk) 07:03, 3 September 2008 (UTC)
8051 has a von Neumann architecture nad not the Harvard architecture