Communication Hardware "Universal Access Device 2" - UAD2

Universal Access Device 2 - UAD2

With a powerful 32-bit Communication Unit based Universal Access Device 2 (UAD2), pls presents an extremely rapid and flexible communication tool to access a multitude of popular 16 and 32-bit microcontrollers.

The unique combination of JTAG and CAN bus, measurements of a mere 13 x 8 x 3cm³, and a robust aluminum housing, predestine the UAD2 for mobile use in the field. A ground connector enables a common voltage reference between the target system and the UAD2. Because the supply input tolerates unregulated DC voltages from 7V to 25V, the development system is well suited for use in motor vehicles.

Basic Features

• Standalone Communication device 13 x 8 x 3cm³
• Host Connection via USB 2.0
  • 480Mbps Communication Speed
  • USB 1.1 supported with reduced efficiency
  • Works under Windows XP, Windows Vista, Windows 7, Windows 8 (32/64)
• Serial Wire Debug (SWD) support
• Serial Wire Viewer (SWV) support
• Instrumentation Trace Macrocell (ITM) support
• Flexible serial high-speed communication to an XC16x, C16x, ST10, TriCore, ARM7, ARM9, ARM11, XScale, PowerPC, SuperH target system.

Controller Peripheral	Interface	Transfer rate	UDE Support
ASC asynchronous	RS232	up to 1 Mbps
ASC a/synchronous	RS485	up to 1 Mbps
SSC synchronous	RS485	up to 1 Mbps
CAN (On-Chip CAN)	CAN	up to 1 Mbps
JTAG	LVTTL	up to 50 MHz
JTAG (OCDS L1 Support)	LVTTL	up to 50 MHz
DAP	LVTTL	up to 50 MHz
SWD	LVTTL	up to 25 MHz

Supported microcontroller derivatives

• C166, ST10
• XC166, XC2000, XE166
• TriCore
• PowerPC, PowerArchitecture
  
• Cortex-A8, Cortex-M3, Cortex-R4
  
• ARM7, ARM9, ARM11
• XScale
  
• SuperH
  

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.
• 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)

CAN Bus Monitoring

• CAN bus polling
• 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.

ETB Trace for ARM9

The ARM9 ETB trace allows the recording of trace information of a running program on the ARM derivatives in real-time.

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

DAP Support for Infineons TriCore and XC2000

UDE Support for DAP

• DAP communication frequency @ 50 MHz
• Transfer rate up to 3,5 MByte/s ( with TC1797 AUDO Future)
• 2-wire/pin and 3-wire/pin DAP mode supported
• Prepared for single-wire/pin DAP mode
• LED for power indicating

SWD Support for Cortex

• Instrumentation trace ITM (printf-like Debugging)
• Watchpoint Trace DWT, Instruction Pointer Trace
• Event Trace (Interrupts)

UDE Support for SWD

Electrostatic Precautions

1. Before you change any cable connections from the Access Device, please remove the power from the Access Device and your target system.
2. Please ensure that the static electricity and ground potentials between the Access Device, the host PC and the target hardware are balanced. If there is a danger of high potential differences, you must connect the Access Device, the host PC and the target hardware to the same ground domain via a low resistance connection.
3. Establish the target connection and power on the systems.

In all cases, the following rule must be attended:
     The first connection between the devices must be done via the ground !

Solution
All Universal Access Devices are equipped with a ground socket on the front side. Please use this ground socket for discharging the static electricity and balancing ground potentials between the Universal Access Device, the host PC and the target hardware BEFORE you connect the target hardware to the Access Device.

An additional protection for UAD can be achieved by using the JTAG Protector. In hard process environments it is strongly recommended to use the UAD-JTAG-Protector. Please note, that the JTAG Protector DOES NOT suspend the precautions described above.

Trademarks: TriCore is a trademark of Infineon Technologies. ARM, EmbeddedICE and Thumb are registered trademarks of ARM Limited. ARM7, ARM9 and Embedded Trace Macrocell, are trademarks of ARM Limited. ST is a registered trademark of companies belonging to the STMicroelectronics Group. XScale is a registered trademark of companies belonging to the STMicroelectronics Group. All other brands or product names are the property of their respective holders.