• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 76 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.

AM62L-PROCESSOR-SDK: Domain Conflict confirmation

Dheeraj K
Intellectual 750 points
Part Number: AM62L-PROCESSOR-SDK
Other Parts Discussed in Thread: SYSCONFIG, AM62L

Tool/software:

Hi Team,

While working on the AM62L3 platform and generating pin configurations using the SysConfig tool, I observed that the wkup_i2c and wkup_uart peripherals are listed under a separate section called mcu_pmx, indicating they belong to the MCU domain pinmux. However, when referring to the k3-am62l3-evm.dts file in the TI SDK, I noticed that the pin configurations for these peripherals are placed under the &pmx node, which typically refers to the main domain pinmux controller. This creates some confusion regarding which domain—pmx or mcu_pmx—should be used when adding pinctrl entries for wkup_i2c and wkup_uart in the device tree. Could you please confirm the correct domain for these peripherals and clarify whether the usage of &pmx in the EVM DTS is intentional or if these should ideally be placed under mcu_pmx as per the SysConfig output? Understanding this mapping clearly will help ensure that our custom board's pin configurations are applied correctly.


Regards, 
Dheeraj K

  • 0
    TI__Mastermind 48868 points

    Hi Dheeraj,

    I have taken your inputs and checking it internally. Please allow some time to revert back.

    Regards,

    Tushar

  • +1
    TI__Mastermind 48868 points

    Hi Dheeraj,

    Thanks for reporting the above. It seems to be bug in the Pinmux tool. 

    I have checked internally and got the information that we only have a single pmux node for the device tree. There is no MCU domain for AM62L devices.

    The same information can be verified by referring to datasheet also. There are no MCU_PADCONFIG registers for wkup_uart, and wkup_i2c. These peripherals also uses the PADCONFIG define in Main domain.

    Please refer below images.

    Regards,

    Tushar