• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 458 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Build Bug in CCS version 4 for MSP430

Donald McFarland
Prodigy 140 points

Hi there,

 

When making an update to an MSP430 project last week, I was only able to build properly the first time. We are using the TI TXT output format, and that is where the bug is found.

BUG:

The first time you build (I have a fresh copy of CCS version 4) everything goes fine, and the TXT file gets built properly, however all subsequent attempts of re-building fail to include any changes that were supposed to be in the build. The problem is that when you rebuild, rebuild-all, or clean, all of the intermediate and final output files are initially deleted EXCEPT for the TXT file - and to make matters worse, the time stamp on the TXT file gets updated with the same time as the .out file, which leads the user to believe that the TXT file was also updated. After being fooled by this insidious behavior for a few days, I decided to manually delete the TXT files prior to building our 2 projects, and that fixed the problem (i.e. new changes appeared as they should in the resulting run file).

WORK-AROUND:

The CCS version 4 IDE has an option for a pre-build action in the build settings. I created a macro which deletes the TXT file, and I invoke the macro in the pre-build step.

  • 0
    TI__Guru**** 253380 points

    This is an issue for the CCS folks.  I'll briefly explain what I can.  The TI TXT output format is a file created by the hex utility hex430.  The default build process supported within CCS stops after linking the code into a binary object file.  This object file typically has the extension .out.  Your project must include a post-build step which invokes hex430 to convert the .out file to the TI TXT file.  It appears that CCS does not correctly consider whether the TI TXT file is out of date when deciding what should be deleted or rebuilt.

    I'll move this thread to the CCS forum.

    Thanks and regards,

    -George

  • 0
    TI__Guru**** 173310 points

    I haven't been able to recreate this issue. If I modify the source file and rebuid, as you mention the date of the TI TXT hex file does update and the file contains the changes as well. I have the command line to convert the .out file to .txt format as a post-build step in CCS.

    Which version of CCS4 are you using (you can check this from Help->About)? I am using 4.2.1.00004. If you are on a older versiion, would you be able to update to this latest version when you get a chance and verify if the issue still exists? If it does still exist, we may need additional details or a test case that duplicates the issue as I haven't been to duplicate the behavior yet.

  • 0 in reply to AartiG
    Prodigy 140 points

    Hi,

     

    I have the same version as you do. One difference might be that the changes that I made did not effect the size of the rebuilt application because only the values of timer constants were changed (i.e. no new lines of code - just changing some already existing #defines in a header file). If the change that you made caused the run file size to change, then you might not see the bug.

     

    Also, after doing a build, go to the Debug folder and take a look at the intermediate and target output files that were generated - then do a clean of that project and go back and look at what is left in the folder. You will notice that the TI .TXT files were not removed from the folder (fixing this, will fix the bug, even if you can't reproduce it). Ive already lost a couple days of productivity because of this issue, so Im going to move along now. Hope that helps.