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.

  • Resolved

CCS/TMDS570LS31HDK: Release version does not produce a .out file

Intellectual 290 points

Replies: 13

Views: 215

Part Number: TMDS570LS31HDK

Tool/software: Code Composer Studio

After developing and debugging a project ok in Debug mode  I thought I would do a Release version.

After adding some missing include paths to match the Debug settings the project seemed to build ok.

But there is no .out file in the Release directory like there is in the Debug directory and no other feedback.

Any ideas?

  • In reply to Tomasz Kocon:

    Thanks. I know what the issue is. You are building TMS570LS3x demo software project from the Hercules Safety MCU Demos package. That demo project was only configured for the Debug configuration. It appears the Release configuration was never correctly set up since it only has the default options. This is why it won't build out of the box. It is missing a bunch of build options. The main difference between the default Debug and Release configurations is the Debug is built with the "-g" option while Release is configured for "-O2" optimization. Hence you can theoretically copy your options from Debug to Release and swap the "-g" for "-O2". But really, the example should have only had one build configuration (Debug) and removed the other one that was not being used at all (Release).

    Thanks
    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Thomas Pikett:

    As for why you got this error:

    Thomas Pikett
    In demo-app/3P/lwip-1.3.2/apps/httpserver_raw_io makefsdata.c the include file dir.h is not found. I cannot find dir.h anywhere.

    I see that for the "Debug" configuration, makefsdata.c has been excluded from the build (along with some other files). Hence why you didn't see the error when you built the Debug configuration. Since the "Release" configuration was never properly configured, it is not excluding any of the files that are supposed to be excluded.

    Thanks

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Thomas Pikett:

    Hi,

    I think my current project is far too messy to fix. I do not need a release build immediately so I will carry on development and mark this issue as resolved.

    I will generate a new HALCogen then CCS project once I have finished - using the latest versions of them.

    Thanks for your help.

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.