mc9s12ne64 Freescale Semiconductor, Inc, mc9s12ne64 Datasheet - Page 456

no-image

mc9s12ne64

Manufacturer Part Number
mc9s12ne64
Description
Hcs12 Microcontrollers Microcontroller
Manufacturer
Freescale Semiconductor, Inc
Datasheet

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
mc9s12ne64CPV
Manufacturer:
RENESAS
Quantity:
21 000
Part Number:
mc9s12ne64CPV
Manufacturer:
FREESCAL
Quantity:
455
Part Number:
mc9s12ne64CPV
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Part Number:
mc9s12ne64CPVE
Manufacturer:
ST
Quantity:
445
Part Number:
mc9s12ne64CPVE
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Part Number:
mc9s12ne64VTU
Manufacturer:
FREESCALE
Quantity:
1 831
Part Number:
mc9s12ne64VTU
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Part Number:
mc9s12ne64VTUE
Manufacturer:
Freescale Semiconductor
Quantity:
10 000
Part Number:
mc9s12ne64VTUE
Manufacturer:
ALTERA
0
Part Number:
mc9s12ne64VTUE
Manufacturer:
FREESCALE
Quantity:
20 000
Chapter 17 Background Debug Module (BDMV4)
For hardware data read commands, the external host must wait 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 firmware read commands, the external host should wait 44 bus clock cycles after sending the command
opcode and before attempting to obtain the read data. This includes the potential of an extra 7 cycles when
the access is external with a narrow bus access (+1 cycle) and / or a stretch (+1, 2, or 3 cycles), (7 cycles
could be needed if both occur). The 44 cycle wait allows enough time for the requested data to be made
available in the BDM shift register, ready to be shifted out.
For firmware write commands, the external host must wait 32 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 64 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 17-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
and
456
Section 17.3.2.1, “BDM Status Register
represents the BDM command structure. The command blocks illustrate a series of eight bit
16-bit misaligned reads and writes are not allowed. If attempted, the BDM
will ignore the least significant bit of the address and will assume an even
address from the remaining bits.
This timing has increased from previous BDM modules due to the new
capability in which the BDM serial interface can potentially run faster than
the bus. On previous BDM modules this extra time could be hidden within
the serial time.
If the bus rate of the target processor is unknown or could be changing, it is
recommended that the ACK (acknowledge function) be used to indicate
when an operation is complete. When using ACK, the delay times are
automated.
(BDMSTS),” for information on how serial clock rate is selected.
MC9S12NE64 Data Sheet, Rev. 1.1
NOTE
NOTE
NOTE
Section 17.4.6, “BDM Serial
1
Freescale Semiconductor
Interface,”

Related parts for mc9s12ne64