CCS/PGA900EVM: Strange build error

The error, in general, means that the definition for that particular symbol referenced by algorithm.obj is not found anywhere. Typically it would be defined in the runtime library.

I do not see the error when building the example project. This is likely because there is no reference to that symbol in the example project. I don't see any source file named "algorithm" in the example, so I presume it is one that you added to your custom project.

Are you using the pre-built rtsv6M0_T_le_eabi.lib provided with the PGA900 Firmware package? If so, I did some analysis and found that the rts in the package was built with an even older version of the linker than 5.2.5 and seems to missing that symbol definition for some reason. You can change the project setting so an updated runtime library using version 5.2.5 linker gets automatically built during project build.

To do that, go into Project Properties->Build->Linker->File Search Path, remove the existing path to the rts library and add "libc.a" instead. This will tell the linker to automatically build the rtsv6M0_T_le_eabi.lib at project build time, and that should resolve the undefined symbol error.

Let us know if this helps.

Thanks for the reply. It did not solve the problem however and I still get the same error. Do you recommend I keep libc.a instead of the path to rtsv6M0_T_le_eabi.lib ?

user4998643 said:

Do you recommend I keep libc.a instead of the path to rtsv6M0_T_le_eabi.lib ?

I don't think it will hurt to leave it as libc.a.

If you still need help resolving the error, we would need the project so we can reproduce the issue first and then investigate the reason for it. If you could zip up the project and attach it here, we could take a look.

I figured out what caused the problem. It was my code after all, but I still find it strange.

So I have a few places in the code where I would like to do a check on a variable to make sure I don't divide by zero. Like shown here (a and b are unsigned short and c and d are signed short).

The error occurs if I uncomment the if statement. And it doesn't matter if it's "if (d != 0.0)" or "if (d != 0)".

Do you mean that the unresolved symbol error is generated even when linking with the runtime library that is auto-generated by the build step? If that's the case, we would still need to see the complete project to better understand what is happening.