Keil Logo


Information in this article applies to:

  • µVision Version 1
  • C51 Version 5.50


I set the option in the BL51 Code Banking Linker Options dialog to keep the Linker Response File. I then built my project, went back to the BL51 Options dialog and set the response file as my Linker Command File. When I rebuilt my project I got the following error:

Fatal Error 204: Invalid Keyword

Why won't my Command File work, and is there a difference between the Response File and the Command File?


The Linker Response File (.lnk) contains every command line argument that was passed to the linker during the last build.

The Linker Command File (.lin) contains only Linker directives and does not include the list of .OBJ files and .LIB files that are included in the target. This means that a Linker Response File cannot simply be used as a Linker Command File.


You can either reduce the Response File to only contain directives, or you can generate a Command File.

To generate a Command File...

  • Go to the BL51 Options dialog and click on the Files tab,
  • Check 'External Linker Command File' and click on the Create button,
  • Save the Command File and click on the Edit button. The file will then be displayed.
  • Edit the command file where you may enter long directives, splitting the lines with ampersands.

When you create a linker command file, the file created will include the directives you currently have selected. For example:

RS(256) PL(68) PW(78)

Note that the files included in the link are not listed. These are obtained from the list of files included in the project and are automatically inserted in the link by µVision.


Last Reviewed: Friday, July 15, 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.