S32K中的主题 EMIOS PWM

EMIOS PWM

vmhb — Fri, 07 Jun 2024 13:28:32 GMT

I am trying to configure 2 pwm signals on the S32k3x4EVB-Q172 EMIOS 1. Both PWM's have the same input source clock and can be set to different duty cycles. They are both OPWMB and the only difference I can see between the two signals is that one is a type H port and the other a type X. I have included screen shots of the setups. Is there anything different about these type H channels?

From initialisation the X port produces the correct period and duty but the type H port does not. If I increase the duty from 0 - 100 in 5% steps the type X port responds correctly at each stage. The type H port does not report any pulse until 30%. At this point the period of the H port is correct but the period is nonsense

Here is

the trace at 30%

At 45% the TYPE H channel show 75% where the type X channel shows 45%

At 55% the TYPE H channel has gone 100%

I have tried different ports, different periods but the symptoms remain. The only difference I can see is that the channel CNT register seems to sit at the requested duty count for the type H whereas on the X channel it counts.

Re: EMIOS PWM

VaneB — Mon, 10 Jun 2024 20:25:31 GMT

Hi @vmhb

I worked on replicating your issue. According to the results of the tests, the issue is present on channel type X, and channel types H and Y work as expected. Refer to the attached images.

I will escalate this situation with the corresponding team. While we are waiting for the internal team's response, the workaround I can give for this situation will be to use the channel types H and Y.

B.R.

VaneB

Re: EMIOS PWM

VaneB — Wed, 12 Jun 2024 23:05:10 GMT

After several tests, we concluded that this behavior is related to the hardware design of the S32K3x4EVB-Q172, We did some testing with other pins for each channel and most of them work as expected. The only channel I could not get working was channel 15 due to EVB pin availability and pin connections to other devices. In conclusion, all channel types should have the same behavior under the same configurations as the ones shared before.