Keil Logo


Information in this article applies to:

  • µVision all Versions


I am using the Hitex emulator, Hitop software, and the Keil PK51 µVision IDE. How do I configure the uV IDE to work with the Hitop software and emulator?


The uV and HiTop software is seamlessly integrated. However, there are a few things that need to be done to see your source code and symbol information in your emulator software.

  1. Make sure that you're loading the absolute object file (created by the linker), not the hex-format file. The Intel hex file format does not allow for debug information to be included. The absolute object file, if you're using µVision, will have a filename of PROJECTNAME. (no extension.)
  2. Make sure that debug switches are turned on for the linker, assembler, and compiler. Use DEBUG for the Assembler. Use DEBUG and OBJECTEXTEND for the C compiler. To accomplish this in uV - Project - Options for Target "TargetFilename" - Output - check debug.
  3. For some emulators, source files must be located in the same directory as the absolute object file. If your configuration does not allow for this, your emulator software should provide a means of telling it where to find your source files. Remember, the OMF (absolute object) file does not contain your source code - it only contains references to filenames and line numbers. The source must be read from the actual source code file by your emulator software.
  4. Now you must run the Hitex symbols converter program for the Keil compiler. To enter this in uV - Project - Options for Target "TargetFilename" - Output - Execute after make - Hitop Program SPxxxKe.exe (Browse to find the Hitex subdirectory of this executable.
  5. Then when you open run the project in uV and Hitop has that targetfilename converted and loaded into the emulator when you do another uV build Hitop will tell you the converted file has changed "Do you want to down load it into the emulator"?


  • Getting started with µVision - Chapter 4. Creating Applications


Last Reviewed: Wednesday, August 3, 2005

Did this article provide the answer you needed?
Not Sure
  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

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.