This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F280039C: Using Enhanced Pulse Width Modulator (ePWM) Module for 0-100% Duty Cycle Control Application Report

Part Number: TMS320F280039C

Dear Champs,

I am asking this for our customer.

From

TRM 20.6.5 Waveforms for Common Configurations

the app note - spraai1 (https://www.ti.com/lit/an/spraai1/spraai1.pdf?ts=1675773045683

This post 

e2e.ti.com/.../tms320f28075-type-4-epwm-to-generate-full-range-0-100-duty-cycle-waveform-w-o-isr-intervention

The user wants to clarify the conditions and symptoms for this issue.

Question:

1. Conditions:

ONLY when CMPA/CMPB is from 0 to a non-zero value

ONLY for up-down count (that is, excluding up-count and down-count).

Is it right?

2. Occurrence frequency 

If the conditions meet, it will ALWAYS happen rather than INTERMITTENLY happen.

Is it right?

3. Symptom

What is the symptom here when this issue happens?

Would you please make it clearer?

Wayne

  • Hi Wayne,

    I am looking into your query, will respond before thursday.

    Best,

    Uttam

  • Dear Uttam,

    Is there any update?

    The user has seen unexpected waveforms when setting CMPA=0 (supposed to be 0% duty but 100% intermittently for a PWM cycle), so they are analyzing this and want us to clarify conditions and symptoms of this boundary issue.

    Wayne

  • Hello Wayne,

    Sorry for the delay, this thread has been re-assigned to Luke. He will get back to you as early as possible.

    Best,

    Uttam 

  • Hey Wayne, apologies for the delayed response on this thread, I am looking into this now.

  • Hey Wayne,

    Is this the issue from the thread you are referring to?

    "On type 0 EPWM, like device F2808, it seems CMPA will be loaded as 0 once TBCTR=0, and then the comparison action will be ignored thus CAU event will NOT occur so output high will not work"

    If this is correct:

    "ONLY when CMPA/CMPB is from 0 to a non-zero value"

    Do you actually mean from non-zero value to 0, or was this intentional?

    "ONLY for up-down count (that is, excluding up-count and down-count)."

    I believe this condition is independent of the count-mode but rather whether the counter is incrementing or decrementing. So for example a load of CMPA = 0 in up-count mode could result in the same ignored event.

    Thank you,

    Luke

  • Dear Luke,

    We are still confused.

    In fact, the user just wants us to clarify all the conditions and considerations when using CMPA/CMPB=0 in up-count and up-down count and what are the symptoms and their occurrence freq. (always or intermittent) because TRM 20.6.5 Waveforms for Common Configurations and the post in the original post confuse us.

    For example, TRM 20.6.5 Waveforms for Common Configurations says:

    "To achieve 0-100% asymmetric PWM use the following configuration: Load CMPA/CMPB on TBPRD. Use the Zero action to set the PWM and a compare-up action to clear the PWM. Modulate the compare value from 0 to TBPRD+1 to achieve 0-100% PWM duty."

    Why it asks to Load CMPA/CMPB on TBPRD rather than on ZRO? Isn't ZRO and PRD at the same cycle on TBCTR=0 for up-count mode? Is load on TBPRD a must when using CMPA/CMPB=0?

    For example, the referred post says, it is only for up-down count which implies up-count does not have this concern. But does F28003x type-4 PWM still the same as that on the post?

     

    For example, the app note "spraai1" says, this would happen from CMPA/CMPB = 0 to non-zero as well as from non-zero to CMPA/CMPB = 0, and in TRM 20.6.5 Waveforms for Common Configurations, it includes this app note. Why?

    All these confuse the users, who just wants to confirm how to use CMPA/CMPB=0 in a right way.

    Would you please help clarify?

  • Hey Wayne,

      and I are working on this issue together, I will close this thread since this has moved to email but feel free to respond here if it's easier for the customer.

    --Luke