
Section 9: Address/Data Bus Interface
MOTOROLA
Page 45
MC68HC05C0 Specification Rev. 1.2
9.5
BUS CYCLE CHARACTERISTICS
There are a few points to be made regarding bus activity which are independent of mode
or cycle stretching. First, as in all 68HC05 microcontrollers, any write cycle is preceded by
a “dummy” read cycle. Although this is transparent to the user with other 68HC05 parts, the
68HC05C0 expanded bus reveals this phenomena. Another note of interest is that if IRV is
not enabled, internal bus activity does not cause changes on the external address or data
for more information on IRV. The reason for this behavior is to reduce unnecessary external
switching which contributes to power consumption and noise. For the same reasons,
effective address calculation bus cycles which force the internal address bus to $XXFE are
not reflected externally, unless IRV is enabled.
9.6
ADDRESS/DATA BUS DURING WAIT AND STOP MODE
The CPU halts during WAIT or STOP mode, which suspends bus activity. The address bus
will hold the state of the address following the WAIT or STOP instruction. If the part is
operating in Muxed Mode, the muxed address/data bus is driven with the lower order
address following the WAIT or STOP instruction. If the part is operating in Non-Muxed
Mode, the data bus will be driven to the opcode of the instruction following the WAIT or
STOP instruction. When the processor exits WAIT or STOP mode, the bus activity will
resume.
NOTE:
When executing a program out of external memory, RD will remain low
during STOP mode and will become high again at the beginning of the
STOP recovery. This implies that the external memory will be driving data
for the duration of STOP. If it is not desired that the external memory be
active for the entire STOP duration, the STOP instruction should be
executed out of internal RAM with internal read visibility disabled.