Miguel,

I'll give a simple answer and if you have more questions we can go deeper.

The simpler answer is that if you can deal with:

• your PWM period being some N (integer) multiple of maybe 800ns to 1.6us
• your minimum PWM period being around 2N
• your duty cycle adjustable by steps of ~12.5ns (for 80MHz clock) or 10ns (if you use 100Mhz clock

Then the answer would be yes.  If you need more like a center aligned PWM then it gets a bit more complex ... either the code and resources gets more complex or you pretty much would double the time scales we are talking about.

If these speeds exceed what you need by a lot then I would say no problem and just look at the pinout of the part to check the other features.

I'm not so sure about the GPIO count whether this includes the timer pins or not.
And our ADC pins are not useable as GPIO.    You can *convert* the pins periodically & automatically compare then in a threshold register in the ADC to get a 1 or 0 value but this takes a sample & convert time slot ... and only lets you use the pin as an input.

Miguel,

The LS1114 is a step function higher in performance in all around than the TMS570LS0432 and in addition to having 2 programmable timers (N2HET) which allow you to coordinate large #s of pins from a central, programmable unit, the LS1114 has 7 of the motor control timers ePWM that also appear on the C2000 product line.   These timers are in some sense less flexible than N2HET but they have a lot of functionality like deadband and complimentary, symmetric PWMs in hardware and can run faster because of all the dedicated hardware.     So you'll have lots of options.

Synchronization between all the ePWMs and the N2HETs is possible if you want -- or you can chose not to synchronize.

Of course this part is a little more expensive but if that's not an issue for you I would say you should have plenty of breathing room.  Just please do make sure you have your GPIO and ADC pin counts identified first, especially if you are looking at the 144 QFP package which has less pins available.  Your requirements sounded like they might be a little tight for that package but that's just off the cuff.  I'd want to see a spreadsheet of pin list versus function in your application before committing if I were you.  If you put that together (pin list and how you would want to use each pin) we'd be happy to review it for you.