S9S12P96J0MFT Freescale Semiconductor, S9S12P96J0MFT Datasheet - Page 149

• Manufacturer Part Number: S9S12P96J0MFT
• Description: MCU 96K FLASH AUTO 48-QFN
• Manufacturer: Freescale Semiconductor
• Series: HCS12r

Specifications of S9S12P96J0MFT

• Core Processor: HCS12
• Core Size: 16-Bit
• Speed: 32MHz
• Connectivity: CAN, SCI, SPI
• Peripherals: LVD, POR, PWM, WDT
• Number Of I /o: 34
• Program Memory Size: 96KB (96K x 8)
• Program Memory Type: FLASH
• Eeprom Size: 4K x 8
• Ram Size: 6K x 8
• Voltage - Supply (vcc/vdd): 1.72 V ~ 5.5 V
• Data Converters: A/D 10x12b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 125°C
• Package / Case: 48-QFN Exposed Pad
• Processor Series: S12P
• Core: HCS12
• 3rd Party Development Tools: EWHCS12
• Development Tools By Supplier: KIT33812ECUEVME, DEMO9S12PFAME
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

Since the host knows the target serial clock frequency, the SYNC command (used to abort a command)
does not need to consider the lower possible target frequency. In this case, the host could issue a SYNC
very close to the 128 serial clock cycles length. Providing a small overhead on the pulse length in order to
assure the SYNC pulse will not be misinterpreted by the target. See
Timed Reference
Figure 5-12
command. Note that, after the command is aborted a new command could be issued by the host computer.
Figure 5-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. Since this is not
a probable situation, the protocol does not prevent this conflict from happening.
Freescale Semiconductor
(Target MCU)
Drives SYNC
To BKGD Pin
BKGD Pin
Target MCU
BDM Clock
BKGD Pin
BKGD Pin
Drives to
Host
shows a SYNC command being issued after a READ_BYTE, which aborts the READ_BYTE
shows a conflict between the ACK pulse and the SYNC request pulse. This conflict could
READ_BYTE
Figure 5-12
Pulse”.
the READ_BYTE Command
READ_BYTE CMD is Aborted
Host
Figure 5-12. ACK Abort Procedure at the Command Level
and Starts to Execute
Figure 5-13. ACK Pulse and SYNC Request Conflict
does not represent the signals in a true timing scale
by the SYNC Request
Memory Address
Target
Host SYNC Request Pulse
BDM Decode
S12P-Family Reference Manual, Rev. 1.13
(Out of Scale)
ACK Pulse
16 Cycles
Host and
Target Drive
to BKGD Pin
At Least 128 Cycles
NOTE
Electrical Conflict
High-Impedance
READ_STATUS
Host
SYNC Response
From the Target
(Out of Scale)
Target
New BDM Command
Section 5.4.9, “SYNC — Request
Background Debug Module (S12SBDMV1)
New BDM Command
Host
Speedup Pulse
Target
149