• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 947 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.

CCS/TMS320F28379D: SysConfig Generates Two Pinmux Files

Bryan Radke
Expert 1313 points

Part Number: TMS320F28379D
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Tool/software: Code Composer Studio

This should be a simple solution, I just can't figure it out. We would like to utilize the sysconfig utility for our pinmuxing. Currently the sysconfig is generating a f2837xd_pinout.c/h and a pinout.c/h. We only need the pinout.c/h source, but the compile is throwing a redefine error due to the other file sets. I can't find documentation on how to disable the f2837xd_pinout.c/h generation. Any help would be appreciated!

  • 0
    TI__Guru**** 163055 points

    Bryan,

    Looks like it is setup to generate both the bitfield and driverlib versions of the files.  I am pretty sure that at this point the F28x support is meant to be used in the cloud or standalone vs integrated with CCS.  I will check with the team but I don't see a way to prevent it from generating the bitfield version of the files.

    One workaround would be to generate the files.  Then add the pinout.c/.h files directly do your project.  Currently they will be in a folder like this:

    You could then right click on the .syscfg file and select to exclude it so that it does not keep generating the files every build.  Then if you want to change the muxing you can just open the .sysfig file.  Make your changes.  Look at the preview pane for the generated files and copy the source into your version of the files.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Guru**** 163055 points

    Bryan,

    I spoke with the C2000 team and there is a better way to do this.  What we were doing above was really following the standalone PinMux solution.  i.e. you are meant to just take whichever output you want and then integrate into your project.

    In the latest C2000Ware they have included examples that use the integrated SysConfig method for doing pinmux.  In this method it generates a board.c and board.h that have the pinmux configuration.

    Here is the syscfg file opened and you can see the output on the right.

    There are a couple of different examples depending on which pin package you are using.  The path to navigate to the example is shown at the top.  The example projects are at the bottom of my screen capture.

    Looking at this example I then updated another project so that it was invoking sysconfig correctly by changing these options:

    Regards,

    John