Z85233 Datasheet, PDF (315/317 Pages) Zilog, Inc. – The Zilog SCC Serial Communication Controller

SCC™/ESCC™ User’s Manual
Zilog SCC
MISCELLANEOUS QUESTIONS
Q. Can the SCC support MARK and SPACE parity in
async?
A. The SCC can transmit-end the equivalent of MARK par-
ity by setting WR4 to select two STOP bits. The receiv-
er always checks for only one STOP bit; therefore, the
receiver does not verify the MARK parity bit.
The SCC (and products using the SCC cell) does notsup-
port SPAC parity for transmitting or receiving. The
Zilog USC Family of serial datacom controllers do sup-
port odd, even, mark, & space parity types.
Q. Since both D7 and D1 bits in RR0 are not latched,
it is possible that the receiver detected an Abort
condition, set D7 to 1, initiated an external/status
interrupt and before the processor entered the ser-
vice routine, termination of the abort was detect-
ed, which reset the Break Abort bit . Currently in
the TM (page 7-20), the description for Bit1: Zero
Count states if the interrupt service routine does
not see any changes in the External/Status condi-
tions, it should assume that a zero count transition
occurred when in fact, an Abort condition oc-
curred and was missed. What could be done to
correct this and not miss the fact that an Abort oc-
curred?
A. Very few people actually use the Zero Count interrupt.
This interrupt is generated TWICE during each bit time
and is usually used to count a specific number of bits
that are sent or received. If this interrupt is not used by
your customer, then what is said in the TM about the
Zero Count is true for the Abort Condition. If no other
changes occurred in the external/status conditions
and the Zero Count is not used, then the source of the
interrupt was the Abort condition.
Q. Can the SCC resynchronize independent clocks
(at the same frequency, but could be out of phase),
one for Rx data and one for Tx data?
A. No, the two clocks are independent of each other.
However, the SCC provides a special transmitter-to-
receiver synchronization function that may be used to
guarantee that the character boundaries for the re-
ceived and transmitted data are the same.
Q. When is EOM and EOF asserted?
A. EOM is asserted when it detects depletion of data in
the Tx buffer; EOF is asserted when it detects a clos-
ing flag.
Q. After powering up the SCC, are the reset values in
the write and read registers guaranteed?
A. No. You must perform a hardware or software reset.
Q. Can you read the status of a write register, such as
the MIE bit in WR9?
A. No, in order to retain the status of a write register, you
must keep its status in a separate memory for later
use. However, the only exception is that WR15 is a
mirror image of RR15. Also, the ESCC has a new fea-
ture to allow the user to read some of the write regis-
ters (see the ESCC Product Specification or Technical
Manual for more details).
Q. Is there a signal to indicate that a closing SDLC
flag is completely shifted out of the TxD pin? This
is needed to indicate that the frame is completely
free of the output to allow carrier cut off without
disrupting the CRC or closing flag.
A. No, the only way to find this timing is to count the num-
ber of clocks from Tx Underrun Interrupt to the closing
flag. The ESCC contains the feature by deasserting
the /RTS pin after the closing flag. Upgrade to the ES-
CC!
Q. Does the SCC detect a loss of the receive clock
signal?
A. No, if the clock stops, the SCC senses that the bit time
is very long. Use a watch-dog timer to detect a loss in
the receive clock signal.
Q. Is there any harm in grounding the “NO CON-
NECT” (NC) pins in the PLCC package (pin
#17,18,28,36)?
A. These NC pins are not physically connected inside the
die. Therefore, it is safe to tie them to ground.
Q. Can the SCC be used as a shift register in one of
the synchronous modes with only data sent to the
Tx register with no CRC and no sync characters?
A. CRC is optional in Mono-, Bi-, and External Sync
Modes only. The sync characters can be stripped out
via software.
7-10
UM010901-0601