AM5729: CCS is unable to trace the compiler path (config.bld error)

Hello Aditya,

What exactly are you trying to accomplish?

Could you point me to what part of the document you are following?

Are you at this step: 

From the error above it seems like your SDK is installed in your /home/NAME/ folder and not /home/NAME/ti folder as indicated..

perhaps this is the issue?

-Josue

Aditya,

Can you try editing the SDK path without the bin folder so it doesn't repeat it?

-Josue

Yes I have tried that by just adding the path till the /usr and let CCS add /bin further but, doing that made it worse and I couldn't even build the project. I also tried to edit the path itself by moving the bin folder to other location but doing that currepted the bin folder and I had to reinstall it.

It is actually asking me to check the config.bld which I did and noticed the same path (with a extra /bin) there and also config.bld is generated automatically every time the project is built hence editing this file also dosen't help

Aditya,

I am out of office at the moment. I will be back on Monday.

-Josue

Sure.

Hi Aditya,

Thank you for your patience. The engineer responsible is currently out of office. Please expect 1 business day delay in response.

Regards,

Takuma

Aditya,

Steps I followed -

* Downloaded CCS

Had issues importing app so did the following steps:

CCS complained there was no ARM compiler..

* Followed this to install ARM compiler: https://software-dl.ti.com/ccs/esd/documents/ccs_compiler-installation-selection.html

CCS complained there was no SYSBIOS libraries...

* Under preferences added the SDK path to capture the needed libraries:

    * Window->Preferences->Code Composer Studio->Products->Add.. 

Hit refresh after path has been added, then install, restart.

Then you add Template app Using project explorer..

Seeing this error after trying to build:

makefile:140: recipe for target 'Template_App.out' failed
/home/josue/ti/ccs1281/ccs/tools/compiler/gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: error: Template_App.out uses VFP register arguments, /home/josue/ti/ccs1281/ccs/tools/compiler/gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/libgcc.a(_udivmoddi4.o) does not
/home/josue/ti/ccs1281/ccs/tools/compiler/gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: failed to merge target specific data of file /home/josue/ti/ccs1281/ccs/tools/compiler/gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/libgcc.a(_udivmoddi4.o)
collect2: error: ld returned 1 exit status
gmake[1]: *** [Template_App.out] Error 1
gmake: *** [all] Error 2
makefile:136: recipe for target 'all' failed

**** Build Finished ****

I will continue trying to finish this today.

-Josue

Have you tried importing the compiler the way the above documentation says?

-Josue

Hey Josue,

Yes I have installed the ARM compiler and imported as the doucument says.

But that didn't solve the problem!

And also I have solved all those issues that you have encountered before this issue that I am stuck with now.

Did  yo u have the same issue with "VFP register arguments"?

Yes but, I managed to solve it and then ran into this problem.

I am out of office for Labor Day. 

I appreciate your patience!

-Josue

Aditya,

I am attempting to recreate your issue here, could you please tell me how you solved the VPF issue?

-Josue

Josue,

I actually added a wrong version of the ARM compiler that my senior shared me that caused the issue. That was solved by just installing the right ARM compiler.

This issue might be caused by using the wrong compiler.

-Aditya

Aditya,

I tried two different compilers including the one mentioned in the documentation and ran into the same issue. 

I will have to try again. This week my BW is non existent so I will not be able to get to it until a week or two.

-Josue

Hi Aditya,

Is this still open at your end?

-Josue