MC9S12C128VFU Freescale Semiconductor, MC9S12C128VFU Datasheet - Page 185

• Manufacturer Part Number: MC9S12C128VFU
• Manufacturer: Freescale Semiconductor

Specifications of MC9S12C128VFU

• Cpu Family: HCS12
• Device Core Size: 16b
• Frequency (max): 25MHz
• Interface Type: CAN/SCI/SPI
• Program Memory Type: Flash
• Program Memory Size: 128KB
• Total Internal Ram Size: 4KB
• # I/os (max): 60
• Number Of Timers - General Purpose: 8
• Operating Supply Voltage (typ): 2.5/5V
• Operating Supply Voltage (max): 2.75/5.5V
• Operating Supply Voltage (min): 2.35/2.97V
• On-chip Adc: 8-chx10-bit
• Instruction Set Architecture: CISC
• Operating Temp Range: -40C to 105C
• Operating Temperature Classification: Industrial
• Mounting: Surface Mount
• Pin Count: 80
• Package Type: PQFP
• Lead Free Status / Rohs Status: Not Compliant

Figure 6-13
occur if a POD device is connected to the target BKGD pin and the target is already in debug active mode.
Consider that the target CPU is executing a pending BDM command at the exact moment the POD is being
connected to the BKGD pin. In this case, an ACK pulse is issued along with the SYNC command. In this
case, there is an electrical conflict between the ACK speedup pulse and the SYNC pulse. Because this is
not a probable situation, the protocol does not prevent this conflict from happening.
The hardware handshake protocol is enabled by the ACK_ENABLE and disabled by the ACK_DISABLE
BDM commands. This provides backwards compatibility with the existing POD devices which are not
able to execute the hardware handshake protocol. It also allows for new POD devices, that support the
hardware handshake protocol, to freely communicate with the target device. If desired, without the need
for waiting for the ACK pulse.
Freescale Semiconductor
(TARGET MCU)
BKGD PIN
DRIVES SYNC
TARGET MCU
TO BKGD PIN
BDM CLOCK
DRIVES TO
BKGD PIN
BKGD PIN
HOST
shows a conflict between the ACK pulse and the SYNC request pulse. This conflict could
This information is being provided so that the MCU integrator will be aware
that such a conflict could eventually occur.
READ_BYTE
HOST
AND STARTS TO EXECUTES
Figure 6-12. ACK Abort Procedure at the Command Level
READ_BYTE CMD IS ABORTED
Figure 6-13. ACK Pulse and SYNC Request Conflict
THE READ_BYTE CMD
MEMORY ADDRESS
TARGET
BY THE SYNC REQUEST
HOST SYNC REQUEST PULSE
BDM DECODE
ACK PULSE
16 CYCLES
(OUT OF SCALE)
MC9S12C-Family / MC9S12GC-Family
HOST AND
TARGET DRIVE
TO BKGD PIN
AT LEAST 128 CYCLES
Rev 01.24
NOTE
Chapter 6 Background Debug Module (BDMV4) Block Description
ELECTRICAL CONFLICT
HIGH-IMPEDANCE
HOST
SYNC RESPONSE
FROM THE TARGET
(OUT OF SCALE)
READ_STATUS
TARGET
NEW BDM COMMAND
NEW BDM COMMAND
HOST
SPEEDUP PULSE
TARGET
185