• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 514 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.

TMS320F28377D: Update build and debug settings when copying a project

O.H
Mastermind 6430 points
Part Number: TMS320F28377D


Hi experts,

My customer is having trouble using CCS.
Environment:
OS: Windows 10 Pro (64bit)
CCS: Version: 8.3.1.00004 (32bit version)
Device: TMS320F28377D(or other MCUs)

Could you tell me how to use the debug configurations to be updated according to the project when copying the project in the same workspace?
To briefly explain the current issue, I created a new project and reviewed it. Below is an explanatory diagram and details.

The build settings and debug configurations of the newly created project Proj1 are shown in (1) to (3) on the upper side.
In ④ on the lower side, the build is executed with Proj2, which is a copy of Proj1, and it is confirmed that the build settings have been inherited.
In ⑤, it seemed that the debug configurations were also taken over by Proj2, but as in ⑥, the contents were still Proj1, and the debug configurations were not taken over.
In this way, I can save the debug configurations as a file, but when we copy the project, the debug configurations file is only copied and its contents do not seem to be updated as the original file.

It's not a big deal if we just change the specification of the program to be debugged, but if we change other detailed settings (specifically, the settings of the Flash sector to be erased, etc.), there are many changes, so it is a mistake. When editing a .launch file directly, it is necessary to understand the contents of the file to some extent, such as specifying the Flash sector, and it seems that it cannot be changed easily.

For this reason, it would be helpful if you could teach me how to use the debug settings to be updated with the project when we copy the project. 

Please point out any other necessary information or points that are difficult to understand.

Best regards,
O.H

  • 0
    TI__Guru**** 467201 points

    Thank you for providing such excellent details on the issue. It was very clear to understand.

    You are correct. The .launch file in the project is copied as-is without any refactoring done. Whether this is by design or not I am not sure. .launch files are usually considered a generated file even though in the above case it was created manually. I will need to follow up with engineering for more details. Note that many of them are on vacation and will return Tuesday of next week so I will not be able to get any confirmation until then.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 467201 points

    Today is a holiday here so I will follow up with the experts tomorrow and keep you posted.

    Thanks

    ki

  • 0 in reply to Ki
    Mastermind 6430 points

    I understand.

    Thank you for following and connecting with the experts.

    Best regards,
    O.H

  • 0 in reply to O.H
    TI__Guru**** 467201 points

    Thank you for your patience. I was investigating further with one of the engineers. We had made some improvements with launch file portability in CCS 10.x. However, it still doesn't do the required refactoring when you copy a project. We agree that it should and that this is a limitation we will look to resolve in the future. I will file a bug for this.

    Thanks

    ki 

  • 0 in reply to Ki
    TI__Guru**** 467201 points

    One comment - after the project is created and the copied project is debugged, you will be asked if you wish to reuse the debug settings previously set. If you select "Yes", it will create a new launch configuration with the name of the copied project but otherwise the rest of the settings will be correct. Other than the different name for the launch configuration, everything else should be as desired. Do you agree with this?

  • 0 in reply to Ki
    Mastermind 6430 points
    Ki said:
    One comment - after the project is created and the copied project is debugged, you will be asked if you wish to reuse the debug settings previously set. If you select "Yes", it will create a new launch configuration with the name of the copied project but otherwise the rest of the settings will be correct. Other than the different name for the launch configuration, everything else should be as desired. Do you agree with this?

    I have reused the previous debug settings as described above, am I correct in assuming that the debug settings have been updated to match the copied project?

    If the above is YES, then I agree.

    As a customer, we would like to be able to take over the detailed debug settings even if the CCS or PC environment changes.

    If the conditions are limited, such as the reuse of previous debug settings can only be done with the same CCS version and in the same workspace, we would like to be able to handle this according to the CCS specifications.

    Best regards,
    O.H

  • 0 in reply to O.H
    TI__Guru**** 467201 points
    O.H said:
    I have reused the previous debug settings as described above, am I correct in assuming that the debug settings have been updated to match the copied project?

    Yes, this should be the case based on the behavior I see in my environment.

    I filed a bug for the original issue. Tracking link:

    https://sir.ext.ti.com/jira/browse/EXT_EP-10532

    This bug would cover the required refactoring for the project launch configuration when a copy is made via the Project Explorer.

    Thank you

    ki

  • 0 in reply to Ki
    Mastermind 6430 points

    Thanks for the report and answer.

    I will contact the customer with the information and workaround you provided and see if it is what they are looking for. If any additional questions arise, we will contact you.

    Best regards,
    O.H