About microprocessor 8085: state signals?

  • Thread starter Thread starter ilconformista
  • Start date Start date
  • Tags Tags
    Signals State
AI Thread Summary
The discussion centers around the function of the S0, S1, and IO/M* state signals in the 8085AH microprocessor. S0 and S1 indicate the type of machine cycle, such as OpCode Fetch, with specific values assigned to each state (e.g., S1=S0=1 for fetch). The processor uses these signals, determined by the instruction decoder, to indicate whether it is in a halt, read, write, or fetch state. While some participants express confusion about the utility of S0 and S1, it is noted that they can be used to enhance functionality, such as extending address space by addressing ROM instead of main memory. Additionally, S0 and S1 can be leveraged for creating visual indicators like a "blinking light" front panel or for building a hardware debugger that allows control of the processor based on observed signal combinations.
ilconformista
Messages
18
Reaction score
0
Hello everyone! Could anyone explain to me the following: The 8085AH has 3 state signals: S0, S1 and IO/M*. S0 and S1 provide different type of machine cycles depending on their status.

For example if the machine cycle is OpCode Fetch, we will get: S1=S0=1 and IO/M*=0. I don't get it though, what do the S1 and S0 signals actually do? I believe the processor decides their status with the help of the instruction decoder, and then what happens? They don't seem to connect to anything!

Thank you for your time.
 

Attachments

  • preview_html_m301a4067.png
    preview_html_m301a4067.png
    15 KB · Views: 710
Technology news on Phys.org
Code:
s0 s1
 0  0  halt
 0  1  read
 1  0  write
 1  1  fetch

Link to pdf file:

http://staff.neu.edu.tr/~kuyar/301/ch3.pdf
 
Last edited by a moderator:
rcgldr, thanks four your answer! However I still can't think of any way that these signals are useful. The processor decides first if it's halt, read, write or fetch (by decoding the instruction) and THEN updates the states of S0 and S1. Am I right?
 
ilconformista said:
rcgldr, thanks four your answer! However I still can't think of any way that these signals are useful. The processor decides first if it's halt, read, write or fetch (by decoding the instruction) and THEN updates the states of S0 and S1. Am I right?
S0 and S1 don't have to be used, since there are already other signals for read and write. Fetch will occur when reading instructions. If a program was coded carefully, fetch could be used to address some type of rom instead of main memory, effectively extending the address space. S0 and S1 are updated before a memory operation takes place.
 
You could use S0 and S1 and some of the other status lines to create a "blinking light" front panel that would show what the processor is doing. It might be feasible to single step the processor one button press at a time and this would let you watch the status signals, address lines, data lines, etc.

You could use S0 and S1 to build a hardware debugger that would allow you to stop the processor and grab control with a particular combination was observed.
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
Back
Top