• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 518 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.

PWM Configuration and Control for Acceleration Profile

Nathan Smith
Intellectual 620 points
Other Parts Discussed in Thread: HALCOGEN

I am using a TMS570 dev kit, CCS 5.4, Halcogen 3.02.02, and the FreeRTOS that came with CCS.

I want to dynamically change the period of a PWM signal to implement an acceleration profile for a stepper motor.

I am using end_of_duty and end_of_period interrupts to give semaphores to unblock tasks to calculate the next period length and update the PWM.

However, at the beginning of the process I am getting two pulses of the same width, which should not happen.

I am calling into question my implementation of the PWM commands.

If I use Halcogen and FreeRTOS to configure and control PWM signals in the N2HET, does that accomplish the same thing as using the separate HET IDE?

If I use pwmSetSignal followed by pwmStart, is that redundant?

What happens when pwmSetSignal is called on a running PWM?

  • 0
    TI__Genius 11645 points
    Hi,

    Sorry for the delayed response, somehow missed this thread.

    Using HET IDE and halcogen generated PWM's are slightly different, with Halcogen you get certain pre-defined routines with HET RAM code for generating PWM and set signal essentially writes the new value on to control and data fields with values given by you which is a bit simpler to use compared to generating your own het program.

    If I'm not wrong once you set the required period and duty cycle, you then enable the pwm using pwm start.

    Post that if you are using the pwmsetsignal, that should change the duty/period of PWM.

    I'll request our Halcogen experts to have a quick look at this as well to re-confirm.