• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 98 subscribers
  • Views 543 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.

J721e - Pad muxing

Satish Lal Das1
Intellectual 355 points

In J7 based board, where we have to do the PAD pinmux? Could you please point us to the files either in Linux or RTOS SDK we can can update the PAD mux changes?

Thanks,

Satish

  • 0
    TI__Mastermind 42515 points

    Hi Satish,

    for PSDKRA, please check directory "psdk_rtos_auto_j7_06_02_00_21/pdk/packages/ti/board/src/j721e_evm/"

    for PSDKLA, pinmuxing should be done in u-boot.

    Let me know if you need any further help.

    Regards,

    Yordan

  • 0 in reply to Yordan Kamenov
    Intellectual 355 points

    Hi Yordan,

    There are two file generated from pinmux tool i.e. J721E_pinmux.h & J721E_pinmux_data.c and we are trying to load this from Linux u-boot side.

    Could you please help me understand these

    1) Which u-boot we should integrate this, u-boot-ti-staging or u-boot-k3-r5?

    2) In J721E_pinmux.h there are two include files i.e.

    #include "pinmux.h"
    #include "csl_types.h"

    Where we can find this file? There header files suppose to be available on "git/arch/arm/mach-k3/include/mach"? 

    3) Where in u-boot source code, gJ721E_MainPinmuxData and gJ721E_WkupPinmuxData gets loaded ?

    Thanks,

    Satish

  • 0 in reply to Satish Lal Das1
    TI__Genius 9905 points

    Hello,

    From pinmux tool, you should generate device tree files.

    The output sniipet is the DT node describing the required pinmux settings.

    It should be added in the kernel/u-boot device tree and the corresponding peripheral to request for that pad state by defining pinctrl-0 property.

    Regards,

    Nikhil D

  • 0 in reply to Nikhil Devshatwar
    Intellectual 355 points

    Nikhil, 

    The device tree generated from pinmux tool is looking for following two includes which is not available in u-boot. U-boot fails to build along with device tree. Could you point me how to resolve this.

    #include <dt-bindings/pci/pci.h>
    #include <dt-bindings/sound/ti-mcasp.h>

    I am expecting device tree file should build from u-boot as it generated from pinmux tool, is this correct understanding?

    In past, header (.h) & source (.c) file worked great for me , how I can integrate .c & .h file generated from pinmux tool?

    Thanks,

    Satish

  • 0 in reply to Satish Lal Das1
    TI__Genius 9905 points

    Hi,

    For pinmux, you do not need PCI or McASP bindings. Do not include them

    Regards,

    Nikhil D