• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 441 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.

AM6442: SysConfig 1.10 missing pinmux for System peripherals?

Steven Hansen
Intellectual 666 points
Part Number: AM6442
Other Parts Discussed in Thread: SYSCONFIG

Using CCS 11.0 with SysConfig 1.10.0 for AM6442 with MCU+SDK v8.01. SysConfig seems to be missing support for setting up pinmux on "System" peripherals like EXT_CLK1 or CLKOUT0.

Under the Reserve Peripherals tab of SysConfig I can see, select, and choose pins for system peripherals. See screenshot below:

But Reserve Peripherals doesn't actually change the generated files (I've read it's for planning only). That's fine, but I can't seem to find any system peripherals like CLKOUT0 on the Software tab of SysConfig that is actually used to generate ti_pinmux_cfg.c.

Is there any way to set up the pinmux for pins like CLKOUT0 using SysConfig?

Thanks!

  • 0
    TI__Mastermind 22883 points

    Hello Steven,

    This can be done using the "PinMux-Only" View of the SysConfig Tool. The layout is similar to the original PinMux Tool and exposes all device modules including MCU_SYSTEM and SYSTEM signals. This can be found by directly selecting the device from the SysConfig Tool start screen instead of selecting a Software Product.

    We are working on updating the "Reserved Peripherals" pane of the Software Product to enable this functionality without the need to switch between the two tool "Views" (SysConfig-SW+Reserved Peripherals and SysConfig-PinMux). In the mean time, you can copy and paste the content from the SysConfig-PinMux generated output to the SysConfig-SW files.

    Let us know if you have additional questions.

    Regards,

    Zackary Fleenor

  • 0 in reply to Fleenor
    Intellectual 666 points

    Hi Zackary,

    Thanks for the info. So I've switched to the desktop SysConfig tool (instead of through CCS), and sure enough if I select only the device on the start screen I can generate pinmux code for CLKOUT0 as you suggest.

    But when I copy this code into my CCS project (I'm putting it into ti_pinmux_config.c which is an Auto Generated file where the other pinmux logic resides), SysConfig automatically recreates these files when the project is built so all changes are lost. Is there a way to keep the changes I've made without SysConfig auto-rebuilding the files?

  • 0
    TI__Mastermind 22883 points

    Hello Steven,

    Is there a way to keep the changes I've made without SysConfig auto-rebuilding the files?

    I have forwarded this question to our MCU+SDK and SysConfig development experts for additional follow up. We will work next week to see if a workaround is available, and also look for a long-term CCS/SysConfig Tool solution.

    Please see comment below from our experts:

    To stop SysConfig from overwriting generated files:

    # Copy the generated files you no longer want generated out of their current location to somewhere in your project (you are now responsible for the file) # To stop generating only some files, click the <> in SysConfig to bring up the generated files view, find the generated file(s) you no longer want built, and click on the "include in build" toggle.  Going forward, the file will be generated into a sub folder named "excluded", but won't be included in the build.  You can then use regular diffing tools to see what's changed.

    # Alternatively, you can right click on the .syscfg script and select "exclude from build".  SysConfig will not be run any more and will not generate any files.