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.

LAUNCHXL-F280049C: LAUNCHXL-F280049C

Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: C2000WARE

Dear TI engineers,

I had a question when I have studied the example of cla which called cla_ex1_background_task. Why the EPWM4A did not generate duty cycle? The register configuration seemed to generate 50% duty cycle. But only high electrical level appeared in oscilloscope?

Looking forward to your reply. 

Best wishes for you.

  • Hi Coke Kou,

    To confirm you're running the 'cla_ex1_bankground_task' C2000ware example? Located here: C:\ti\c2000\C2000Ware_2_00_00_03\device_support\f28004x\examples\cla

    Can you double check that you're probing the correct pin on the LaunchPad? Should be GPIO6 which is pin 78 (on silkscreen).

    Best,

    Kevin

  • Dear Kevin,

    Ths for your reply,

    I have confirmed that I chose the right example and pin showed in pictures.

    I also have detected the 97 pin which is GPIO6 of the cpu. It was also high electrical level. So,what is the problem?

    Looking forward to your reply. 

    Best wishes for you.

  • Dear TI engineers,

    Could anyone give me some suggestion?

  • Hi Coke Kou,

    Sorry for the delay. I'll try this example on my end today to see if I experience anything different.

    In the meantime, can you try the DriverLib example 'cla_ex2_background_task' rather than the bit-field one, located:

    C:\ti\c2000\C2000Ware_2_00_00_03\driverlib\f28004x\examples\cla

    It looks like it does the exact same thing, except using driver libraries. You could also try a simpler example just to make sure your scope/board are working OK. Maybe the 'gpio_ex2_toggle' example:

    C:\ti\c2000\C2000Ware_2_00_00_03\driverlib\f28004x\examples\gpio

    Best,

    Kevin

  • Hi Coke Kou,

    Looks like the bit-field example has EPWM4 configured incorrectly (EPWM4_DUTY_CYCLE is wrong I believe), but the DriverLib example does work as intended. I'll file an internal ticket to have this example fixed.

    Thanks for bringing this to our attention and sorry for the inconvenience.

    Best,

    Kevin