Keil Logo

C51: Removing and Disabling Warning 13 (RECURSIVE CALL)

Information in this article applies to:

  • C51


When I link my project, I get over 100 times warning 13 (recursive call to segment). I am certain that there is no possibility for recursion to occur in my project, so I used the linker DW(13) directive to disable the warning.

However, I still get Fatal Error 232, application contains too many recursions. How can I remove this?


The DW(13) disable warning directive simply stops the warnings from being displayed during linking. The problems are still there and the linker stops when there are too many warnings.

The solution is to use the RC(0) directive to specify that the linker should allow all the recursive call warnings. However, the DW(13) directive should still be used to stop the warnings being displayed.

In order to specify the directives in µVision you can enter them in Options for Target ... - BL51 Misc - Misc controls field.

The following are the relevent sections from the release notes describing these two directives:

- With the directive DISABLEWARNING (Abbr. DW) you can selectively disable Linker warnings. Example:

BL51 myfile.obj DISABLEWARNING (1, 5)

will disable the report of Warning Number 1 and 5.

- With the BL51 directive RECURSIONS (Abbr. RC) you can specify the number of RECURSIONS allowed, before the Linker responds with the message:


Example for using the RECURSIONS directive:

BL51 test.obj  RECURSIONS (100)

It should be noted that the linker may run for a long time to detect all recursions and remove the references. You should, therefore, use the standard setting RECURSIONS (10) by default.


Last Reviewed: Thursday, February 25, 2021

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.