Keil Logo Arm Logo

Error Messages

This list identifies errors that might occur when using ULINKpro. The messages are sorted in groups to identify the error cause easily. If you are experiencing difficulties, contact our support group.

ULINKpro

Firmware Download Failed
ULINKpro firmware cannot be downloaded. "ulinkpro.bin" cannot be found, is invalid, or firmware cannot be downloaded due to hardware problems.
Firmware too old
ULINKpro firmware (ulinkpro.bin) is too old. Reinstall the software.
Cannot read ULINK Firmware version number
Communication is lost or ULINKpro is not working. Unplug ULINKpro from the USB port and plug it back in.
Cannot read ULINK Firmware serial number
Communication is lost or ULINKpro is not working. Unplug ULINKpro from the USB port and plug it back in.
No ULINK device found
No ULINKpro detected. ULINKpro is not connected to the USB port, or the USB driver is not installed properly, or ULINKpro is not working properly. Reconnect or connect ULINKpro to the USB port of the PC.
No ULINK is selected
No ULINK adapter has been selected for debugging. Occurs when more ULINK adapters have been detected, but none has been selected. Select one ULINK from the Serial No drop-down list in the Target Driver Setup dialog. Use Options for Target - Debug - Settings.
ULINK Communication Timeout
Communication is lost or corrupted. Unplug ULINKpro from the USB port and plug it back in.
USB Communication Failure
USB communication is lost or corrupted. Unplug ULINKpro from the USB port and plug it back in.
DR Communication Sequence Error
Internal driver error. Please report it to our support group.
Macro Sequence Error
Internal driver error. Please report it to our support group.
Macro Sequence too long
Internal driver error. Please report it to our support group.
Parameter Error
Internal driver error. Please report it to our support group.

JTAG

JTAG Communication Failure
JTAG communication is corrupted. Target JTAG interface is not working properly. Mainly caused by the target: debug block not powered or clocked properly. Avoid Deep-Sleep modes while debugging. Lower the Max Clock frequency in the Target Driver Setup - Debug dialog.
JTAG Device Chain Error
Devices on the JTAG chain do not meet the requirements, or the JTAG chain is not configured properly. Refer to Chaining Multiple Targets.
JTAG RTCK Failure
JTAG RTCK signal is missing or not working properly. Occurs when RTCK is used for controlling JTAG Max Clock and RTCK is not connected to the target or not provided by the target. Instead, set an explicit value for Max Clock in the Target Driver Setup - Debug dialog.
No Cortex-M Device found in JTAG chain
No Cortex-M processor-based device detected (using JTAG). Device is not connected, not powered, or the debug interface is not working. Enable the SWJ switch in the ULINK USB-JTAG/SWD Adapter section of the Target Driver Setup - Debug dialog.
No JTAG Devices Found
No JTAG device has been detected. Target not connected or not powered, or JTAG interface is not working.
Too Many JTAG Devices in Chain
Either too many JTAG devices have been detected in the chain (maximum 64 devices are allowed), or the JTAG communication is corrupted and it behaves as if too many devices are present. Check if the target is powered. Check if the JTAG interface is working properly. Lower the Max Clock frequency in the Target Driver Setup - Debug dialog.
No ARM Device found in JTAG chain
No ARM7/ARM9 processor-based device detected (using JTAG). Device is not connected, not powered, or the debug interface is not working. Check the connections, or try a manual RESET.

Serial Wire Debug

No Cortex-M SW Device Found
No Cortex-M processor-based device detected (using Serial Wire). Device is not connected, or not powered, or the debug interface is not working. Enable the SWJ switch in the ULINK USB-JTAG/SWD Adapter section of the Target Driver Setup - Debug dialog.
SWD Communication Failure
Serial Wire Debug communication is corrupted. The target SWD interface is not working properly. Mainly caused by the target: debug block not powered or clocked properly. Avoid Deep-Sleep modes while debugging. Lower the Max Clock frequency in the ULINK USB-JTAG/SWD Adapter section.

Debug

Cannot access Memory
Memory on the target cannot be accessed by the debugger. Avoid accessing invalid memory areas on the target system. This message can also be displayed due to the target's debug block being improperly powered or clocked (for example in deep-sleep mode). A lower Max Clock frequency in the Target Driver Setup - Debug dialog might help.
Cannot enter Debug Mode
Debug Interface on the target cannot be accessed. The target debug interface is not working properly. Mainly caused by target problems: debug block not powered or clocked properly. Avoid Deep-Sleep modes while debugging. Lower the Max Clock frequency in the Target Driver Setup - Debug dialog.
Could not stop Cortex-M device
The debugger tries to stop the target. This attempt can be made after initializing the connection, or while resetting the target, or through a stop/step command while debugging. In some cases, the target's debug block not functioning properly raises this error.
Device could not be powered up
Debug block on the device could not be powered. Debug block on the target is not working properly. Mainly caused by target problems: debug block not powered and clocked properly.
Memory Mismatch
Memory mismatch detected while downloading the code to target. Appears when the option Verify Code Download is enabled and when a debugging session is started. Then the code in the target is compared against the load image. The message is raised when the target's Flash was not programmed with the code being debugged. Download the program to Flash.
Could not stop ARM device
The debugger tries to stop the target. This attempt can be made after initializing the connection, or while resetting the target, or through a stop/step command while debugging. In some cases, the target's debug block not functioning properly raises this error.

