Freescale Semiconductor TWR-K65F180M, Руководство пользователя

Страница: 7 / 18

TWR-K65F180M User's Guide , Rev. 0 , 05/2015
Freescale Semiconductor, Inc. 7
OpenSDAv2 is managed by a Kinetis K20 MCU built on the ARM Cortex-M4 core. The OpenSDAv2
circuit includes a status LED (D3) and a pushbutton (SW1). The pushbutton asserts the Reset signal to
the K65 target MCU. It can also be used to place the OpenSDAv2 circuit into bootloader mode. SPI and
GPIO signals provide an interface to either the SWD debug port or the K20. Additionally, signal
connections are available to implement a UART serial channel. The OpenSDAv2 circuit receives power
when the USB connector J7 is plugged into a USB host.
3.6 Cortex Debug connector
The Cortex Debug connector is a 20-pin (0.05 inch) connector providing access to the SWD, JTAG, and
EzPort signals available on the K65 device. The K65 pin connections to the debug connector (J18) are
shown in this table.
Table 2. Cortex Debug connector pinout
Pin Function TWR-K65F180M connection
1 VTref 3.3 V MCU supply (MCU_PWR)
2 TMS/SWDIO PTA3/UART0_RTS_b/FTM0_CH0/JTAG_MS/SWD_DIO
3 GND GND
4 TCK/SWCLK PTA0/UART0_CTS_b/FTM0_CH5/JTAG_CLK/SWD_CLK/EZP_CLK
5 GND GND
6 TDO/SWO PTA2/UART0_TX/FTM0_CH7/JTAG_DO/TRACE_SWO/EZP_DO
7 Key
—
8 TDI PTA1/UART0_TX/FTM0_CH6/JTAG_DI/EZP_DI
9 GNDDETECT PTA4/FTM0_CH1/MS/NMI_b/EZP_CS_b
10 nReset RESET_b
11 Target Power 5 V supply (via J21)
12 TRACECLK PTE0/SPI1_PCS1/UART1_TX/SDHC0_D1/TRACE_CLKOUT
13 Target Power 5 V supply (via J21)
14 TRACEDATA[0] PTE4/SPI1_PCS0/UART3_TX/SDHC0_D3/TRACE_D0
15 GND GND
16 TRACEDATA[1] PTE3/SPI1_SIN/UART1_RTS_b/SDHC0_CMD/TRACE_D1
17 GND GND
18 TRACEDATA[2] PTE2/SPI1_SCK/UART1_CTS_b/SDHC0_DCLK/TRACE_D2
19 GND GND
20 TRACEDATA[3] PTE1/SPI1_SOUT/UART1_RX/SDHC0_D0/TRACE_D3
NOTE
To avoid conflict with RMII signals, trace signals are routed to the PTE
port with unpopulated 0 Ohm resistors to avoid signal conflicts with
SDHC.
3.7 External Bus Interface
– FlexBus
The K65 device features a multi-function external bus interface called the FlexBus interface controller.
This is capable of interfacing with slave-only devices. The FlexBus interface is not used directly on the
TWR-K65F180M. Instead, a subset of the FlexBus is connected to the Primary Connector so that the
external bus can access devices on Tower peripheral modules. See
Table 6
“
Error! Reference source
not found.
” and sheet 8 of the
TWR-K65F180M Schematics (document TWR-K65F180M-SCH ) for
more details.