Keil Logo

L166: ERROR 110 (CANNOT FIND SECTION OR REGBANK)


Information in this article applies to:

  • C166 Version 4.03

SYMPTOMS

I have converted my µVision1 project over to µVision2. When I build it I get the following error:

*** ERROR L110: CANNOT FIND SECTION OR REGBANK
    SECTION: ?C_CLRMEMSEC
    CLASS:

I am locating ?C_CLRMEMSEC at a specific address using the SECTIONS directive.

CAUSE

In the version 4 tools ?C_CLRMEMSEC is no longer located in this way. A new linker directive called CINITTAB is used.

From the Release Notes (in C166/HLP):

4.3 CINITTAB (Abbr. CI) directive added

The CINITTAB directive locates the C166 Initilization Sections, ?C_CLRMEMSEC and ?C_INITTAB, to a specified address range. For example:

L166 myfile.obj CINITTAB (0x10000 - 0x18000)

This locates the sections ?C_CLRMEMSEC and ?C_INITTAB to the address range 0x10000 - 0x18000. L166 issues a warning if relocation is not possible.

RESOLUTION

  1. Remove the ?C_CLRMEMSEC section from the SECTIONS directive.
  2. If your M66 file shows a CINITTAB directive for the Linker invokation line (at the start of the file) then you do not need to do anything else. If the directive is not shown then complete the remaining steps.
  3. Choose Options for Target from the Project menu and click on the L166 Misc tab.
  4. Enter the CINITTAB directive into the Misc Controls box.

MORE INFORMATION

  • Refer to CINITTAB in the L166 User's Guide.
  • Refer to Error L110 in the L166 User's Guide.
  • Refer to SECTIONS in the L166 User's Guide.

FORUM THREADS

The following Discussion Forum threads may provide information related to this topic.

Last Reviewed: Wednesday, August 3, 2005


Did this article provide the answer you needed?
 
Yes
No
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.