• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 102 subscribers
  • Views 950 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.

[FAQ] AM6422: am64x internal clock as Ethernet PHY Clock source CLKOUT0 EXT_REFCLK1

Jakob Roll
Prodigy 70 points
Part Number: AM6422
Other Parts Discussed in Thread: DP83867IR, SYSCONFIG

Hello,
I am working with the am64x and the industrial communication SDK. I am trying to run the ethercat_slave_beckhoff_ssc_demo.
The development board I am using does not provide a clock source for the PHYs (DP83867IR). Instead the XI Pin is connected to the A19 Pin (EXT_REFCLK1) of the am64x.

I am confused how to use sysconfig, to mux the CLKOUT0 Signal to this Pin and how to configure CLKOUT0 to have a Frequency of 25MHz.

Can you assist here?

Thank you and kind regards,

J.Roll

  • +1
    TI__Mastermind 28045 points

    Jakob

    You can use the Clock Tree Tool to visualize the clock sources/paths for the CLKOUT0 pin.  You would get:

    In order to get 25MHz on the EXT_REFCLK1 (CLKOUT0) pin you must:

    * set CLKOUT_CTRL[0] = 0     (Table 5-220 of the Device TRM - rev h)

    * set the PADCOFIG157 to mux mode 5. 

    In he SysConfig (pinux) tool you would select SYSTEM from the left column and then select CLKOUT0:

    --Paul

  • 0 in reply to PaulM
    Prodigy 70 points

    Thanks a lot for your answer. It works.  But to achieve 25MHz the CLKOUT_CTRL Clock Select has to be 1 for 25MHz, i.e. CLKOUT_CTRL[0] = 1 (according to Table 5-220).

    And I have to manually add the pinmux for CLKOUT0. Adding the SYSTEM->CLKOUT0 does not update the ti_pinmux_config.c file.

  • 0 in reply to Jakob Roll
    TI__Mastermind 28045 points

    Jakob

    Thanks for the feedback.   I'll confirm CLKOUT0 ti_pinmux_config.c issue and submit a bug report. 

    --Paul 

  • 0 in reply to PaulM
    TI__Mastermind 28045 points

    Jakob

    I used SysConfig via dev.ti.com and I do see the CLKOUT0 being added to the ti_pinmux_config.c file. 

    The tool shows the diffs after each action. You can see that prior to adding the CLKOUT0 signal on the left, and after on the right.

    FYI, you can select diff views using the the 3-dot menu at the top right of the GUI.

    --Paul

  • 0 in reply to PaulM
    Prodigy 70 points

    Hi Paul,

    I know the diff feature, but this seems not to be the problem.

    What Product did you choose when opening a new project in sysconfig?
    When I use MCU+ SDK for AM64x, SYSTEM appears in the "Reserve peripherals" tab, and does not alter the pinmux file.

    Only the .syscfg file changes:

    Kind regards,

    Jakob

  • 0 in reply to Jakob Roll
    TI__Mastermind 28045 points

    Jakob

    I used the pure pinmux version of SysConfig. It is launched using the following settings:



    I'll add another colleague to help answer for the MCU+ SDK tool. 

    --Paul 

  • 0 in reply to Jakob Roll
    TI__Mastermind 49248 points

    Hello Jakob,

    Jakob Roll said:
    When I use MCU+ SDK for AM64x, SYSTEM appears in the "Reserve peripherals" tab, and does not alter the pinmux file.

    When you select product as MCU+SDK and try to use the reserve peripheral option in the Sysconfig tool. Sysconfig tool will not generate any code for the configured reserve peripherals. 

    As the name suggests, The Reserved Peripherals tab is used to reserve any particular hardware resource that your own custom code will handle, and it tells the Sysconfig tool not to use that peripheral. This tab should not be used for any peripherals that you want to be configured by the tool.

    Regards,

    Tushar