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.

AM3358: Wait of the synchronous read/write access via GPMC on AM3358

Guru 16800 points
Part Number: AM3358

Hello,

What does mean the following sentence?
"Wait monitoring is supported for all configurations except for GPMC_CONFIG1_i[19-18] WAITMONITORINGTIME = 0 for write bursts with a clock divider of 1 or 2 (GPMC_CONFIG1_i[1-0] GPMCFCLKDIVIDER field equal to 0 or 1, respectively)."
This is described at 7.1.2.3.8.3.5 in TRM.

In some cases (such as using the fast GPMC clock (100MHz)), doesn't wait function work correctly?

Our expectations are following:
- AD multiplexing 16 bit mode
- While asserted the wait signal from external in both of RD/WR, RD/WR doesn't happen and GPMC_CLK output forever.

Best Regards,
Nomo

  • Hi Nomo-san,

    This restriction means that when using the GPMC CLK with divide-by-1 or divide-by-2 from the internal GPMC_FCLK, the WAIT signal must be valid (meeting setup time) at least 1 GPMC CLK cycle before WRITEACCESSTIME. It cannot change just before WRITEACCESSTIME. WAITMONITORINGTIME must be > 0.

    When the GPMC CLK is using divide-by-3 or divide-by-4, the WAIT signal can become valid just before the same GPMC CLK cycle as WRITEACCESSTIME.

    Can you confirm the writes and reads will be synchronous (ie. clock is used)? If asynchronous, then the WAIT signal must be valid 2 GPMC CLK cycles before WRITEACCESSTIME/READACCESSTIME for asynchronous transfers. If more time is requied from WAIT becoming valid to the WRITEACCESSTIME/READACCESSTIME, then WAITMONITORINGTIME can be increased.

    I believe your 2 listed expectations will be satisfied.
    AD multiplexing 16 bit mode - yes
    While wait signal is asserted, GPMC_CLK output forever - You may want to implement a software timeout to detect when the WAIT signal is never released. If this happens the GPMC cycle should never end, so the CLK should not stop.

    Will burst mode be used (WRITEMULTIPLE or READMULTIPLE set to 1)?

    Regards,
    Mark

  • Hi Mark-san,

    Thank you for your reply and very helpful information.
    We will use burst mode for both of RD/WR.
    GPMC will be connected to FPGA, and burst access and single access will be changed by switching CS.
    (Multiple CSs is connected to the same FPGA device.)

    Best Regards,
    Nomo

  • Hi Nomo-san,

    This all sounds fine. Please confirm burst write will be synchronous - using the GPMC0_CLK.

    Burst writes will only work in synchronous mode (WRITETYPE = 1, Write synchronous)

    Regards,
    Mark

    WRITETYPE
  • Hi Mark-san,

    Thank you for your reply.
    We'll check that WRITETYPE = 1, Write synchronous.

    Best Regards,
    Nomo