• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 879 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.

F28069 Control Card Example projects and HRPWM

Prasanta Achanta
Prodigy 100 points
Other Parts Discussed in Thread: CONTROLSUITE

1) Is there a folder similar to C:\ti\controlSUITE\development_kits\F28069 controlSTICK for the F28069 ISO control card in the controlSUITE ? If not, can I use the examples in the device support folder to edit and deploy programs onto the control card ?

2) I plan to use all the 6 HRPWM channels for my project. Is there a way to insert deadband across HRPWM channels i.e ePWM1A and ePWM2A ? 

3) From the manual, it is clear that all the ePWM modules can be made to operate in sync. Does it imply that the HRPWM mode is in sync as well ?

Thank you,

Prasanta.

  • 0
    TI__Guru 57255 points

    Hi Prasanta,

    1) The key thing is the device.  The F2806x device_support examples can run on this controlCARD.  The controlSTICK examples can too (but any the cSTICK's documentation is written to tell the user what do to if you're using the controlSTICK).

    2 & 3) Yes to both in most situations.  Some of this is use-case specific though. 

    The following may be insightful:
    https://e2e.ti.com/support/microcontrollers/c2000/f/171/p/341217/1194174

    Note that in some situations/topologies, it may be possible to use the dead-band feature inside the PWM module to generate PWMB - even when using PWMA as HR.  PWMB cannot be high-resolution and so in this situation it will have a constrained amount of jitter.  This may or may not be an issue.

    ===

    Note that for the most recent set of devices (such as devices in the F2837x or F2807x family), features have been added to improve the HRPWM, synchronization and tripping so that they can be done in less software-intensive/resource-intensive/safer ways.


    Thank you,
    Brett