• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 180 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28388D: Bug in Sysconfig code generation for HRPWM phase control

Adrien Thurin
Intellectual 526 points
Part Number: TMS320F28388D
Other Parts Discussed in Thread: SYSCONFIG, , C2000WARE

Tool/software:

Hi,

I am developing a product using a TMS320F28388D, using Sysconfig for the peripheral configuration. One of the converters is a phase-shifted full bridge, so I am looking at HRPWM configuration with phase regulation.

The program works without HRPWM activated. However, when HRPWM is activated in sysconfig, the PWMs are no longer synchronized.

I believe the configuration is correct :

And yet, no synchronisation of the 2 ePWMs.

Upon investigation, I found that the should-be-sync-ed ePWM has his EPwmXRegs.TBCTL.PHSEN = 0.

Looking at the code generated by Sysconfig, I have the HR phase enabled twice, but the regular phase is not enabled :

If I add the "normal phase" enable somewhere manually :

EPWM_enablePhaseShiftLoad(PWM_PSFB_DELAYED_BASE);

This line causes EPwmXRegs.TBCTL.PHSEN = 1. Then the ePWMs are sync-ed.

I am under the impression that when HRPWM and HR phase are enabled, the box for phase enabling is mis-translated into the HRPWM_ function rather than the EPWM_ function. Which causes the issue with synchronisation of the ePWMs.

Best regards,

Adrien