Tool/software:
Hi Team,
We are using TXU0102(CLK,CS) and TXS0108(TXD0:7) level shifter for MCU-NAND SPI 10MHz communication.
We need the Typical propagation delay info for the following condition highlighted.
Vcca = 1.8V; Vccb = 1.8V
TXU0102:
TXS0108:
Also require Min delays for TXS0108 as no values are specified in the datasheet.
And also, I have another question the Min (-40C) and Max (125C) delays given are applicable to extreme cases am i right??
Thanks and regards,
Sathish Raja C
Both voltages are the same. Why are you using level shifters?
At 1.8 V, the fastest buffers are in the AUC logic family, e.g., SN74AUC2G34. Please note that the TXS is not a buffer (a bidirectional buffer is not possible without a separate direction signal).
The min/max values cover both temperature changes and manufacturing variations. Typical values, if they were specified, would not be guaranteed.
Hello Sathish,
Are you planning to use the TXU and TXS as a SPI buffer/redriver? If so, I would not recommend the TXS since it has a very low output drive strength.
Why is there a need for typical values? LIke Clemens mentioned, min/max values are covered across temperature (worst-case) while typical values will vary.
Regards,
Josh
Hi Clemens and Joshua,
I am doing timing analysis for SPI interface which shows some failure in Setup/hold time @Flash end at Slow corner (@125C) with worst case delays.
So, we wanted to check the delays considering the typical case.
Regarding the SPI buffer, will consider your suggestions in our design.
Thanks and regards.
Sathish Raja C
Hello Sathish,
I can capture prop delay typical data for you. Since I have some unpopulated units I can provide this on Monday.
Regards,
Josh
Hello Sathish,
The TXU0102 prop delay value I captured is 10.12ns. Test condition: Frequency: 10MHz, VCCA=VCCB=1.8V, and 5pF load
Regards,
Josh
Thanks for the Data.
Do we have the Min Delay values for TXS0108 ..I think its missing in the below table - Needed for Highlighted config..
Thanks and regards,
Sathish Raja C
Hello Sathish,
Our validation team only captured prop delay max values for this part. Sorry for the inconvenience.
Regards,
Josh