You may get this message, if you update the UDE® version and there is a new version of firmware/loader for the Access Device included. This update is normally applied automatically ...

An update of the IO Pod configuration is needed, if you see this message. This might be caused by new version of UDE® or if you select another communication mode (e.g. DAP instead of JTAG). Please follow the steps below to update or change the configuration ...

If you use an old access device with a new UDE® version, there may be a loader update for the Access Device required. This update can't be applied over Ethernet, please follow the steps below, to update the loader. To update a UAD2+, which is normally connected over Ethernet, you must connect the UAD2+ using USB or FireWire and apply the update ...

This message occurs, when the target system was started in 'Alternate Boot Mode' and the option Safe ABM header handling is not enabled. The message should prevent the user from erasing the ABM header accidentally ...

While downloading of a program code the target pattern are checked via a CRC checksum algorithm. If the check fails the message above will occur. The reasons may be ...

Usually the program code should handle the TriCore exceptions/traps by correct initialisation of the BTV (Trap Vector Table Pointer) register and providing a trap vector table. If the program does not handle the traps it can crash unexpectedly by occurrence of a trap ...

You can configure advanced break conditions (In addition to breakpoints). The complexity of this hardware triggers depends on used target. The program will halt if the configured conditions match. Then this message will be displayed in command view ...

This error message was caused by UDE® symbol engine database. The appropriate database file is located to deep inside the systems path ...

For diagnostic of the problem run the tool:

What are reasons of this error message and how can I solve it? The message occurs, when the internal symbol database of the target application (*.out, *.elf) built by UDE® is corrupted -> delete the corresponding *.sdf file, which is located near by the *.elf file

While ROM stepping the trap handling by the debugger is not possible, because the traps cannot be caught by UDE®. To avoid this error please disable all entries in Config - Target Configuration - Debug - Handle this Controller Exceptions ...

SimIO or Simulated I/O is one of the UDE® features. It allows the usage of the printf/scanf functions to transfer characters between the user application and the debugger (via Simulated I/O Window) via the debugging communication channel (JTAG, ASC, ..). It supports the so-called printf-debugging. Examples for using the SimIO feature can be found within the UDE® installation as Sieve sample for many target architectures ...