• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 215 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TMS320F28023: multiple configurations and linker command file

Cool Javelin
Expert 1680 points
Part Number: TMS320F28023

Tool/software: Code Composer Studio

CCS V6, Win7 32 bit.

I have been creating a project using a 28022 Piccolo, and I have a custom CMD file that lays out the memory for that device.

I want to move to a 28023 (more flash) and it has a different layout for the memory.

I added a command line flag (--define=F28023) in the linker part of the project, and I put a couple of #ifdef's in the CMD file that checks that flag.

I forgot to tell CCS that the target configuration changed, and when I went to program the device, of course, it disagreed with the CMD file.

I have since changed the target device and all is OK now.

However...

I would like to go back and forth between the two devices

so, my question is...

Rather then me adding a --define= flag and also changing the target configuration, is there a way I can check the target config and have the linker automatically select the proper memory sections for me?

This way I don't have to remember to do 2 things each time I use a different processor, I only have to do one thing.

Even better, is there a way CCS can automatically detect the processor it is connected to and change the target config for me?

Thanks, Mark.

  • 0
    TI__Guru**** 173310 points

    Mark,

    Cool Javelin said:
    Even better, is there a way CCS can automatically detect the processor it is connected to and change the target config for me?

    CCS cannot do this. 

    However, one way to address your situation is by having two build configurations within the same project - one for each device, each with its own --define linker flag. 
    Also add both the target configuration files for both devices to the project. Then you can create multiple debug configurations and set it up so that a debug configuration uses a specific target configuration file as shown in this quicktip video.

    Then the only thing you would need to do is select the appropriate project build configuration prior to launching the debug configuration.

    Hope this helps.

  • 0 in reply to AartiG
    Expert 1680 points

    Thanks Aarti:

    This helped a lot. It also gave me a better understanding of Target configurations as well.

    Thanks, Mark.