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.

Making a new project in CCS 6 does not automatically set the part type

Other Parts Discussed in Thread: MSP430AFE231, TM4C1294NCPDT

I am making a project similar to enet_io for the EK-T4M1294XL example.  For some reason, setting the processor in the project properties dialog to T4M1294NCDP does not cause the "define PART_T4M1294NCDP" instruction to the compiler.  Any suggestions?

  • I don't know why but in CCSv6 not all device families are handled in the same way.

    E.g. with a MSP430 project, changing the device does change the pre-defined name passed to the compiler.

    But with a TivaC project, changing the device doesn't change the pre-defined name passed to the compiler.

  • I am including this so that a search for PART_T4M1294XL (and presumably PART_T4M1234XL) will show this thread.  There is a Wiki on the TI site that describes what one must do to port a SYS/BIOS project (pretty much all of the stuff developed for CCS v5 from what I can tell) to TI-RTOS:

    processors.wiki.ti.com/index.php/Porting_an_existing_SYS/BIOS_project_to_TI-RTOS_with_TI-RTOS_drivers

    Please note that a lot of the examples reference TivaWare_C_series-2.0b.  If you install TivaWare from early May 2014 the directory will be called TivaWare_C_Series-2.1.0.12573 instead.  Be sure to use your actual directory name.


    Note that CCS v6 is *NOT* creating this #define automagically like it should, but at least these instructions tell you where to change a lot of project variables to get it to work.  Had I found this early on, I would have saved days of effort tracking down why RTOS projects would not build.

    Perhaps someone from TI should cross post to the RTOS forum and maybe the Tiva forum since searches may not always turn up this information.

  • One more update:

    The default RTOS driverlib constant and usblib constant is listed in the Wiki as COM_TI_RTSC_TIRTOS_INSTALL_DIR.

    The constant that is *actually* used is COM_TI_RTSC_TIRTOSTIVAC_INSTALL_DIR.

    Your mileage may vary....

  • The -D is not getting defined as it is not specified as a default build option to set for the device.  Basically there is an xml file that defines a bunch of things for a device including some default build options to use when creating a new project.

    For example the file for the MSP430AFE231 has this line:

    <property Type="stringfield" Value="-D=__MSP430AFE231__" id="CompilerBuildOptions"></property>

    For if I look at the file for TM4C1294NCPDT I don't see it defined when using the TI compiler but it does have it defined for the GNU compiler.

    <property Type="stringfield" Value=" --silicon_version=7M4 --code_state=16 --abi=eabi --float_support=FPv4SPD16" id="CompilerBuildOptions"/>

    <property Type="stringfield" Value=" -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -ffunction-sections -fdata-sections -MD -std=c99 -Wall -pedantic -DPART_TM4C1294NCPDT -c" id="GNUCompilerBuildOptions"/>

    If you import a project from TivaWare the project will have the -D setup.  I filed a defect (SDSCM00050224) to get the Tiva support files updated to include this option.  It should be there for both TI compiler and GCC projects.

    John

  • Yet another update.  The previous post listed what the xdctools are set to.  That is apparently why the xdctools are *not* working.  I'll post the *real* variable name once I find it.


    I have searched everywhere to see where CCS v6 gets the values for the various variables and how they are set.  I have been unsuccessful.  Getting CCS v6 set up has been very frustrating.  It should be great once I solve all of these environement issues though.

  • Thanks John!!  I appreciate you getting it fixed for the whole community.