Datasheet

Operation
 2013 Microchip Technology Inc. DS52085A-page 35
3.6 TRACE CONNECTIONS
Depending on your selected device, one or more trace capabilities may be available
when the emulator is selected as the debug tool.
3.6.1 Native Trace Connections
No additional connections are necessary to use Native trace. The communications
connection will carry the trace information using the PGD/PGC/EMUC/EMUD pins.
However, the selected device must have this feature. If it does not, one of the other
trace methods may be used.
For more on this type of trace, see Section 6.3.3.1 “Native Trace”.
3.6.2 SPI Trace Connections (High-Speed/LVDS Connection)
Serial trace is an optional trace available using the device SPI and pins 7 (DAT) and 8
(CLK). The device is connected to the target using high-speed/LVDS communication
hardware (Performance Pak) which provides the extra lines for clock and data. The
device does not have to be operating at high speeds to use this feature.
Figure 3-10 shows the proper connections. As with pins 4 (PGD) and 5 (PGC)
(Section 3.5.4 “Circuits That Will Prevent the Emulator From Functioning”), do
not use pull-up or pull-down resistors, capacitors or diodes.
FIGURE 3-10: SERIAL TRACE CONNECTIONS
The DAT and CLK lines are intended for use with devices that do not have built-in
debug logic that allows tracing (Native trace) to use the PGD/PGC/EMUC/EMUD pins.
The DAT line connects to either the target device SPI port SDO1 or SDO2. The CLK
line connects to SCK1 or SCK2.
When you dedicate these pins to tracing, then any multiplexed function on these pins
can no longer be used by the application.
For more on this type of trace, see Section 6.3.3.2 “SPI Trace”.
7
8
Application
PC Board
1 - 6
DAT
CLK
Device
SPI
SDO (serial data ouptut)
SCK (serial clock)
High-Speed/
LVDS
Connection
ACTIVE STATUS
RESETFUNCTION
Emulator Pod