harvard-architecture
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| harvard-architecture [May 16, 2026 at 17:35] – created Ivan Janevski | harvard-architecture [May 16, 2026 at 17:56] (current) – Ivan Janevski | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| # Harvard architecture | # Harvard architecture | ||
| - | **Harvard archictecture** is a computer archictecture | + | **Harvard archictecture** is a type of computer archictecture. It's a type of architecture where code and data are kept in separate memories. |
| + | |||
| + | The Harvard architecture can be contrasted against von-Neumann archictecture. In the latter, code and data are both stored in the same working memory (RAM). The CPU has to fetch both the instructions and data by accessing the same memory bus, leading to what is known as von-Neumann bottleneck. This doesn' | ||
| + | |||
| + | For comparison, Harvard architecture splits data and code into two different memories. For example, data can be stored in RAM or EEPROM, while code is stored in flash memory. This makes it popular in microcontrollers (MCUs) like PIC. You flash an MCU once and it always behaves the same way. The MCU usually has no way to modify its own code so it's slightly more immune to errors and hacking. | ||
harvard-architecture.1778952935.txt.gz · Last modified: by Ivan Janevski
