Chinese Version

The access to the whole choice of C16x, XC16x, C166CBC, C166S V2, TriCore, ST30, STR7, ARM7 and ARM9 derivatives is supported with the Universal Access Device 2+, the new all-in-one add-on interface hardware for Universal Debug Engine. UAD2+ offers state-of-the-art hardware support for debugging via JTAG/OCDS and via a wide variety of target system access channels. It is optimized for High-Speed Communication between the UDE on the Host PC and a target system. UAD2+ supports all access features of UDE in an optimized manner.

Basic Features

* Standalone Communication device 17 x 14 x 5cm3
* Host Connection via USB 2.0
-480Mbps Communication Speed
-USB 1.1 supported with reduced efficiency
-Works under Windows 2000, Windows XP and Windows Vista
* or via Host Connection via IEEE1394-OHCI (also known as Firewire? or i.Link?)
-400Mbps Communication Speed
-Integrated Hub Function for optimal Operating with other IEEE1394Targets
-Works under Windows 2000, Windows XP and Windows Vista
* or via Ethernet (in preparation)
-10/100Mbps Communication Speed
-Works under Windows 2000, Windows XP and Windows Vista
* Galvanically isolated target interfaces minimize the negative effects of potential differences between UAD2+ and the target
* Build-in JTAG extender technology features a maximal cable length of the JTAG cable between the UAD2+ and the target up to 50 cm (1 meter and longer on request)
* JTAG port is provided via a dedicated pod with drivers and cables
* CAN bus D-Sub male connector (CiA pin assignment) as debugging communication channel to C167CR, C164CI, XC161CJ, XC164CS, XC167CI or equivalent ST10 and TriCore CAN target systems
* On-board high-speed CAN bus interface driver for ISO-DIS 11898 standard
* Automatic firmware update via on-board Flash programming possible
* Flexible serial high-speed communication to an XC16x, C16x, ST10, ARM7, ARM9 and TriCore target system.

Supported microcontroller derivatives

• C161 CI, C161 CS, C161 JC, C161 JS, C161 K, C161 O, C161 R, C161 U, C161 PI, C161 SI, C161 V (Infineon)
• C163, C163-16F (Infineon)
• C164 CI (Infineon)
• C165, C165 H, C165 UTAH (Infineon)
• 80C166, 83C166, 88C166 (Infineon)
• C167 CR, C167 CR-16F, C167 CS-32F (Infineon)
• XC161 CJ-16FF (Infineon)
• XC164 CM-8FF ,XC164 CS-8FF, XC164 CS-16FF (Infineon)
• XC167 CI-16FF (Infineon)
• XC2264, XC2267, XC2285, XC2286, XC2287 (Infineon)
• ST10R163, ST10F163, ST10R165, ST10F166, ST10R167, ST10F167, ST10F168, ST10F169, ST10R172 (STMicroelectronics)
• ST10F251, ST10F252, ST10R271, ST10R272 (STMicroelectronics)
• ST10R273, ST10F275, ST10F276, ST10F280, ST10F282, ST10F269, ST10F296 (STMicroelectronics)
• Vecon (Infineon)
• EGOLD (Infineon)
• SDA6000 (Micronas)
• SDA6001 (Micronas)
• TC11 IB (Infineon)
• TC1100, TC1115, TC1130 (Infineon)
• TC1161, TC1162, TC1163, TC1164, TC1165, TC1166 (Infineon)
• TC1765 (Infineon)
• TC1766, TC1766ED (Infineon)
• TC1775, TC1775 B (Infineon)
• TC1796, TC1796ED (Infineon)
• TC1910 (Infineon)
• TC1912 (Infineon)
• TC1920 (Infineon)
• ARM7TDMI ADuC7019, ADuC7020, ADuC7021, ADuC7022, ADuC7024, ADuC7025, ADuC7026, ADuC7027 (Analog Devices)
• ARM7TDMI AT91x40, AT91FR40162 (Atmel)
• ARM7TDMI-S LPC2114, LPC2119, LPC2124, LPC2129, LPC2131, LPC2132, LPC2138, LPC2142, LPC2148, LPC2194 (Philips/NXP)
• ARM7TDMI-S LPC2212, LPC2214, LPC2292, LPC2294 (Philips/NXP)
• ARM7TDMI-S LPC2364, LPC2366, LPC2368, LPC2378 (Philips/NXP)
• ARM7TDMI NS7520 (NetSilicon)
• ARM7TDMI NET+15, NET+20, NET+40, NET+50 (NetSilicon)
• ARM7TDMI-S MAC71x1, MAC71x2, MAC71x4, MAC71x5, MAC71x6 (Freescale)
• ARM7TDMI ST30 (STMicroelectronics)
• ARM720T STR710, STR711, STR712, STR720, STR730, STR731, STR750 (STMicroelectronics)
• ARM7TDMI TMS470R1A64, TMS470R1A128, TMS470R1A256, TMS470R1A288, TMS470R1A384 (TexasInstruments)
• ARM7TDMI TMS470R1B512, TMS470R1B768 (TexasInstruments)
• ARM920T AT91RM9200 (Atmel)
• ARM926EJ-S TDMI AT91SAM9261 (Atmel)
• ARM926EJ-S LPC3180 (Philips/NXP)
• ARM966E-S STR910, STR911, STR912 (STMicroelectronics)
• XScale PXA255, PXA27x (Marvell/Intel)
• i.MX31 (Freescale)*
• Cortex-M3 (ARM)*
  

