mcf51ac256a Freescale Semiconductor, Inc, mcf51ac256a Datasheet - Page 525

no-image

mcf51ac256a

Manufacturer Part Number
mcf51ac256a
Description
Mcf51ac Flexis
Manufacturer
Freescale Semiconductor, Inc
Datasheet

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
mcf51ac256aCFGE
Manufacturer:
FREESCALE
Quantity:
2 400
Part Number:
mcf51ac256aCFGE
Manufacturer:
FREESCALE
Quantity:
2 400
Part Number:
mcf51ac256aCFUE
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Part Number:
mcf51ac256aCLKE
Manufacturer:
FREESCALE
Quantity:
1 500
Part Number:
mcf51ac256aCLKE
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Part Number:
mcf51ac256aCPUE
Manufacturer:
MURATA
Quantity:
1 000
When the MCU is reset in active background (halt) mode, CLKSW is set which selects the bus clock as
the source of the BDC clock. This CLKSW setting is most commonly used during flash memory
programming because the bus clock can usually be configured to operate at the highest allowed bus
frequency to ensure the fastest possible flash programming times. Because the host system is in control of
changes to clock generator settings, it knows when a different BDC communication speed should be used.
The host programmer also knows that no unexpected change in bus frequency could occur to disrupt BDC
communications.
Normally, setting CLKSW should not be used for general debugging because there is no way to ensure the
application program does not change the clock generator settings. This is especially true in the case of
application programs that are not yet fully debugged.
After any reset (or at any other time), the host system can issue a SYNC command to determine the speed
of the BDC clock. CLKSW may be written using the serial WRITE_XCSR_BYTE command through the
BDC interface. CLKSW is located in the special XCSR byte register in the BDC module and it is not
accessible in the normal memory map of the ColdFire core. This means that no program running on the
processor can modify this register (intentionally or unintentionally).
The BKGD pin can receive a high- or low-level or transmit a high- or low-level. The following diagrams
show timing for each of these cases. Interface timing is synchronous to clocks in the target BDC, but
asynchronous to the external host. The internal BDC clock signal is shown for reference in counting
cycles.
Figure 22-17
host is asynchronous to the target so there is a 0–1 cycle delay from the host-generated falling edge to
where the target perceives the beginning of the bit time. Ten target BDC clock cycles later, the target senses
the bit level on the BKGD pin. Typically, the host actively drives the pseudo-open-drain BKGD pin during
host-to-target transmissions to speed up rising edges. Because the target does not drive the BKGD pin
during the host-to-target transmission period, there is no need to treat the line as an open-drain signal
during this period.
Freescale Semiconductor
SYNCHRONIZATION
PERCEIVED START
(TARGET MCU)
UNCERTAINTY
TRANSMIT 1
TRANSMIT 0
OF BIT TIME
BDC CLOCK
HOST
HOST
shows an external host transmitting a logic 1 or 0 to the BKGD pin of a target MCU. The
MCF51AC256 ColdFire Integrated Microcontroller Reference Manual, Rev. 5
Figure 22-17. BDC Host-to-Target Serial Bit Timing
TARGET SENSES BIT LEVEL
10 CYCLES
Version 1 ColdFire Debug (CF1_DEBUG)
EARLIEST START
OF NEXT BIT
22-33

Related parts for mcf51ac256a