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.

TMS320LF2407A External memory Interface Timing Specification Question

Other Parts Discussed in Thread: TMS320LF2407A

My question is regarding the external memory interface timing of the TMS320LF2407A. On page 101 of SPRS145L, rev. Sep 2007, it lists the setup time of data to the write strobe, tsu(D)W as (2H-17) nsec. In our system, H=12.5 nsec, so tsu(D)W=8nsec. However, with multiple wait states, I would expect this setup time to increase. For example, if we have two wait states (2 x 25ns), then I would expect that tsu(D)W=58nsec. Can anyone confirm if this is correct?

Also, there is another parameter for the enable time when the DSP starts driving the bus, ten(D)COL. The timing diagram on p.102 implies that the data is valid as soon as it is enabled (there is no driven, but grayed out area indicating invalid data is being driven). Normally, I would expect that the data begins being driven by the DSP after ten(D)COL, but won't necessarily be valid until tsu(D)W is satisfied. Does anyone know if this is correct?

For reads, I have a similar question regarding the parameters ta(RD) (Read data access time) and tsu(D)RD (read data setup time). If wait states are inserted to increase the time for external logic to access data, I would expect ta(RD) to increase by the amount of wait states added. Does anyone know if this is also true?

Also, on read accesses, it seems to me that tsu(D)RD is the critical time constraint to be met by the input data to the DSP, so as long as tsu(D)RD, it may not be necessary to meet ta(RD).

.

  • Hi Andrew,

     In our system, H=12.5 nsec, so tsu(D)W=8nsec. However, with multiple wait states, I would expect this setup time to increase. For example, if we have two wait states (2 x 25ns), then I would expect that tsu(D)W=58nsec. Can anyone confirm if this is correct?

    Your understanding is correct. 

      Normally, I would expect that the data begins being driven by the DSP after ten(D)COL, but won't necessarily be valid until tsu(D)W is satisfied. Does anyone know if this is correct?

    Yes, data enable and data valid are two different parameter. Data enable is used to avoid bus contention and it means by that time no other driver should be driving the bus whereas data valid (or setup time) is when data will be stable and can be sampled.

    For reads, I have a similar question regarding the parameters ta(RD) (Read data access time) and tsu(D)RD (read data setup time). If wait states are inserted to increase the time for external logic to access data, I would expect ta(RD) to increase by the amount of wait states added. Does anyone know if this is also true?

    Yes, that's also correct. As you mentioned in your last point, read setup time is what critical here and one need to increase the wait state only if not able to meet that timing.

    Regards,

    Vivek Singh