ASC Interface

Universal Access Device 2+ provides a buffered asynchronous communication path between an external RS232 device controlled by the target system application and the ASC0 of the target system controller.

In ASC-BSL/CAN, ASC-BSL/3Pin or ASC-BSL/SSC mode, after booting up the target system controller via ASC0 and transferring the monitor code the ASC0 channel will no longer be used by the debug communication and is therefore available for the application. With the buffered ASC0 of Universal Access Device 2+, the application's external RS232 device does not need to be manually reconnected - this is automatically done by Universal Access Device 2+.

Additionally to the buffered ASC0 via RS232, an unbuffered TTL-level ASC0 is available. For this, no additional hardware (RS232 driver) at the target system is required - the signal lines TxD and RxD are directly connected to the corresponding controller pins.

SSC Interface

As no additional hardware is required, the maximum transmission speed of up to 5Mbps can be achieved.

• RS232/ASC0 for booting-up the target system. After downloading the monitor (<< 1sec at 115kbps), the RS232 interface is available for the application again without any external hardware or application software reconfiguration.
• About 3kByte of target system RAM for the SSC monitor.
• Only 3 port pins of the C16x controller used.
• Optionally one timer for run-time measurement.

3Pin Interface

ASC Bootstrap loader / 3Pin Interface - The Perfect Solution for ROMless Debug Monitors
With the new ASC-BSL/3Pin (Hardware) interface supported by Universal Access Device 2+, a plug-and-play-like target system access can be achieved. Saving system resources in mind, this interface has been developed to free the RS232/ASC0 and any other controller peripherals that are often used by the application itself while maintaining the advantages of an uploadable high-speed monitor without the need for ROM and programming the ROM at the target system prior to debugging. The target system is connected to Universal Access Device 2+ via a standard RS232 link for downloading the 3Pin target connection monitor and three additional lines for the 3Pin interface.
With the ASC-BSL/3Pin interface, a host-to-target communication speed up to of 12 times faster than a standard host PC-COMx based RS232 interface is supported.

• RS232/ASC0 for booting-up the target system. After downloading the monitor (<< 1sec at 115kbps), the RS232 interface is available for the application again without any external hardware or application software reconfiguration.
• About 3kByte of target system RAM for the 3Pin monitor.
• Only 3 port pins of the C16x controller used.
• Optionally one timer for run-time measurement.
  

Your advantage: No additional hardware has to be set-up - no additional monitor required !

CAN Interface

The UAD2 even allows the continuous recording and transmission of messages over the CAN bus during a test process. When performing service needs in the field or also during the development, a CAN service monitor can be linked with the application on the target system. This way, the debugger is able to maintain a connection with the microcontroller even during normal operation.
Following advantages are thereby achieved:

*CAN communication channel may be used simultaneously for your application and for debugging because of the CAN bus node addressing.
*The CAN bus debugging monitor in the target system requires just 4kByte of code and 128Bytes data memory; it can thus be easily integrated into nearly all types of target systems. 4 message identifier and 2 CAN module messages objects for host-to-target communication must be reserved. CAN bus timing is user-definable.

