Compilation issue on Segger studio

[GeekAD]

I have used an example in the sdk 15.2.0 Pin_change_int_pca10040 and added  2 header files and 2 C files extra to this project. I have cleared all the error which came while adding the files but could not able to clear this error as it is not showing any.

No error came while compilation but still it fails how can we solve this issue?

Kindly help!

[Karl Ylvisaker]

Hello,

Could you click on the little triangle at the beginning of the warning line, and see if this does not elaborate on the warning given?
Furthermore, I would recommend building using the debug option when actively developing, you can set this in the top left corner of SES.

Best regards,
Karl

[GeekAD]

[GeekAD]

Hello Karl,

               As you suggested I have changed the building option to debug and compiled the code. Still issue there. I have posted the log regarding the same.

[Karl Ylvisaker]

Hello again,

Have you made any changes to the example?
The last screenshot says that you have multiple definitions of "TIMER_LED". It seems it stems from your Timer.h file.

The warning you had in your first screenshot appeared to be an "Implicit declaration of function" warning, which could be caused by not properly including some headerfile. By the looks of it, this is no longer an issue.

Best regards,
Karl

[GeekAD]

Hello Karl,

                Yes, I added function prototype in the header file and that issue was solved but the build fails is still there.

if there is no warning then why it is failing the build? Kindly assist...

[Karl Ylvisaker]

Hello,

Did you check out your "multiple definition" of "TIMER_LED"?
You can use the rebuild option to have all the files compiled again.
Please do this once you have looked into the multiple definition, and let me know what your compiler outputs then.

Furthermore, I would advise you to move your project folder higher in your system level, to avoid exceeding Windows's path length character limit of 260 - this will save you some potential headaches in the future.

Best regards,
Karl