|
The
debugging software escorts you either way. Please find the following overview
about the different debug solutions and their support. Typical variants
for remote debug connection using the debugger Universal Debug Engine
(UDE) regarding the avaliable communication interfaces on the C16x, XC16x,
ST10, TriCore and ARM7 microcontroller hardware:
|
Controller
Peripheral
|
Interface
|
Transfer
Rate
|
Supported
Derivative
|
Monitor
required
|
|
ASC0/ASC1
asynchron
|
RS232
|
up
to 115 kBaud
|
C16x,XC16x,ST10,C166CBC,C166SV2
|
yes
|
|
ASC0/ASC1
asynchron
|
TTL
|
up
to 115 kBaud
|
C16x,XC16x,ST10,C166CBC,C166SV2
|
yes
|
|
ASC0/ASC1
asynchron Startkit
|
RS232
|
up
to 9.6 kBaud
|
C16x,XC16x,ST10,C166CBC,C166SV2
|
yes
|
|
SSC
asynchron
|
TTL
|
up
to 2.5 MBaud
|
C16x,XC16x,ST10,C166CBC,C166SV2
|
yes
|
|
3-pin-Interface
2nd generation
|
TTL
|
up
to 1 MBaud
|
C16x,XC16x,ST10,C166CBC,C166SV2
|
yes
|
|
CAN
(on-chip CAN)
|
CAN
|
up
to 1 MBaud
|
C16x,XC16x,ST10,C166CBC,C166SV2
|
yes
|
|
JTAG/(OCDS
Level 1)
|
LVTTL
|
up
to 500 kBaud
|
XC16x,C166CBC,C166SV2,TriCore
|
no(yes)
|
|
JTAG
|
LVTTL
|
up
to 500 kBaud
|
ARM7
|
no
|
|
JTAG/Starterkit(OCDS)
|
TTL
|
up
to 80 kBaud
|
XC16x,C166CBC,C166SV2,TriCore
|
no(yes)
|
|
Emulator
|
Bond-out
Chip
|
-
|
C16x,ST10
|
no
|
Debugging
via Monitor
- available
for All C16x, XC16x and ST10 derivatives
- guarantees
access to even the latest derivatives when emulators are not yet available
- supports
communication to the host PC via different high-speed serial interfaces
- even
if the application uses all of the serial ports, debugging is possible
via generic port pins
- CAN
bus is available for application even when debug communication channel
is CAN
- Portable
Monitor Development Toolkit for accessing proprietary target system
hardware
- Monitor
Configuration Tool for fast startup when using Bootstraploader/ASCx
communication
- Service
Monitors for above mentioned communication path available-the ideal
solution for on-site application parameter setup
Debugging
via JTAG/OCDS
OCDS
(On-Chip Debug Support) offers direct access to microcontrollers with
an On-Chip Debug Support module (e.g. C166CBC, C166S V2, TriCore and ARM7).
JTAG/OCDS provides a direct serial interface to the controller-internal
functional units (registers, busses, control unit etc.). This way, debugging
is performed without monitor sofeware or emulators.
OCDS
Level 1 is the base of the latest generation of development environments
with new features:
- Event
Triggering by the on-chip trigger unit, by software breakpoints or by
the Break Input pin
- additional
execution of data transfers
- complex
trigger conditions
- symbolic
conditions for enhanced definitions
- automatic
selection and optimized usage of the on-chip resources
- task-specific
breakpoints
- access
to the entire address space of the controller without any external hard-
or software resources
- hardware
breakpoints for debugging in ROM or On-Chip FLASH
- optimum
support for single-chip applications.
OCDS
Level 2 supports the recording of the running program's trace. This allows
the watching of the flow of the running program in real-time within the
process environment. Timing measurements of critical sections are also
possible.
UDE
supports JTAG/OCDS by the Universal Access Device add-on. OCDS L2 is supported
by the Universal Access Device - Trace Board option.
Debugging
via Emulator
- hardware
startup when severe hardware problems are expected
- additionally
to the monitor solution, a trace functionality is available
- debugging
single-chip applications without external RAM
- complex
breakpoints/triggering on events possible
- simulation
memory available
- real-time
execution for extremely time-critical applications
|
