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/LAUNCHXL-F28069M: Project compatibility with CCS v8

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: MOTORWARE

Tool/software: Code Composer Studio

Hi,

   I'm using Motoware Version 1_01_00_18 and CCS v8. Is there any additional procedure required to open/debug/import/export the example projects given with motorware? [Beacause while using the documentation in the resource explorer shows the links for CCS v5].

Thank you

  • Abdul,

    I've assigned your post to a C2000 expert, but due to the US holiday we will get back to no later than July 8th, by end of day US Central Time.

    Best regards,
    Matthew

  • Hi Abdul,

    I don't believe there should be any additional steps needed to properly open/debug/import/export the example projects in CCS v8 vs CCS v5 as they are quite similar in that respect.

    The current version of Motorware and documentation were validated using CCS v5. I wouldn't expect you to have any major issues working through the labs in CCS v8, though I'm not aware of all the differences between the two versions. Functionally it should work the same, but the documentation may not match exactly.

    You can download CCS v5 below to work through the labs if you come across any issues or confusion:

    http://software-dl.ti.com/ccs/esd/documents/ccs_downloads.html

    Best,

    Kevin

  • Hello Kevin,

    Thank you very much for your response.  I was able to successfully import and build 'proj_lab13e' from Motorware's InstaSpin Motion example projects, using CCS v8.  But when I add my own code to it, there are issues.  I added the following code only.

    #include <F2806x_Gpio.h>  //edited
    #include <F2806x_Device.h>  //edited
    uint16_t pinValue; //edited

    EALLOW;  //edited

      GpioCtrlRegs.GPAMUX1.bit.GPIO12 = 0;   //edited
      GpioCtrlRegs.GPADIR.bit.GPIO12 = 0;   //edited

    EDIS;   //edited

    pinValue = GpioDataRegs.GPADAT.bit.GPIO12;  //edited

    Then I added the files F2806x_Gpio.h, F2806x_Gpio.c and F2806x_Examples.h (which was referenced in F2806x_Gpio.c) .  When the project was built, there was errors and warnings as shown below.

    I tried to find if there is a file named 'F2806x_Examples.c' but couldn't locate it in the Motorware folder.  Could you please suggest what could be the cause of this issue?

    Best Regards

  • Hi Abdul,

    This seems like a linking/includes issue. Check the project properties for linking / includes as something may be missing or there that shouldn't be

    In the 'Project Explorer' of CCS can you check the project and its sub folders for the files you're looking for? You may be able to double click the yellow warnings to bring you to the location of the redefinition issues within your project.

    Feel free to provide screenshots of your include / linking properties and project directory of the 'Project Explorer' within CCS if you need help.

    Best,

    Kevin

  • These are the files included.

    I got warnings in "F2806x_Device.h".

  • Abdul,

    Do you have the file 'F2806x_GlobalVariableDefs.c' in your project? This may be needing to be added if not.

    For the redefinition warnings, it's meaning you have the same #define in your project more than once. For example you have ESTOP0 defined in F2806x_Device.h and decalred at line 105 in some other project file as stated in the warning. Finding this other file with the redefinition should help you understand the warning.

    Best,

    Kevin

  • I've added the file 'F2806x_GlobalVariableDefs.c' to my project. It results an error as shown below.

  • Abdul,

    The error is saying your program is not fitting into the device memory space (RAM/Flash). You will need to tweak your linker command file (F28069M_ram_lnk.cmd) and find a way to make it fit. See the below document for information on the linker command file:

    http://software-dl.ti.com/ccs/esd/documents/sdto_cgt_Linker-Command-File-Primer.html

    You can also utilize the memory allocation tool in CCS (go to View on toolbar --> memory allocation) to see how much of each RAM/Flash section is being used.

    Best,

    Kevin