UPSD3354DV-40U6 Datasheet, PDF (240/272 Pages) STMicroelectronics – fast 8032 MCU with programmable logic

PSD module
UPSD33xx
Figure 83. Example of chaining UPSD33xx devices
JTAG
CONN.
V_CC
100K
100K
TMS
TCK
CIRCUIT BOARD
100K
TMS
TCK
Device 1
TDI
JTAG
Programming
or Test
TSTAT
Equipment TERR
Connects Here
TDO
Optional
Optional
100K
TDI
TDO
TSTAT
TERR
UPSD33XX
TMS _{Device 2}
TCK
10K
) _RST
ct(s ^GND
100K
rodu _100K
lete ^P _System
o _Reset
s _Circuitry
TDI
TDO
IEEE 1149.1
Compliant
Device
TMS _{Device N}
TCK
TDI
TDO
TSTAT
TERR
UPSD33XX
Ob _AI09188b
Obsolete ^{Product(s) - 27.5.8}
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 82 can be used for ISP or for 8032
debugging. There are 3rd party suppliers of UPSD33xx JTAG debugging equipment (check
www.st.com/mcu). 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 79 on page 235) 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 59 for more details.
240/272
Doc ID 9685 Rev 7