• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 381 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.

Code Composer 3.3 Vs Code composer 2.2

GilKal
Prodigy 50 points
Other Parts Discussed in Thread: CCSTUDIO

 

 

I'm having problems with the loading for an out file generated by Code composer 3.3.

When I load an out file generated by Code Composer 2.2 VIA my own application (platform: Window XP sp3, Visual studio 2005),  I see that it works ok.

However, when I try to load and out file which was build with Code Composer 3.3 i see that it is not doing what it should do (turn leds on).

I heard that there was some change in the out file form between CC.2.x and CC.3.x.

Is anyone here familier with this problem? How can I solve is (or bypass it

 

 

  • 0
    TI__Guru* 84110 points

    CCS 3.x adds some additional information to the .out file that was not included in CCS 2.x. Technically, it is the Code Generation Tools that create the .out file, but those tools are accessed through the CCS IDE for your convenience. The changes include Special Section Types like NOLOAD. The Assembly Language Tools User's Guide describes what is created by the linker when it generates the .out file, plus there are utilities described that let you see what is in the .out file.

    To find out what is different between your CCS 2.2 and CCS 3.3 files, try running the Object File Display Utility (Section 10.1 of spru186q) on both of the .out files and compare the sections that are included and the attributes of the ones added in the CCS 3.3 file. You will then know what sections and/or attributes to look for in your application loader to avoid the problems you are having.

    My guess is that one or more dummy or NOLOAD sections are getting loaded by your application, but they should not be. This is likely overwriting other program or initialized data and causing things to quit working.

    Good luck, and thanks for using the TI E2E Community Forum.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Prodigy 50 points

    This is great, I will try to follow you advise, tahnk you for your answer.

    In any case, is there any way to build the out file to be similar to the it's old version, using CC3.3?

     

  • 0 in reply to GilKal
    TI__Guru* 84110 points

    There is not a switch that I can find to make CCS 3.3 produce CCS 2.x-compatible .out files.

  • 0 in reply to RandyP
    Prodigy 50 points

    OK, still working on your previous response. Thank you for your help!

  • 0 in reply to GilKal
    TI__Guru*** 125430 points

    Here's a possibility:

    1. Rename your current codegen directory from c6000/cgtools to c6000/cgtools_orig or something like that (so you can undo the hack if needed!).
    2. Copy the newer codegen tools from CCStudio_v3.3 into that original directory.
    3. See if you can now load the executable.

    I haven't tried it, but thought I'd throw it out there as a possibility.

  • 0 in reply to Brad Griffis
    Prodigy 50 points

    Thank you for your advise, but I'm getting compilation error because of this new change :)

  • 0 in reply to GilKal
    TI__Guru*** 125430 points

    Arg, bummer...  The other way to do it, which would actually be more proper, would be to install the "old" codegen tools in the setup using CCS 3.3.  In CCS 3.3 you have the ability to install multiple versions of codegen tools and select the version you want to use through Help -> About -> Component Manager.  If you go to the Update Advisor in CCS 3.3 you can get to a page with all the codegen downloads.  I don't remember off the top of my head how far the versions go back, but I believe it's pretty far.  Can you look in your c6000/codegen directory to see if you can find a version number anywhere associated with your codegen tools?  It's been several years since I've had CCS 2.2 installed so that's not easy for me to check!

  • 0 in reply to Brad Griffis
    Prodigy 50 points

    Thank you for your help. I decided to changed the ".out" loader so that it will not include the no load parts. This solved the problem. In order to do that, the flag should be ignored when its value is 10 or 50 (Hex).

     

    Thank you for your help guys :)