Trace

Selected SWO Clock is not supported
Selected SWO clock frequency is not supported (too high). Select a lower frequency from the drop-down list.
Selected Trace Port available only with SW Debug Port
Serial Wire trace Output can only be used when Serial Wire is selected as the debug interface. Select the SW port in the ULINK USB-JTAG/SWD Adapter section of the Target Driver Setup - Debug dialog.
Selected Trace Port is not supported
For example, the Serial Wire Output - UART/NRZ trace port mode is not supported. Select a different trace port from the drop down-list in the Target Driver Setup - Trace dialog.
Trace HW not present
Tracing has been enabled in µVision, but the hardware does not have the requested trace resources. For example, ETM trace is selected but the device has no ETM. Execute a Power-on-Reset. Check whether the hardware has been configured properly, for example through an *.ini file. Consult the chapter Configure Cortex-M Devices for Tracing.

Breakpoints (Cortex-M)

It was not possible to disable all breakpoints
Occurs when breakpoints cannot be disabled while the target is running. Stop the target to perform this operation.
Not possible while target is executing
This operation is not possible or failed while the target is running. Occurs in situations where breakpoints cannot be enabled or disabled while the target is running.
This target device does not support all the defined breakpoints
Too many breakpoints have been defined. Reduce the number of breakpoints.
This target device does not support all the defined watchpoints
Too many watchpoints have been defined. Reduce the number of watchpoints.
This target device does not support conditional breakpoints
Remove all conditional breakpoints.
This target device supports only the following watchpoints:
    size = 2^n; n = 0..15
    start must be 2^n aligned
    with optional value match
Change the watchpoint definition.

Breakpoints (ARM7/ARM9)

This target device does not support all the defined breakpoints
Too many breakpoints have been defined. Reduce the number of breakpoints. The following breakpoint combinations are supported:
  • When executing from volatile (RAM) memory:
    • unlimited address breakpoints and one data access breakpoint
    • two data access breakpoints
  • When executing from non-volatile memory, for example Flash:
    • two address breakpoints
    • two data access breakpoints
    • one address breakpoint and one data access breakpoint
This target device only supports one complex range breakpoint
Too many complex range breakpoints have been defined. Reduce the number of these breakpoints.
This target device only supports two simple range breakpoints
Too many simple range breakpoints have been defined. Reduce the number of these breakpoints.
This target device only supports two data access breakpoints
Too many data access breakpoints have been defined. Reduce the number of these breakpoints.
This target device does not support any other breakpoints when:
   — one complex range breakpoint is defined.
   — two simple range breakpoints are defined.
   — two data access breakpoints are defined.
   — simple range and data access breakpoint is defined.
Reduce the number of breakpoints.
Operation not possible while the target device is executing
This operation failed or is not possible while the target is running. Stop the target to perform this operation.
It was not possible to kill all breakpoints
Usually occurs when breakpoints cannot be killed while the target is running. Stop the target to perform this operation.
This target device does not support conditional breakpoints
Remove all conditional breakpoints.
This target device supports only the following range breakpoints:
simple include range and complex exclude range:
    size = 2^n; n = 0..31
    start and end+1 must be 2^n aligned
complex include range:
    size = 2^n - 2^m; n = 0..31; m = 0..n-1
    start or end+1 must be 2^n aligned
Change the breakpoint definition.
This target device supports only data access breakpoints with range:
    size = 2^n; n = 0..31
    start must be 2^n aligned
Change the breakpoint definition.

Flashing

Cannot Load Flash Device Description
Flash description cannot be loaded from the built algorithm (corrupted). Rewrite the Flash algorithm.
Cannot Load Flash Programming Algorithm
The Flash algorithm cannot be loaded due to one of the following reasons.
  • Missing Flash Algorithms.
    Mandatory algorithm functions are missing. Rewrite the programming algorithm.
  • Flash Algorithms not in Thumb Code.
  • Insufficient RAM for Flash Algorithms.
    Increase the RAM for Algorithm size in Configure Flash Download.
  • Cannot Write to RAM for Flash Algorithms.
    Check Configure Flash Download whether the RAM for Algorithm address is valid.
Flash Timeout. Reset the Target and try it again.
The Flash algorithm executed on the target did not respond in time (Flash algorithm code doesn't work as expected). Timeouts are defined in the Flash algorithm.
Missing Flash Sectors Description
Flash sectors are not defined in the Flash algorithm. Rewrite the Flash algorithm.
No Algorithm found for: ...
This is a warning (not an error), which occurs when no Flash algorithm has been found for a certain address range. Configure Flash Download and add or alter a Programming Algorithm.
Overlapping of Algorithms at Address ...
Occurs when more Flash algorithm are defined for an address range. Configure Flash Download and check the Programming Algorithm settings. Correct the address ranges and ensure they are discrete.
Zero Device Size
Occurs when the device size is defined as 0 in the Flash algorithm. Alter the Flash algorithm code.

Keil logo

Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings