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.

Problems compiling in CCS5 that didnt exist in CCS4

Other Parts Discussed in Thread: MSP430F5510

I'm finally switching over to CCS5 from CCS4, and I'm noticing quite a few differences between the two versions.

I have a project that uses an MSP430F5510 microcontroller with built in USB interface. I'm also using the USB API that comes with the "MSP430 USB Developers Package". I've created the USB descriptor files using the "USB Descriptor Tool". The project compliled fine under CCS ver 4, but now it wont compile under ver 5.

Please refer to the included screenshot.

When I compile warnings come up about functions declared implicitly,even though they are in fact declared in UsbCdc.h under the USB_API folder. It's as if the compiler is not seeing the code in UsbCdc.h burried within the folder hierarchy. How do I make the compiler aware of these source files?

 

  • The first thing to comes to top of mind is that the project settings that would communicate to the C compiler of the path to the header files did not get brought in.

    Check the Project Build settings for the compiler and ensure the include file path(s) are defined appropriately such that the C compiler can find the highlighted header file.

  • Hi Rob,

    My colleague made an excellent point about checking and verifying your include paths and options.  Please see this wiki for details

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    Also note this useful wiki as CCSv4 and CCSv5 need different msp430 dll versions

    http://processors.wiki.ti.com/index.php/MSP_Debug_Stack

    Please keep us informed whether this helps.

    Best Regards,

    Lisa

  • OK - I think I have this sorted out now. Thanks for the links and suggestions.

    Rob

  • Hi Rob,

    ok, glad to hear and thanks for the update.


    All the best with development.

    Best Regards,
    Lisa