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.
Here is what we read in the last paragraph in SPRUH22C–April 2012–Revised February 2013 page 817.
In SFO_TI_Build_V7.lib, the SFO() function also updates the HRMSTEP register with the scale factor
result. If the HRCNFG[AUTOCONV] bit is set, the application software is responsible only for setting
CMPAHR = fraction(PWMduty*PWMperiod)<<8 or CMPBHR = fraction(PWMduty*PWMperiod)<<8 or
TBPRDHR = fraction (PWMperiod) while running SFO() in the background. The MEP Calibration
Module will then use the values in the HRMSTEP and CMPAHR/CMPBHR/TBPRDHR register to
automatically calculate the appropriate number of MEP steps represented by the fractional duty cycle
or period and move the high-resolution ePWM signal edge accordingly. In SFO_TI_Build_V7.lib, the
SFO() function does not automatically update the HRMSTEP register. Therefore, after the SFO
function completes, the application software must write MEP_ScaleFactor to the HRMSTEP register
(EALLOW-protected).
The last and the first sentence are contradictory.
Which one is true?
Best regards
Joel,
I expect the first statement to be correct and that the last two sentences in your quote should be deleted from the guide.
I am waiting for confirmation.
Thank you,
Brett