This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/EVM430-FR6989: Continue from previous problem of "MSP430FR6989_emu.xml" lead to new problem missing header files

Part Number: EVM430-FR6989
Other Parts Discussed in Thread: MSP430FR6989,

Tool/software: Code Composer Studio

FROM PREVIOUS QUESTION

Hi Johns,

Thanks for instructions.

After delete "MSP430FR6989.ccxml" the system generate a new "MSP430FR6989.ccxml" without "MSP430FR6989_emu.xml".

Now I run into environments setup problem the CCS compiler can't locate "intrinsics.h"

What should I add in dialog windows  "Include Options" to solve this include file problem?  Thanks.

Best Regards,

T. Nguyen.

HERE MY NEW QUESTIONs

I use CCS-9 rebuild EVM430-FR6989 codes and run into problem of missing "intrinsics.h" file.

I can't find this file in CSS-9 and EVM430FR6989.

Does anyone rebuild EVM430FR6989 codes successful with CCS-9?

Which CCS version should I use?

Thanks,

Best Regards,

T. Nguyen

  • T. Nguyen,

    You need to add the location of intrinsics.h to the include path list. I did a simple search on my compiler and  I can see that file is in the \include folder under the compiler.  It is odd that your project does not have that path specified already.

    Here is what the path should look like.  I would set it up using a variable like this so that if you change the compiler being used that it will automatically update. ${CGT_TOOL_ROOT}/include.  By putting my mouse over the [...] I can see what the path resolves to.

    Regards,

    John

  • Hi John,

    Thanks for reply,

    I don't see the "intrinsics.h" file in the below path in my system

    C:\TI\ccs910\ccs\tools\compiler\ti-cgt-arm_18.12.2.LTS\include

  • You are looking in the folder for the ARM compiler (ti-cgt-arm...).  Please look in the folder for the MSP430 compiler (ti-cgt-msp430...)

    Regards,

    John.

  • Thanks, but it gives more errors.

    I use CCS-6 with the first instruction remove the file "MSP430FR6989.ccxml" then the compiler goes through.

    Best Regards,

    T. Nguyen

  • libc.a is the C runtime support library.  I suspect that you are also missing the search path for the compiler libraries. ${CGT_TOOL_ROOT}/lib

  • John,

    Thanks for giving more instructions.

    I will stay with CCS-6 for now before switch to CCS-9 when I am familiar with CCS environment setup.

    To avoid environment errors like missing header files or library files, the best way for rebuild EVM430-FR6989 just using CCS-6 instead of CCS-9 - This work for me for others ?????

    Have a good weekend,

    T. Nguyen

  • T. Nguyen,

    Is it the EVM430-FR6989_Out_of_Box_FW project that you are attempting to build?  

    I found that project in a sample package for this board.  I downloaded the package and ran the installer.  

    EVM430-FR6989 Sample Source Code Installer

    I was able to just import the project and build it without any build errors.  I get the error about the _emu.xml file which we know how to fix but I do not get build errors.  I would recommend changing the project seeings so it is using the 18.12.x compiler instead of 4.x but I didn't even have to do that to get it to build.  I am not sure why you are getting all those build errors.

    Regards,

    John

  • Hi John,

    Thanks for another solution.

    I download "EVM430-FR6989 Sample Source Code Installer", install, and rebuild.  It still gives me the same problem.

    Here my 2cents opinions "there are some environments setup missing in CCS-9 when CCS-6 can rebuild with just one modification".

    Best Regards,

    T. Nguyen

  • I believe I know what the issue is.  The project is set to use the 4.2.1 compiler which is about 10 years old.  CCSv6 which in itself is quite old has the build definitions for this compiler so it is able to map it to the 4.3 compiler that it ships with.  CCSv9 does not have the build definitions for this compiler so once you change something in the project settings (such as fixing the _emu error) it is not able to resolve the option mapping from the 4.2.1 compiler to the 18.2.2 compiler.  As a result some of the build options (include paths) are not set and thus the build fails.  I was able to fix this by having CCSv9 discover a 4.2 compiler that I had in my CCSv5.5 install.  It then gets the build definitions from there and can properly migrate the project to the new compiler.  

    Regards,

    John

  • Hi John,

    You already do an excellence job by dig deep into the root causes.

    I am very appreciate for your work done this will help beginner like myself or  future users also run into the same problem like me.

    This is proving the E2E technical support approach WORK!!!!

    Thanks.
    T. Nguyen