The CAN debugging interface uses the on-chip CAN module of the C167CR, C167CS, C164CI, C161CS, C161JS, XC161, XC164, XC167, ST10R167, ST10R168 or TriCore TC1775, TC1130, TC1796 CAN derivatives or an external i82527 CAN bus controller for communication with debugger on the host PC. The Controller Area Network (CAN) bus and its associated protocol allows very efficient communication between a number of stations connected to the CAN bus. Accessing a number of stations simultaneously may be of great advantage when designing complex systems with a number of CAN nodes based on XC16x, C16x, ST10. Other software performance enhancing features of the CAN bus are: The CAN bus debug interface is an excellent solution allowing rapid access to the target system for software development, testing and on-site maintenance at all times.

Special CAN Bus Target Monitor Features

• Target system monitors for XC16x, C16x, ST10 internal on-chip CAN module and external i82527 available.
• CAN bus ROM monitors for standard evaluation boards come with the Debugger Standard Package.
• User specific CAN bus monitors can be configured from the UDE-Mon Portable Monitor package. All components (sources, objects and libraries) are compatible with the available C16x / ST10 cross compilers.
  
• Standard and Extended Identifiers supported.
• CAN interrupt sharing between monitor and application using the On-Chip CAN module.
• Flash programming via CAN bus (internal FLASH and external FLASH-EPROMs AMD 29F xxx)
• ROM-less CAN debug monitors possible (ASC Bootstrap loader and CAN).
  

CAN Bus Analyzer

• Independent intelligent subsystem enables continuous trace of CAN bus messages
• CAN bus observing capability, can also be used in conjunction with the CAN bus based debugger communication
• CAN bus stimulation - ideally suited for testing CAN applications !
  

The Universal Access Device 2+ CAN Bus Monitoring tool is designed as a development aid for applications using the CAN bus and is not supposed to completely replace a CAN Analyzer.

JTAG

OnChip Debug Support (OCDS) - The New Debug Interface for Infineon C166CBC, C166S V2 (XC16x) and TriCore Family Microcontrollers supported by Universal Debug Engine with Universal Access Device 2+ represents a new technology of debug support for the Infineon 16- and 32-bit microcontrollers. So far, OCDS functionality has been implemented into the newest C166CBC, C166S V2 derivatives and the new generation 32-bit μC-DSP TriCore architecture.
Universal Access Device 2+ supports all of the essential OCDS features like:

• Standard 16 pin Infineon JTAG/OCDS L1 connector (2.5V - 3.3V I/O ring voltage) supports C166CBC, C166S V2 and TriCore JTAG debug communication channel up to 50 MHz shift clock - download rate up to 3,5 MByte/s
• Standard 20 pin ARM JTAG connector (2.5V - 3.3V I/O ring voltage) supports ARM7/ARM9 JTAG debug communication channel up to 25 MHz shift clock - download rate up to 1 MByte/s
• Standard 14 pin PowerPC OnCE connector (2.5V - 3.3V I/O ring voltage) supports Freescale PowerPC OnCE debug communication channel up to 25 MHz shift clock
• Standard 16 pin PowerPC COP connector (2.5V - 3.3V I/O ring voltage) supports IBM/Motorola PowerPC COP debug communication channel up to 25 MHz shift clock
• Direct target system access for the host debugger via JTAG interface (IEEE1149.1)
• OnChip debug operations supports emulator-like additional debug functionality
• Hardware Code Breakpoints
• Read or Write Access Data Breakpoints
• Real-Time Trace Operand Access
  

Using these debug features, no additional hard- or software resources in the target system are required. Therefore, when using the JTAG OCDS L1 port for the debugger all other interfaces of the microcontroller are available to the application with no limitations and the system is ready for debugging over its whole lifetime.
Using JTAG OCDS L1 with Universal Debug Engine (UDE) and Universal Access Device 2+ gives the following major advantages:

• Download performance up to 25 times faster than the low-cost printer port solution! Dramatically speeds up the turn-around cycles of debug sessions, especially of larger applications (1++MByte).
• No resident target monitor in RAM or ROM required.
• Hardware breakpoints available for stepping through program code in ROM or OnChip-Flash/OTP.
• Furthermore, complex trigger conditions can be defined. Symbolic trigger conditions feature now enhanced definitions. With the Universal Access Device 2+, single-chip applications can now be debugged via JTAG OCDS L1 without costly in-circuit emulators.

JTAG-Extender

