UPSD3422_06 Datasheet, PDF (257/293 Pages) STMicroelectronics – Turbo Plus Series Fast Turbo 8032 MCU with USB and Programmable Logic

uPSD34xx
PSD module
28.6.8
Figure 95. Example of chaining uPSD34xx devices
JTAG
CONN.
V_CC
100K
100K
TMS
TCK
TDI
JTAG
Programming
or Test
TSTAT
Equipment TERR
Connects Here
TDO
Optional
Optional
100K
10K
RST
GND
100K
100K
System
Reset
Circuitry
CIRCUIT BOARD
100K
TMS
TCK
Device 1
TDI
TDO
TSTAT
TERR
µPSD34xx
TMS _{Device 2}
TCK
TDI
TDO
IEEE 1149.1
Compliant
Device
TMS _{Device N}
TCK
TDI
TDO
TSTAT
TERR
uPSD34xx
AI10459
Debugging the 8032 MCU module
The 8032 on the MCU module may be debugged in-circuit using the same four basic JTAG
signals as used for JTAG ISP (TDI, TDO, TCK, TMS). The signals TSTAT and TERR are not
needed for debugging, and they will not create a problem if they exist on the circuit board
while debugging. The same connector specified in Figure 94 on page 256 can be used for
ISP or for 8032 debugging. There are 3rd party suppliers of uPSD34xx JTAG debugging
equipment (check www.st.com/psm). These are small pods which connect to a PC (or
notebook computer) using a USB interface, and they are driven by an 8032 Integrated
Development Environment (IDE) running on the PC.
Standard debugging features are provided through this JTAG interface such as single-step,
breakpoints, trace, memory dump and fill, and others. There is also a dedicated Debug pin
(shown in Figure 91 on page 253) which can be configured as an output to trigger external
devices upon a programmable internal event (e.g., breakpoint match), or the pin can be
configured as an input so an external device can initiate an internal debug event (e.g., break
execution). The Debug pin function is configured by the 8032 IDE debug software tool. See
Section 12: Debug unit on page 50 for more details.
The Debug signal should always be pulled up externally with a weak pull-up (100K
minimum) to V_CC even if nothing is connected to it, as shown in Figure 92 on page 254 and
Figure 93 on page 255.
257/293