C166: Section not Found After Updating to 7.57 or Newer

Information in this knowledgebase article applies to:

• C166 V7.57 or newer

SYMPTOM

In our build script we compile a module in a sub directory and the input file to the compiler also does contain the path:

C166 t/t.c ...

In the linker configuration the code of this module gets located via a SECTION directive:

SECTIONS(?PR?T_T%FCODE (440100H))

This worked well up to the toolchain version 7.56. But after updating to 7.57, the following error is generated during linking:

*** ERROR L110: CANNOT FIND SECTION OR REGBANK
    SECTION: ?PR?T_T
    CLASS:   FCODE

Why does the new toolchain not work any more?

CAUSE

From version 7.56 to 7.57 there was a change in the path handling of the compiler. Previously, only Windows-style path separators '\' were detected. As in the build script, Unix-style separators '/' are used, the whole file parameter including the path was used as section name for the code. Just none C characters were replaced with an underscore.
Now, also the Unix-style path separators are detected, which results in the correct module name without path generated by the compiler. So, the section name in the linker configuration will not find the module's code anymore.

RESOLUTION

In the SECTION directive, change the selector to just contain the module name, without path:

SECTIONS(?PR?T%FCODE (440100H))

and linking will work again.

MORE INFORMATION

• Refer to Sections, Classes, and Groups in the C166 User's Guide.
• Refer to SECTIONS in the L166 User's Guide.

Last Reviewed: Thursday, February 25, 2021