Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi, I have one question regarding Transmit and Receive state machine for Clause 24. As per Figure 24-8 - Transmit State Diagram , once device enters in TX_SLEEP from IDLE , it should transmit SLEEP code groups (tx_bits[4:0]= 5'b0000). As per Figure 24-11a - Receive State Diagram , receiver can enter in RX_SLEEP from IDENTIFY_JK if it receives (/I/P) . As Transmitter enters in TX_SLEEP directly from IDLE and will start sending SLEEP code groups, while receiver is expecting (/I/J) as receiver can go to RX_SLEEP from IDENTIFY_JK or BAD_SSD state only i.e. before receiver transit it's state to RX_SLEEP , it must have received /I/J/ pattern, but as Transmitter in TX_SLEEP state is sending SLEEP code groups, receiver will never receive /I/J/ so in this case receiver can only enter in RX_SLEEP through BAD_SSD state, as condition from transition to RX_SLEEP from BAD_SSD is rx_bits[9:0] = /P/P. So my question is - what is the correct flow of normal state transition for receiver - IDLE -> CARRIER_DETECT -> IDENTIFY_JK -> RX_SLEEP or IDLE -> CARRIER_DETECT -> BAD_SSD -> RX_SLEEP ? --
Regards, Nishith Shukla --
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
|