• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 372 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.

AM625: How to present Clock tree configuration that was executed in the target

Tuan Dang
Prodigy 60 points
Part Number: AM625


 How can we create *.rd1/*.rd2 file to see what the configuration of clock tree in our target for core M4, A53 and R5? I'd like to check for MCAN as well as MCU_MCAN

 

1. I saw that GEL script file is missing file to Memory Dump for Clock tree in order to generate rd2 file, input for Clock Tree tool for ARM Cortex R5 and M4.

 

2.  In A53 Linux environment: omapconf command was not supported for AM625 device to generate rd1 file

3. In Autosar MCAL in R5, version AM62X_MCAL_00.09.00.02_ENG_REL, the MCU configuration for MCU_CAN0 was utilized MCU_CLK_SRC_1:

 

 So that means in TRM, it could be utilized MCU_PLL0_HSDIV4_CLKOUT 2'b01? Please confirm from my understanding.

 

My Environment: CCS 12.1, mcu_plus_sdk_am62x_08_05_00_14. 

Many thanks,

Tuan.

  • 0
    TI__Genius 9530 points

    Tuan,

    This tool is a fairly new release, so functionality for software to generate import files is still under development. Currently the clock tree tool can best be used to identify what registers to inspect and how to modify values to get an intended result.

    It seems like your question is geared towards which clock source is being selected. In the clock tree tool, if you click on the 'MCU_MCAN-_CLK_SEL' module it will open a drop down in the lower left panel where you can modify the option. Clicking the (?) icon to show expanded information will display the register address and bitfiled values that enable this configuration.

    Examples for the MCU_MCAN0 instance in AM62x below:

    Hopefully this helps demonstrate how the tool can be used to identify and inspect registers at runtime to understand the system configuration. Please let me know if any additional clarification is required.

    Thanks,

    Chris