Keil Logo


Information in this article applies to:

  • µVision version 1.x
  • C166 Version 3.12
  • C251 Version 2.14
  • C51 Version 5.50


When I try to link, µVision reports a linker saying that it couldn't find the linker command file. What's wrong?


There are two possibilities for µVision Version 1 users:

You have configured µVision to use a linker command file and have either not created it, or have erased or moved it. You can see the linker command file settings under Options|BL51 Linker|[Files].

If you have not configured µVision to use a command file as described above, then µVision will create a linker command file on-the-fly every time you link. This is the method used to pass parameters to the linker EXE. There are several reasons why the linker may not be able to find your command file.

  1. You do not have write permission for the directory in which your project file is stored or your TEMP directory, or
  2. You are using a directory name with parentheses in it, for example 'PTE51(0)'.
  3. You have placed your project in a path which involves LFNs(Long File Names):

This only applies to Windows95 and NT.

The Intel OMF-51 file format does not allow for tildes ('~') in file names. When a 16-bit application requests a file or directory name from the operating system, and the file/directory in question has more than 8.3 characters in its name, the filename is converted to meet DOS filename restrictions by placing a tilde and a number as the 7th and 8th characters in the filename. As much of the original file extension as possible is preserved. When the linker looks for a command file in a directory whose name involves long filenames, it cannot find the file, even if it is there. The only solution is to rename your directories in such a way that they meet DOS filename restrictions.



Last Reviewed: Monday, March 12, 2018

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.