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 440 points

Replies: 13

Views: 284

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?

  • Guru 296285 points

    Hello,

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

    It sounds like the build was not successful. Can you provide the full build output in your build console?

    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/Documentation? Check out the CCS Resources page

    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 Ki:

    Thanks. The build log shows that nearly everything failed to compile. When I changed from a Debug to a Release version the compiler changed! Release uses the TMS470 Compiler and Linker; Debug uses the ARM Compiler and Linker. Another difference is in the include paths with nearly all of them disappearing when I changed to Release mode. Only C:/ti/ccsv6/tools/compiler/arm_5.1.6/include remains in the Includes project folder. I have 3 folders for my project demo-app, HALCoGen and 02.02.02 (for flash operations) - all have include and source folders.

    Update:

    I set the paths incorrectly. Now i have set them correctly it is much better. I have one error (albeit with another compiler) :

    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.

  • In reply to Thomas Pikett:

    Set the same compiler tools and other products for both debug and release versions.

    Best regards,
    Tom

    If I had answered to your question, please mark this post as Resolved.

  • In reply to Tomasz Kocon:

    The problem remains the same. The Release version uses a different compiler and this produces errors not seen in the Debug version.
    Incidentally the errors are in the included httpserver_raw_io folder and I do not want any http facilities.
  • In reply to Thomas Pikett:

    Use Project Properties -> General to change a compiler tools for a release version.

    Best regards,
    Tom

    If I had answered to your question, please mark this post as Resolved.

  • Guru 296285 points

    In reply to Thomas Pikett:

    Thomas - it is hard to determine what the root issue is without the project.

    Can you compile both Debug and Release configurations. Make sure you capture all the build output in the console to a text file. Then attach both text files to this thread.

    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/Documentation? Check out the CCS Resources page

    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 Ki:

    Attached is the log for the Debug and Release versions. Thanks.

    CCS 6.0.1.0040 kit is TMDS570LS31HDK (2014 vintage)TMS570LS3x_demo_software.build.logTMS570LS3x_demo_software.build.log

  • Guru 296285 points

    In reply to Thomas Pikett:

    Looks like both attachments are for the Debug configuration. Can you post the one for Release?

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

    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/Documentation? Check out the CCS Resources page

    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 Ki:

  • In reply to Thomas Pikett:

    Thomas, 

    I see no errors in your last Console log file. 

    Thomas Pikett
    Incidentally the errors are in the included httpserver_raw_io folder and I do not want any http facilities.

    if you do not want any http facilities just exclude (or delete) that files from the project. 

    Best regards,
    Tom

    If I had answered to your question, please mark this post as Resolved.

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.