ICU IPWM Capture Cycle Loss

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

ICU IPWM Capture Cycle Loss

ソリューションへジャンプ
1,607件の閲覧回数
Du_0224
Contributor III

Hello NXP engineers.

Test environment:

S32K314 + RTD2.0.2

* Autosar Version : 4.4.0
* Autosar Revision : ASR_REL_4_4_REV_0000
* Autosar Conf.Variant :
* SW Version : 2.0.2
* Build Version : S32K3_RTD_2_0_2_D2211_ASR_REL_4_4_REV_0000_20221129

 

I'm testing with an IPWM acquisition lost cycle problem.

IPWM clock 1M
A jump problem was found during testing of the 3K 50% duty cycle.
Troubleshooting with an oscilloscope, the waveforms from the hardware input to the MCU are correct. There is no cycle loss problem

And the value after the jump is basically around 1.5K, 75% duty cycle.

Based on the phenomenon it is suspected that the IPWM acquisition is missing a cycle?

Du_0224_0-1704191071964.png

Du_0224_2-1704191146143.png

Du_0224_3-1704191152996.png

 

1M clock, counting: 3KHz, 50% duty cycle. The count should be: period value ≈ 333, A-B ≈ 167.

According to the phenomenon, the pulse width is correct, but the duty cycle is calculated incorrectly because the period value is not correct.
The debug adds variables to save the time of arrival of each pulse edge:

Du_0224_4-1704191195511.png

The test found that the value latched into register B is just not right:

Du_0224_5-1704191235621.png

 

 

 

タグ(1)
0 件の賞賛
返信
1 解決策
1,569件の閲覧回数
Du_0224
Contributor III

Problem solved, this issue is closed

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
1,587件の閲覧回数
Du_0224
Contributor III

I performed a further test by doing a register read at the interrupt general entry, but the phenomenon is the same.

Du_0224_2-1704253284189.png

 

Du_0224_1-1704253256812.png

 

0 件の賞賛
返信
1,570件の閲覧回数
Du_0224
Contributor III

Problem solved, this issue is closed

0 件の賞賛
返信