S32DS PA SDK 2.9.0 eMIOS OPWMB channel cannot be driven from OPWFMB timebase

cancel
Showing results for 
Search instead for 
Did you mean: 

S32DS PA SDK 2.9.0 eMIOS OPWMB channel cannot be driven from OPWFMB timebase

358 Views
dan_teodorescu
Contributor III

Hello,

The current implementation of S32DS PA SDK 2.9.0 does not support the configuration of an eMIOS OPWMB channel with a timebase channel configured to be in OPWFMB mode. It only supports a timebase channel configured in MCB mode.

Our application requirement is for two eMIOS channels generating opposite-polarity signals, with dead-time in between, as follows:

               ________           ________                       _____
TB_CHAN : ____|        |_________|        |__________|     
          ___            ______              _______
AUX_CHAN:    |__________|      |____________|       |________

One of the channels is assigned to a BCD eMIOS channel, and the other belongs to the same eMIOS group; ie. one of the channels has to function as common timebase and pwm output.

The current driver seems to require three eMIOS channels, one functioning as an MCB timebase and two functioning as pwm outputs. This seems to be a limitation of the eMIOS pwm driver implementation and not of the eMIOS peripheral itself. Therefore, please update the driver such that:

  1. The OPWMB function will accept a timebase channel operating in OPWFMB mode.
  2. There is a way to initialize the leading and trailing edge placement for the OPWMB mode.

Attached you can see a partial implementation of the proposed solution.

Thank you,

Dan

Labels (1)
0 Kudos
2 Replies

207 Views
PetrS
NXP TechSupport
NXP TechSupport

Hi,

I guess the SDK driver is following the RM and it states "An external counter driven in MCB Up mode must
be selected from one of the counter buses." for OPWMB mode.

Anyway OPWFMB seems to be functional too as counter bus.

BR, Petr 

0 Kudos

207 Views
dan_teodorescu
Contributor III

Hi Petr,

You are correct, the counter must be in MCB mode (such that it counts from 1 ... A1) and count UP only, otherwise the behavior is unexpected or undefined. I would assume that the counter part of the UC configured as OPWFMB would operate as MCB UP mode, at least the RM description of MCB and OPWFMB seems identical with respect to counter control. If this is the case, should the documentation be updated? This will free up an eMIOS channel in our application.

Thank you,

Dan

0 Kudos