Embedded Development Tools and Debuggers for XC2000, TriCore, PowerPC, ARM, Cortex, SH-2A » Support & Updates » FAQ » UDE FAQ » An error or a malfunction was indicated. How can I report this bug?
| Print |

An error or a malfunction was indicated. How can I report this bug?

The UDE software was built and tested under accurateness. Anyhow errors will be occur ...

Please give the pls team your valuable feedback as we continue to build the next version of Universal Debug Engine. For a simple feedback please use an email to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it .

In case of crashes please fill in the 'UDE Support Request Form' from UDE (use the UDE menu Help - UDE Support Request Form when a workspace is loaded) or act the following steps additionally:
  1. Increase the UDE internal Debug Trace Level. Use the menu Config - Debug Server Configuration - Debug Server - Diagnostic Messages-Debug Trace Level and set the value to 100 respectively pull the slider to the right for 'Report all Messages'. If the debugger cannot connect to the target, answer the occurring error box with 'Ignore' and make the setting described above. Restart UDE.
  2. Cause the error and note the procedure.
  3. Write the content of the 'Command View' into a file. Use the context menu, choose Save... or push the Ctrl-S / Strg-S keys. Choose a file name, for example 'CommandLog.txt' and save the file.
  4. Use the UDEAdmin.exe from the UDE program directory to create a report of installed components of UDE and save it as 'Components.txt'.
  5. Please send an email to the pls Support Team at This e-mail address is being protected from spam bots, you need JavaScript enabled to view it with following content:
    • a short description of the procedure to cause the error
    • the generated file 'CommandLog.txt'
    • the generated file 'Components.txt'
    • the file '_connection_lost_report_.txt' from your UDE directory
    • the used target configuration file '*.cfg'. If you do not know, where the file can be found, please open the menu Config - Target Configuration and get the file location from the Target Configuration File box. If the debugger cannot connect to the target, answer the occurring error box with 'Ignore'.
Our Support Team will contact you as soon as possible.
 

Events

4. Elektronik automotive congress
Development Platforms for ARM/Cortex, TriCore, PowerArchitecture

Read more ...

embedded world 2012
Eclipse based development platform for Qorivva microcontrollers, for Kinetis (Cortex-M4) applications

Read more ...

One-Day Crash Course
Multicore Debug Solution MCDS, TriCore Hardware und Treiber-Programming

Read more ...


News

Optimized debug
tools for the
new XMC4000
microcontroller
family
of Infineon
available now

Read more...
 

UDE 3.2:
Efficient multicore
control, unique
visualization
capabilities
and support for the
latest 32-bit SoCs
from different
manufacturers

Read more...
 

Complete debug
solution for the
Development
Device of the
new TriCore
Multicore
Architecture

Read more...
 
Optimized tools
for the new
TC1791, TC1793
and TC1798
AUDO MAX
microcontrollers
Read more...
 
netX controllers
and rcX RTOS
from Hilscher
now supported by UDE
Read more...
 
Dual-core debugging
of NXP's LPC4300
under the single user
interface of UDE
Read more...
 

Kinetis MCUs
from Freescale
based on Cortex-
M4 core supported
by UDE

Read more...
 

UDE version 3.0:
More visualization
capabilities, enhanced
Eclipse integration
and dedicated
support for a wide
range of MCUs

Read more...
 

Complete new
toolchain for
Power Architecture
SoCs
from
STMicroelectronics
and Freescale
based on Eclipse,
GNU and
Universal Debug Engine

Read more...
 
UAD3+ sets new standards in the field of high-end trace and multi-core / multi-target debugging
Read more...