The UAD2+ is equipped with an active UAD-JTAG Extender per default and allows a maximal cable length of the JTAG cable between the UAD2+ and the target up to 50 cm (1 meter and longer on request). The UAD-JTAG Extender provides a dedicated JTAG pod with drivers and cables. Supported JTAG Connectors:

• 16 pin shroud male header - Infineon connector
• 20 pin shroud male header - ARM connector
• Customer's connectors on request
• Cable length 50cm - longer cable length on request
• Support of open-drain RESET#
• Target MCU I/O voltage used for I/O operations
• LVDS technology for highest performance and signal integrity.
  

UAD OCDS L2 Trace Add-On Board

The system is an optimized solution to support all the features of the Infineon OCDS L2 trace port functionality in the best manner.

• Trace ports supported up to 170 MHz
• 1M Sample trace depth
• Timestamp resolution 1/ fCPU (i.e. 10ns at fCPU=100MHz)
• 40bit time stamp range
• Support the full OCDS L1 functionality for providing the trigger events for the tracing unit
• Intelligent trace filter for optimal trace utilization
• TriCore and PCP trace
• Complete support of OCDS L1 trigger signals for trace control and visualization
• Additional 8 external trace lines to observe peripherals and external signals
• LVDS interface to external connector pod supports pods for 60 pin OCDS L2 High-Speed Connector (proposed by Infineon)
• Supported derivatives: TC1130, TC1765, TC1796, TC1910, TC1912, TC1920
  
  

60 Pin OCDS L2 High-Speed Connector Pod

• Recommended by Infineon to support connection to OCDS L2 port of TriCore 1.3 systems (TC11IB, TC1910, TC1912, TC1920 and future derivatives)
• Connector system based on SAMTEC 60 pin high-speed connector QSH-030-01-F-D-A
• Prepared to use for systems up to 150MHz system clock
• Supports 2.5 Volt to 3.6 Volt TriCore 1.3 I/O ring voltage
• 80 pin cable to trace base board using LVDS interface to ensure high trace signal quality
  

UDE Support of OCDS L2 Trace Functions

The complete utilization of trace functionality by 4 setup modes:

• 2 standard modes to allow easy access to standard trace tasks
• 2 expert modes to allow full access to complex possibilities of trace system
• Full connection of trace setup to symbolic reference of source code
• Visualization of internal and external trace events
• Browse capability between trace output and C-language sources
  

ETM and ETB Trace for ARM9

The ARM7 and ARM9 ETM trace board is an add-on for the Universal Access Device 2+ and allows the recording of trace information of a running program on the ARM derivatives in real-time.

UAD ARM7 and ARM9 ETM Trace Add-On Board

The system is an optimized solution to support all the features of the ARM ETM trace port functionality in the best manner.

• Trace ports supported up to 170 MHz, 4 or 8 bit width
• Halfrate Clock Mode supported
• 1M Sample trace depth
• Timestamp resolution 1/ fCPU (i.e. 10ns at fCPU=100MHz)
• 40bit time stamp range
• Support the full ETM functionality for providing the trigger events for the tracing unit
• Intelligent trace filter for optimal trace utilization
• Additional 8 external trace lines to observe peripherals and external signals
• LVDS interface to external connector pod supports pods for 38 pin ETM Mictor High-Speed Connector (proposed by ARM)
• Supported derivatives: LPC21xx, AT91RM9200
  

38 Pin ARM7 and ARM9 Mictor High-Speed Connector Pod

• Recommended by ARM to support connection to ARM ETM
• Connector system based on Mictor 38 pin high-speed connector
• Prepared to use for systems up to 170MHz system clock
• Supports 2.5 Volt to 3.6 Volt I/O ring voltage
• 80 pin cable to trace base board using LVDS interface to ensure high trace signal quality
  

UDE Support of ETM Trace Functions

The complete utilization of trace functionality by setup modes:

• 1 standard modes to allow easy access to standard trace tasks
• Full connection of trace setup to symbolic reference of source code
• Visualization of internal and external trace events
• Browse capability between trace output and C-language sources
  

UDE Support of ETB Trace Functions

The Embedded Trace Buffer (ETB) extends the ETM unit of ARM derivatives by an embedded on-chip circular trace buffer. This simplifies the adaptation of external trace units because the high speed trace signaling does not need to transfer to the external unit. The trace buffer is managed and read via the JTAG communication channel.

• Supported derivatives: LPC3000 derivatives
  

Fax: +86-10-82357574