Report a Bug in a Keil Product

Think you've found a bug?

If you believe you have encountered a bug in your Keil product, please let us know.

We define bugs as:

• Unexpected errors that can consistently be re-created.
• Actions that lock-up your system.

Please read the following information about bugs and how to report them. Following these instructions will ensure that your problem is resolved quickly.

Most Reported Bugs Aren't Bugs

Fewer than 1% of the bug reports we receive are actually bugs. In most cases they turn out to be one of the following:

• A well-known effect of the C programming language (for example, using values larger than a type supports).
• A hardware timing issue (for example, relying on compiler-generated code to be slow-enough for a slow device).
• Improperly configured tools (for example, specifying that the compiler use XDATA memory when your system has none).
• Programmer error or a bug in your application (for example, indexing off the end of an array). The Keil tools are designed to compile, assemble, link, and debug programs you create. You are responsible for verifying that what your program does makes sense.

Please be sure of the facts when reporting a bug. The more precise you are the faster we can get a solution back to you.

Reporting Bugs

When you report a bug, it is imperative that we are able to duplicate it. If we cannot duplicate the problem we cannot correct it.

Compiler and Assembler Bugs

1. Make sure you have the latest update and most current version of the software.
2. Locate the place in your program where the compiler generates incorrect code. You can find this in the listing file generated.
3. Make a copy of the listing file and mark the incorrect assembler code with an obvious comment like *** incorrect code here *** and describe what you think the problem is.
4. Create a project that we can compile and link with no errors that duplicates the problem.
5. Use PKZIP or WINZIP to compress the project, the source and header files, and the commented listing file.
6. Contact technical support to Request Assistance. We will respond as soon as possible.

Linker/Locator Bugs

1. Make sure you have the latest update and most current version of the software.
2. To duplicate a linker bug, we require a µVision project, source files, and header files require to compile and link the program.
3. Make a copy of the MAP file and mark the incorrect linkage results using obvious comments like *** segment located at wrong address *** and describe the problem.
4. If you use the LX51 Linker, use the COD listing file to locate and annotate the error.
5. Use PKZIP or WINZIP to compress the project, the source and header files, and the commented MAP and COD files.
6. Contact technical support to Request Assistance. We will respond as soon as possible.

µVision IDE, Simulator, and Debugger Bugs

1. Make sure you have the latest update and most current version of the software.
2. Thoroughly document exactly what keys to press and buttons to click to duplicate the problem.
3. Describe the error condition or the problem that you encountered.
4. If a project is required to duplicate the problem, use PKZIP or WINZIP to compress the project and any additional files that are needed to duplicate the problem.
5. Contact technical support to Request Assistance. We will respond as soon as possible.

Resolution

When we receive a bug report, we work quickly to duplicate and confirm it. Confirmed bugs are given top priority and are resolved as quickly as possible (usually within 48 hours).