IIC specification

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 
1,613件の閲覧回数
posedge_clk
Contributor I

I am learning NXP UM10204, there is a question that confuses me.

On page 44, table 11, note3. Why does the holding time have a maximum value?

In my understanding, there is usually no requirement for a maximum holding time.

Why data must has a valid time? 

As a host, can't I keep my data valid all the time?

タグ(1)
0 件の賞賛
返信
1 解決策
1,472件の閲覧回数
JozefKozon
NXP TechSupport
NXP TechSupport

Dear Xin,

these data were tested and validated long time ago. It is difficult to answer your questions. When designing your system, please keep the timing data within the boundaries stated in the UM10204. You need to adjust the waveforms with your MCU, so it will look similar to the required waveform for the Slave you want to communicate with. It depends from component to component. But the timings must be within the boundaries state in the UM10204.

With Best Regards,

Jozef

元の投稿で解決策を見る

0 件の賞賛
返信
7 返答(返信)
1,564件の閲覧回数
posedge_clk
Contributor I

As shown in the following figure, i don't understand the max data valid time.

As a host, can't i keep the data is valid all the time until setup next data?

posedge_clk_0-1693445138560.png

 

0 件の賞賛
返信
1,550件の閲覧回数
JozefKozon
NXP TechSupport
NXP TechSupport

Dear Xin,

the tHD;DAT maximum time is not a must. It could be up to the defined maximum time, but the minimum value is also sufficient. 

With Best Regards,

Jozef

0 件の賞賛
返信
1,541件の閲覧回数
posedge_clk
Contributor I

What will happen if the maximum value of data valid time is exceeded ?

For example, in fast mode, the speccification requires the max data hold time is 900ns, what will happen if i hold it for 1us?

posedge_clk_0-1693470155606.png

 

0 件の賞賛
返信
1,524件の閲覧回数
JozefKozon
NXP TechSupport
NXP TechSupport

Dear Xin,

the tHD;DAT never can be longer, than tVD;DAT or tVD;ACK. If you increase the tHD;DAT length, the tVD;DAT and tVD;ACK are automatically also increased.

JozefKozon_0-1693481831010.png

With Best Regards,

Jozef

0 件の賞賛
返信
1,499件の閲覧回数
posedge_clk
Contributor I

Yes, I know the  the tHD;DAT never can be longer than tVD;DAT or tVD;ACK.
But why? 

1. What is the purpose of designing tVD;DAT and tVD;ACK ?

In the above example, I did not see any points where exceeding tVD;DAT and tVD;ACK may cause problems.There is 300ns free time, as a host, I think i can keep the data is valid until next setup.

posedge_clk_0-1693533260392.png

2. In my experience, design usually only imposes constraints on the minimum data valid time and not on the maximum data valid time. Why does this specification define the maximum data valid time?

3. Also, if this maximum data valid time is violated, will the slave not be able to receive data correctly?

 

 

0 件の賞賛
返信
1,473件の閲覧回数
JozefKozon
NXP TechSupport
NXP TechSupport

Dear Xin,

these data were tested and validated long time ago. It is difficult to answer your questions. When designing your system, please keep the timing data within the boundaries stated in the UM10204. You need to adjust the waveforms with your MCU, so it will look similar to the required waveform for the Slave you want to communicate with. It depends from component to component. But the timings must be within the boundaries state in the UM10204.

With Best Regards,

Jozef

0 件の賞賛
返信
1,589件の閲覧回数
JozefKozon
NXP TechSupport
NXP TechSupport

Dear Xin,

you probably have an older UM10204 version. Please check the UM10204 attached.

With Best Regards,

Jozef

0 件の賞賛
返信