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

TMS320F28379D: Sysconfig for CPU2 doesn't show CPU1 after manually merging Sysconfig from another CCS project

stevenh
Guru 20075 points

Part Number: TMS320F28379D
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hello,

I manually merged another project's sysconfig files with my current project's sysconfig files (both CPU1 and CPU2 projects).  After doing so, The CPU2's project sysconfig GUI only shows CPU1 and not CPU2 settings.  Also, some of the settings are missing, specifically the epwm settings.

Why would CPU2's project sysconfig GUI not show CPU1?

There are many differences and I would rather not have to manually change the settings in the sysconfig editor.

  • 0
    Guru 20075 points

    Any suggestions?

  • +1 in reply to stevenh
    TI__Intellectual 2326 points

    Hi Steven,

    I apologize for the late reponse, and just to make sure I understand your problem, you've mannually merged the orginial CPU1 & CPU2's sysconfig files to new projects and the new project's CPU2 sysconfig only shows CPU1 settings as opposed to CPU2?

    If I'm understanding it correctly, can you please make sure that the new CPU2 project settings has the --context flag set to "CPU2" like the attached picture and try manually merging the sysconfig files again? I'm suspecting that the new project are still parsing the sysconfig settings as CPU1 and therefore you're only seeing CPU2 settings disguised in CPU1-compatible settings.

    If the command is set to "CPU1", you could edit the setting (safely) by going to the syscfg GUI and click on the switch button in the device view. 

    Best,

    Sen Wang

  • 0 in reply to Sen Wang
    Guru 20075 points

    The sysconfig properties for both CPUs are set correctly: CPU1 for CPU1 and CPU2 for CPU2.

  • 0 in reply to stevenh
    Guru 20075 points

    I think the issue has to do with the workspace.  The workspace has two projects and 4 system projects.

  • +1 in reply to stevenh
    Guru 20075 points

    The issue was fixed by changing the settings in the SysConfig GUI, but I also think the issue could have been solved by only importing the project that I wanted to build.

  • +1 in reply to stevenh
    TI__Intellectual 2326 points

    Thank you for the update Steven,

    Just out of curiosity, what settings did you change? What was the culprit? Was it some sort of CCS workspace project conflict?

    Best,

    Sen Wang

  • 0 in reply to Sen Wang
    Guru 20075 points

    I didn't change any settings.  I was helping another co-worker with the issue when he was trying to merge his changes into my project.  We finally gave up and he added the changes using the sysconfig GUI. However, I have had similar issues since then and found the way to get around the issue was to only import the System project that I want to build.

  • 0 in reply to stevenh
    TI__Intellectual 2326 points

    Hi Steven,

    Thank you for the info and I really appreciate this insight. I do apologize for the inconvenience caused.

    Best,

    Sen Wang