• State
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 114 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

TMS320F280039: Achieving *no* connection for XCLKOUT in SysConfig

Luca Matteini
Prodigy 40 points
Part Number: TMS320F280039
Other Parts Discussed in Thread: SYSCONFIG

I'm using SysConfig to set up a preview of a new board, but when I allocate GPIO16 for a generic I/O, a Resource conflict pops up in the OTHER section.
The reported error is about XCLKOUT pin allocation, which I don't use: most probably I'm missing where to disable it...

  • 0
    TI__Expert 3690 points

    Hi Luca,

    If you have a look at the xclockout (section 3.7.4) in TRM, you can see that the external clock output (XCLKOUT) can be taken to an external pin, which can be GPIO16 or GPIO18,

    So if you are having both GPIO16 and GPIO18 currently used by a different section, it throws the warning of pinconflict.

    So either you can leave GPIO16/18 unassigned to any specific peripheral so that the conflict can be avoided.

    Thanks

    Aswin

  • 0
    Prodigy 40 points

    I resolved my problem, as there is a setting to disable pins for each peripheral. This is called "Use Case" in the "C2000 SysConfig Overview" (see 3.2 PinMux) and most of the peripheral settings - otherwise, look for "PinMux Use Case", as in the case of EQEP peripheral.

    Setting this property to CUSTOM enables a hidden drop-down list of selectable pins to use. In my case, this is under the OTHER section.