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.

AM5728 - Can the GPMC clock be driven externally?

I’m confused by some things I’ve read in the TRM and datasheet about GPMC clock.  Up to this point, I've heard from TI that the GPMC clock is gated in synchronous mode and there's not a way to have it run continuously or output another clock that is synchronous to the internal GPMC clock.  The datasheet lists the GPMC Clock as bidirectional (table 4-8, page 123) with this note:

(1) This clock signal is implemented as 'pad loopback' inside the device - the output signal is looped back through the input buffer to serve

as the internal reference signal. Series termination is recommended (as close to device pin as possible) to improve signal integrity of the
clock input. Any nonmonotonicity in voltage that occurs at the pad loopback clock pin between VIH and VIL must be less than VHYS.

 and clkout1 is described in Table 4-29 (page 151) as:

Device Clock output 1. Can be used externally for devices with noncritical timing requirements, or for debug, or as a reference clock on GPMC as described in Table 4-8. GPMC Signal Descriptions.

After reading these, I just want to make sure there’s no possible way to drive the GPMC clock externally or use clkout1 as a continuously running version of the GPMC clock.  I haven’t found similar information in the TRM and the evaluation module doesn’t use GPMC.  I will be connecting this bus to an FPGA and would like to have a continuously running clock that is synchronous to the GPMC bus.

Thanks,

Jeff

SIGNAL NAME DESCRIPTION TYPE BALLclkout1 Device Clock output 1. Can be used externally for devices with noncritical timing O F21/ P7requirements, or for debug, or as a reference clock on GPMC as described inTable 4-8. GPMC Signal Descriptions.

  • Jeff Gill said:
     Up to this point, I've heard from TI that the GPMC clock is gated in synchronous mode and there's not a way to have it run continuously or output another clock that is synchronous to the internal GPMC clock.

    That is correct.

    Jeff Gill said:
    I just want to make sure there’s no possible way to drive the GPMC clock externally or use clkout1 as a continuously running version of the GPMC clock.

    The GPMC cannot be driven externally.

    We were actually trying to design this device to enable you to use clkout1 as a substitute for gpmc_clk to enable always-on operation, but unfortunately we weren't able to guarantee the proper relationship between clkout1 and gpmc_clk across all process, voltage, and temperature and so we had to drop this feature.  I'll file a ticket to have "or as a reference clock on GPMC" removed since that's not something we can do.

  • Jeff,

    I have an update on this item. I've been investigating further and we do have a *possible* option for you. In particular, we did characterize the timing relationship between gpio6_16.clkout1 and gpmc_clk. That timing relationship is given as parameter F23 in the following tables of the data manual:

    * Table 7-25. GPMC/NOR Flash Interface Switching Characteristics - Synchronous Mode - 1 Load
    * Table 7-25. GPMC/NOR Flash Interface Switching Characteristics - Synchronous Mode - 5 Loads

    Note that the corresponding picture is not correct, i.e. currently there is a gpio_io_dir signal shown with respect to F23. We'll fix this in a future revision.

    So to summarize:

    1. Your board would need to connect gpio6_16.clkout1 as the GPMC clock source to your external device.
    2. You would need to ensure that the timings can accommodate the additional skew introduced by using gpio6_16.clkout1 instead of the gpmc_clk signal.

    A future revision of the data manual should make this a bit more clear.

    Brad