• State
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 48 views
  • Users 0 members are here
Support feedback
Options
Options
Related

TMS320F28P650DK: _multi project deletes .sysconfig generated files.

Federico D. Ceccarelli
Prodigy 70 points

Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: SYSCONFIG

I'm setting up a _multi project for a dual core solution following the c28x_dual/empty_project multi core  example.

After editing system.xml accordingly the set up is working but I'm finding an issue when .syscfg file is excluded from projects. 

In the CPU1 case the development has been frozen and .syscfg file has been excluded from the project. When compiling from _multi project the .sysconfig output folder is clean every time deleting the source files that won't be regenerated. 

This doesn't happen compiling from the _cpu1 project.


Can you please indicate me a solution for this issue? 

  • 0
    TI__Intellectual 880 points

    Hi Federico,
    Looking into it, will get back to you.
    Regards,
    Lakshya 

  • 0 in reply to Lakshya Verma
    TI__Intellectual 880 points

    Hi Federico ,
    When you mentioned that the “.syscfg file has been excluded from the project”, did you mean that you right-clicked on the SysConfig file and selected “Exclude from Build”?



    If yes, this would prevent SysConfig from generating the output files
    II would like to better understand your intention behind excluding the SysConfig file so I can assist you more effectively.

    Are you trying to freeze the current configuration and avoid regeneration, or modify the generated SysConfig files manually?

    Best Regards,
    Lakshya Verma 



  • 0 in reply to Lakshya Verma
    Prodigy 70 points

    You are right, I meant that I right-clicked on the SysConfig file and selected “Exclude from Build .syscfg forcpu1 and cpu2 projects.

    As you mention this prevents Sysconfig to run and generate the output files. The .syscfg development has been freeze already for a previous release. The sysconfig output files have been moved to a permanent location, different  than the build folder and, and this location included in the project paths. 

    What have also been change in the project is the .syscfg output location to where the definitive files lives. 

    This allows us to implement the following workflow. Re include .syscfg to build after a change, regenerate syscgf output, freeze the changes and Exclude from build .syscfg again.

    What is happening since moving to a multi core approach is that with the .syscfg excluded from build, when clicking "Build Project(s)" on the _multi project the toolchain cleans and deletes the previously generated files (sysconfig generated source file). 

    This doesn't happen if I Buil Project from each core individually.