• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2492 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/TMS320F28069F: Selected flash sectors to erase when flashing are not part of the ccs 7.2 project files

Thomas Watt
Prodigy 40 points
Part Number: TMS320F28069F

Tool/software: Code Composer Studio

I have an implementation of a bootloader and main code. The bootloader takes up sector A and the main code fills the other sectors.

By default CCS v7.2 will erase all sectors when starting a debug session and this ends up erasing either the bootloader or the main code.

I found this select box in the image below which works, however it does not modify any of the normal CCS project files (.ccsproject, .cproject, .project) which are commited to git

So whenever someone goes to cloned the repo again these setting get lost resulting in much time lost and frustration.

It appears that this information may be contained in the files .launches/xxx.launch directory however these are not recommended to be checked to source control according to a rather old wiki http://processors.wiki.ti.com/index.php/Source_control_with_CCS

Can anyone shed light on if these are the correct files for these flash sector settings and if we'll end up with constant merge conflicts if these files are checked in?

  • 0
    TI__Guru**** 161585 points

    Thomas,

    You are correct that these settings are stored in the "Launch".  We generally advise people not to check in the launch as it contains behavior settings that are more personal preference.  However if you need to share the Flash settings then checking in the Launch is the way to go.  You might want to tell people to make it writable after so that they can modify it without having to check out.

    In my case the project name was Example_2806xFlash and the file containing the settings is in the ./launches folder and is called Example_2806xFlash.LAUNCH

    Basically anything you can set from the Debug Configurations dialog gets stored in a launch.

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 40 points

    Hi John,

    I've been using this for a little while and see a problem with this solution - the same set of sectors to Erase are used for all Build Configurations of the project.

    This causes two problems

    -> every time you set a different Build Configuration as Active then the <proj>.launch file is marked as modified - this is a pain for source control.

    -> it isn't possible to have different Flash configurations for different Build Configurations of the project.

    Anyways around this?

    regards,

    Thomas

  • 0 in reply to Thomas Watt
    TI__Guru**** 161585 points

    Thomas,

    It is possible to have multiple debug configurations / launches.

    If you go into the Debug Configuration dialog you can copy an existing one.  You can then set the properties to point to the output of a specific build configuration.

    Here I have created Debug and Release "debug" configurations that correspond to my build configurations:

    Once they have been launched once they will show up on the debug button drop down menu:

    The disadvantage of this method is that you would need to build your project and then click on the debug action.  If you click on the bug button itself it will still launch the one that is associated with the project (unless you delete it).

    Regards,

    John