trying to solve
> this, but its deep in the core system where this CONFIG_PWM_PULSECOUNT has
> effect. If I only had more time
>
> Ben
>
> -Oorspronkelijk bericht-
> Van: raiden00pl
> Verzonden: dinsdag 6 april 2021 08:10
> Aan: dev@nuttx.apache.org
> Onderw
t-
Van: raiden00pl
Verzonden: dinsdag 6 april 2021 08:10
Aan: dev@nuttx.apache.org
Onderwerp: Re: PWM advanced and normal timers (STM32)
As far as I can remember, it never worked that way. If you enable PULSECOUNT,
you can only use timers that support this feature.
Other PWM instances wil
As far as I can remember, it never worked that way. If you enable
PULSECOUNT, you can only use timers that support this feature.
Other PWM instances will not work properly.
sob., 3 kwi 2021 o 17:19 napisał(a):
> So /dev/pmw0 = TIM1
> /dev/pmw1 = TIM4
>
> All well.. but with CONFIG_PWM_PULSEC
So /dev/pmw0 = TIM1
/dev/pmw1 = TIM4
All well.. but with CONFIG_PWM_PULSECOUNT only TIM1 is working when you
give in counts but with counts=0 nothing happens
TIM4 is quitting immediatly. with CONFIG_PWM_PULSECOUNT DISABLED I can use
both in a generic way...
I think the:
#i
