S9S12G64F0MLF Freescale Semiconductor, S9S12G64F0MLF Datasheet - Page 298

no-image

S9S12G64F0MLF

Manufacturer Part Number
S9S12G64F0MLF
Description
16-bit Microcontrollers - MCU S12 Core,64kFlash,Au
Manufacturer
Freescale Semiconductor
Datasheet

Specifications of S9S12G64F0MLF

Rohs
yes
Core
S12
Processor Series
MC9S12G
Data Bus Width
16 bit
Maximum Clock Frequency
25 MHz
Program Memory Size
64 KB
Data Ram Size
2 KB
On-chip Adc
Yes
Operating Supply Voltage
3.13 V to 5.5 V
Operating Temperature Range
- 40 C to + 125 C
Package / Case
LQFP-48
Mounting Style
SMD/SMT

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
S9S12G64F0MLF
Manufacturer:
IR
Quantity:
4 200
Part Number:
S9S12G64F0MLF
Manufacturer:
FREESCALE
Quantity:
2 500
Part Number:
S9S12G64F0MLF
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Part Number:
S9S12G64F0MLF
Manufacturer:
FREESCALE
Quantity:
2 500
Part Number:
S9S12G64F0MLF
Manufacturer:
FREESCALE
Quantity:
20 000
Company:
Part Number:
S9S12G64F0MLF
Quantity:
1 961
Part Number:
S9S12G64F0MLFR
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Background Debug Module (S12SBDMV1)
For hardware data read commands, the external host must wait at least 150 bus clock cycles after sending
the address before attempting to obtain the read data. This is to be certain that valid data is available in the
BDM shift register, ready to be shifted out. For hardware write commands, the external host must wait
150 bus clock cycles after sending the data to be written before attempting to send a new command. This
is to avoid disturbing the BDM shift register before the write has been completed. The 150 bus clock cycle
delay in both cases includes the maximum 128 cycle delay that can be incurred as the BDM waits for a
free cycle before stealing a cycle.
For BDM firmware read commands, the external host should wait at least 48 bus clock cycles after sending
the command opcode and before attempting to obtain the read data. The 48 cycle wait allows enough time
for the requested data to be made available in the BDM shift register, ready to be shifted out.
For BDM firmware write commands, the external host must wait 36 bus clock cycles after sending the data
to be written before attempting to send a new command. This is to avoid disturbing the BDM shift register
before the write has been completed.
The external host should wait for at least for 76 bus clock cycles after a TRACE1 or GO command before
starting any new serial command. This is to allow the CPU to exit gracefully from the standard BDM
firmware lookup table and resume execution of the user code. Disturbing the BDM shift register
prematurely may adversely affect the exit from the standard BDM firmware lookup table.
Figure 7-6
times starting with a falling edge. The bar across the top of the blocks indicates that the BKGD line idles
in the high state. The time for an 8-bit command is 8 × 16 target clock cycles.
1. Target clock cycles are cycles measured using the target MCU’s serial clock rate. See
300
and
Section 7.3.2.1, “BDM Status Register (BDMSTS)”
represents the BDM command structure. The command blocks illustrate a series of eight bit
16-bit misaligned reads and writes are generally not allowed. If attempted
by BDM hardware command, the BDM ignores the least significant bit of
the address and assumes an even address from the remaining bits.
If the bus rate of the target processor is unknown or could be changing, it is
recommended that the ACK (acknowledge function) is used to indicate
when an operation is complete. When using ACK, the delay times are
automated.
MC9S12G Family Reference Manual,
for information on how serial clock rate is selected.
NOTE
Rev.1.23
Section 7.4.6, “BDM Serial Interface”
1
Freescale Semiconductor

Related parts for S9S12G64F0MLF