• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 502 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.

CCSv4: creating and maintaining custom RTSC Platform via the wizard

Ram R
Intellectual 420 points

Hello All

1. If I create a platform using the wizard, what are the files that need to be source controlled - in the spirit of "CCSv4 Tips and Tricks"?

2. The wizard page for editing the config is not the most convenient. Please consider this as a request for usability enhancements:

 - inability to resize the internal windows (as you break things down to a fine granularity)

- inability to move grid elements up/down (especially if you want to order them monotonically)

 

Thanks!
Ram

  • 0
    TI__Mastermind 37985 points

    Ram,
    The source files for a platform package are: config.bld, package.xdc, package.bld, Platform.xdc and Platform.xs. All other files can be recreated from them by running 'xdc' executable from XDCtools.

    However, if you are not planning to ever change any of these source files and rebuild the platform using XCDtools, it will be much easier to keep all the generated files in a source control system. If you keep only sources, whenever you check them out you'll have to run 'xdc' on them.

    There is also a middle ground between those two options. Not all generated files are really needed. If there is a zip file in the platform directory, then that file contains a minimum set of files needed to use the platform. You can unzip the file and replace the original platform directory with the directory extracted from the zip file. Then, add all the files from the extracted directory to a source control system. One more important tip is to keep in the source control system the whole path encoded in the platform name. For example, if your platform is named myCompany.myBoard, then when you check out the platform files, the path myCompany/myBoard has to be created in order to have the platform work correctly.