Understanding ROM Implementation: A Troubleshooting Guide

  • Thread starter Thread starter transgalactic
  • Start date Start date
  • Tags Tags
    Example
Click For Summary

Discussion Overview

The discussion revolves around the implementation and understanding of Read-Only Memory (ROM) in the context of a specific example involving a truth table and its application in circuit design. Participants explore the functionality of ROM, its role in computers, and how to approach a given problem related to its implementation.

Discussion Character

  • Exploratory, Technical explanation, Debate/contested, Homework-related

Main Points Raised

  • One participant expresses confusion about the functionality of ROM in a specific example, despite understanding its general role in computers.
  • Another participant explains that ROM is non-volatile and retains data when the computer is turned off, emphasizing its reliability and primary function in boot programs.
  • A different participant describes ROM as a form of combinatorial logic, where each output line is a boolean function of the address lines, suggesting that the outputs depend on the address inputs.
  • One participant notes that the example provided seems to simplify the ROM implementation by using a large box in a Karnaugh map, questioning if they can create a ROM from the entire setup.

Areas of Agreement / Disagreement

Participants generally agree on the basic properties and functions of ROM, but there is no consensus on how to apply this understanding to the specific example presented. The discussion remains unresolved regarding the implementation details.

Contextual Notes

Some participants highlight the complexity of the example and the need for clarity on how to derive the ROM implementation from the truth table, indicating potential missing assumptions or steps in the problem-solving process.

Who May Find This Useful

Individuals interested in digital logic design, computer architecture, or those studying the implementation of memory systems may find this discussion relevant.

transgalactic
Messages
1,386
Reaction score
0
http://img211.imageshack.us/my.php?image=img86301qt1.jpg

i have a trouble in understanding ROM
i know that it has addresses and words and that its used in computers in order
to store info.

but when i get to the example i can't understand the functionality of it.

in the example that i present here we have a truth table and then
the Rom implementation
in the previos question i knew what the Full Adder does

i knew what its for
so i knew how to use itbut here i can't understand what its doing??

again i don't have any problem to build a KARNO table
and to build a big circuit out of it

but i need to implement ROM here
 
Last edited:
Physics news on Phys.org
Read Only Memory is non-volatile. the data does not go away when you turn the computer off. and being read-only, if some program running in the computer accidently starts executing random (and bad) instructions and tries to write to the ROM, the data in the ROM will not change. so that data in the ROM is safe. it's always there and can be counted on to be there (unless you smoke the chip or a static discharge or similar).

the main function of ROM is for the boot program (what the CPU executes when the reset line is toggled) and enough drivers in it to be able to grab the next bunch of code to be executed. some computers will have other drivers or utilities (that know how to talk to other hardware devices) that applications might use, but often those are saved on the disk (or other writable and non-volatile memory) so they can be updated with new versions with bugs fixed or additional functionality.

ROMs can also be thought of as a fixed logic gate array. for each data line out, it can be defined as any static logical combination of the address lines going in. it's the same thing (but i think a ROM is slower than a PLA or PAL or whatever they call it) as a big mess of logic with no states (flip-flops) inside.
 
so how can i solve this question??

i understand the role ROM plays in our PC's
but that doesn't help me much in solving this example
 
Last edited:
listen, all ROMs are, are a piece of arbitrary combinatoric logic (without states inside).

name your data (out) line, let's say D5. so D5 is some boolean function of A0, A1, A2, A3... (all of the address lines). for each permutation of address bits, from 00000000 to 11111111, the data bits are all some function that turns on the data bit (or turns it off) depending on which address word was applied.
 

Similar threads

Replies
2
Views
2K
  • · Replies 7 ·
Replies
7
Views
3K
  • · Replies 4 ·
Replies
4
Views
3K
  • · Replies 2 ·
Replies
2
Views
4K
  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 15 ·
Replies
15
Views
3K
  • · Replies 4 ·
Replies
4
Views
3K
  • · Replies 1 ·
Replies
1
Views
5K
Replies
11
Views
3K