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.

AM6442: Processors forum

Part Number: AM6442
Other Parts Discussed in Thread: TMDS64EVM

Hi All,

  I'm having trouble understanding the best way to configure the SOC for our project and I was wondering if someone can point me in the right direction.

  We are planning on using an AM64x for our project in which we will be running a Linux OS on the A53 core(s). As part of our design, we will have an FPGA connected to the GPMC. While doing preliminary testing on a TMDS64EVM board, I modified a MCU+ SDK (CCS) project with the appropriate pad configurations and enabled clocking to the GPMC block (SOC_moduleClockEnable(TISCI_DEV_GPMC0, 1);) to achieve the functionality needed.

  My question: Is there a portion of the boot sequence that can be modified to configure the SOC in this manner, rather than at the application level? Perhaps part of the SYSFW build? I know that the Linux device tree can handle pad configurations through the pin mux driver but I expect other aspects of the SOC configuration are not handled in this manner. Could someone point me in the right direction?

Thanks

  • Perhaps I should re word my question. For the scenario described above (GPMC), is the device tree pin mux definition enough for the SYSFW to enable clocking to the GPMC module for A53 core access?

  • Hi Chris,

    No, pinmux settings in device tree only affect the pin padconfig registers. The GPMC module clock is controlled by other device tree properties. But yes, once the clock device tree properties are set correctly, the kernel driver will request SYSFW to enable the clocks properly for the GPMC module to function.