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.

TDA4VH-Q1: SysConfig Clock Tree for TDA4VH

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: SYSCONFIG, TDA4VH

Hello,

Is there a way to generate the clock tree for TDA4VH using sysconfig? Using the web tool I see an option to do this for AM62X, but none of the TDA4 platforms. If not, whats the recommended way to generate and view clock settings for the various clocks and PLLs?

  • Hi Jeremy,

    Is there a way to generate the clock tree for TDA4VH using sysconfig?

    This feature is not supported for TDA4VH or other TDA platforms. Alternatively, you can refer TDA4VH TRM chapter 5.4 for details.

    Thanks.

  • Okay thanks for the update. I looked through the reference manual yesterday and was unable to answer my specific question which was why I was hoping for this tool.

    The specific question I have is, what is the best timer resolution possible when using the TIMERx pins in timer capture mode. I have a 26MHz crystal connection to OSC_1 and a 19.2MHz crystal connectioned to WKUP_OSC0.

    What I've looked at to try to figure this out:


    Table 5-62 lists some example resolutions based on different input clocks, but does not fully show the math behind going from the external oscillator frequency to resolution. (Also I think there is a typo in the 27MHz example and 42mS should be swapped with 10.67uS).

    Then in section 12.9.3.1 it says the clock selection is made from MCU_CTRL_MMR0. However, I've searched the TRM for the register definition and I cannot find a register definition for this.

    Table 5-34 Clock mapping shows the possible mux definitions for the MCU_TIMER_x pins, and. one of those is MCU_SYSCLK0 with a typical value of 167MHz, but I am not entirely understanding why this value is typically 167MHz or how to adjust it.

    Thanks for any help. If possible I'd like to understand the full math behind the answer rather than just knowing the best theoretical resolution so I can understand how to do the calculations in the future.

    Thanks,

    Jeremy

  • Hi Jeremy,

    Please note that the clock and device management is ceteralized and handling by the Device Manager (DM) module along with the TIFS (TI foundational software). 

    There is a tool as part of the Linux SDK called 'k3conf" that can be utilized to check the different clock and device state.

    If this is not helpful, we suggest you to look into the TISCI documentation (link) to details.

    Regarding you are query on "timer resolution", we will have to check internally and get back to you.

    Thanks.

  • Thank you! k3conf helped me figure out the clocking.