• State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 22 subscribers
  • Views 1851 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Uncalled segment due to external variable?

T. Ma

I know you have many discussions about warning L16 but I couldn't find one that would match with my problem below.

I got a warning L16: uncalled segment - SEGMENT: ?PR?API_module2?MODULE2 which my app had nothing to do with. See code below:

in test.c:  ---> app code built with lib1.lib
main {
 api_module1();
}

in module1.c: ----> part of lib1.lib
volatile char var1
api_module1( void ) {
   var1 = ...
}

in module2.c: ----> part of lib1.lib
extern volatile char var1
api_module2 ( void ) {
 if (var1 == ...)
}

I suspect the reason I got this warning was because of the global variable var1 (can't find any other link between these two modules except for this global variable).

Question:
If this variable is actually causing this problem, how do I get rid of it as it is increasing my app's code size unnecessary (by also include module2).
If this variable could not possible be causing this warning, where else should I look?

Also, in module2.c I have another API which does NOT use this var1 global variable but I also got the same warning. Any idea?

Parents
  • 0 in reply to Jon Ward

    Hello Jon,
    I rebuilt with 'Cross Reference' option and the map file is much more clear to read. As you pointed it out, I found the culprit. I found the ?PR?MODULE2 under a ?CO? of another/init module name, which is used by the app. It looks like I have a lot of cleaning up work to do but at least I know where to look now.

    THank you so much for your help.

Reply
  • 0 in reply to Jon Ward

    Hello Jon,
    I rebuilt with 'Cross Reference' option and the map file is much more clear to read. As you pointed it out, I found the culprit. I found the ?PR?MODULE2 under a ?CO? of another/init module name, which is used by the app. It looks like I have a lot of cleaning up work to do but at least I know where to look now.

    THank you so much for your help.

Children
  • 0 in reply to T. Ma

    Just out of curiosity: In uVision2, when bringing up 'options for library lib1.lib', the menu will show a list of 'Select module to always include' module (all .c files) available to the application from this lib1.lib. I'm wondering if there is such option to select 'Always exclude' module.