• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 731 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.

PROCESSOR-SDK-AM62X: Integrating Pinmux output from the Sysconfig tool to SDK

Ranjith Kumar
Intellectual 310 points
Part Number: PROCESSOR-SDK-AM62X
Other Parts Discussed in Thread: SYSCONFIG, AM625

Hi TI Team,

We are going to use AM625 SoC in our custom device, PROCESSOR-SDK-LINUX-AM62X as SDK and for changing the pin mux configurations we had seen from the other threads that we need to use Sysconfig tool. We have downloaded the tool and changed the configurations as per our need. In the tool we are able to see that it gives the pin mux configuration output in 5 files namely AM62x_pinmux.h, AM62x_pinmux_data.c, devicetree.dtsi, PinmuxConfigSummary.csv and untitled.syscfg.

Of these we are able to find out that the contents from the devicetree.dtsi need to included in the "arch/arm64/boot/dts/ti/k3-am625-sk.dts" but we are not sure whether we need to do the dts changes in both the kernel and u-boot dts files. And we are also not sure whether to include the changes from the AM62x_pinmux.h and AM2x_pinmux_data.c files in the SDK or not. If the changes from these files also needs to be included means please let us know the path where we need to do include the changes in the SDK.

Thanks in advance.

Ranjith.

  • +1
    TI__Guru**** 168141 points

    Hi Ranjith,

    Ranjith Kumar said:
    but we are not sure whether we need to do the dts changes in both the kernel and u-boot dts files.

    Technically you don't need to change u-boot dts if the related modules are not enabled in u-boot.

    Ranjith Kumar said:
    And we are also not sure whether to include the changes from the AM62x_pinmux.h and AM2x_pinmux_data.c files in the SDK or not.

    No, these files are not for Linux.

  • 0 in reply to Bin Liu
    Intellectual 310 points

    Hi Bin,

    Thanks for the confirmation that we need to include the changes only from the dtsi file.

    Can you please let me know what is the default logic level of the output GPIO pins and how we can change the default logic level of the output GPIO pins so that at startup those pins will have the logic level as per our requirement both in kernel and u-boot stage?

    Thanks,

    Ranjith.

  • +1 in reply to Ranjith Kumar
    TI__Guru**** 168141 points

    Hi Ranjith,

    The AM62x TRM Table 12-259 tells the default GPIO pin level is high impedance. You can set the GPIO pin pullup or pulldown in Sysconfig tool, which will take effect once the GPIO driver is initialized.

    If you need the GPIO pin to be pullup or pulldown even before the uboot or kernel GPIO driver is running, you would have to add external pullup or pulldown resisters on those GPIO pins.