I'm developing a product with the nRF52840, using Zephyr (Toolchain & SDK version 2.7.0). Is there a way to set up two PWM outputs having the same frequency and duty cycle, but with opposite polarity (such that when one pin goes high, the other goes low, and vice-versa)?
I'll also need to start and stop the outputs together (or at least close to it).
Thanks in advance for any help,
--mkj
mkjones said:Since my duty cycle is 50%, the pulse length for pwm_2 is exactly the same as pmw_1; I don't understand how this gets the opposite polarity.
the second channel of the PWM configured with period_usec - duty_cycle_usec, meaning it starts low and becomes high when Channel 0 transitions to low.
The error:'__device_dts_ord_DT_N_S_soc_S_pwm_4001c000_P_pwms_IDX_0_PH_ORD' undeclared
and the code looks something like, not compiled but to show you the logic
#include <zephyr/drivers/pwm.h>
const struct pwm_dt_spec pwm = PWM_DT_SPEC_GET(DT_NODELABEL(pwm0));
void configure_pwm_single_instance(uint32_t period_usec, uint32_t duty_cycle_usec)
{
if (!device_is_ready(pwm.dev)) {
printk("Error: PWM device is not ready.\n");
return;
}
int ret = pwm_set(pwm.dev, 0, PWM_USEC(period_usec), PWM_USEC(duty_cycle_usec));
if (ret) {
printk("Failed to configure channel 0 (normal polarity): %d\n", ret);
}
ret = pwm_set(pwm.dev, 1, PWM_USEC(period_usec), PWM_USEC(period_usec - duty_cycle_usec));
if (ret) {
printk("Failed to configure channel 1 (inverted polarity): %d\n", ret);
}
printk("PWM configured with complementary signals on a single instance.\n");
}
The line that will not compile for me is:
const struct pwm_dt_spec pwm = PWM_DT_SPEC_GET(DT_NODELABEL(pwm0));
It clearly does not like the way I've defined my pwm device. I have tried following the two (different) examples:
https://blog.golioth.io/adding-pwm-sound-in-zephyr/
Nothing I do makes the compiler happy. Can you also give me the contents of the .overlay file that will make the code sample you've provided compile?
This is *incredibly* frustrating; the whole DTS thing is certainly powerful, but unless you are already an expert (and I am not), it is virtually impossible to produce code that will compile (never mind work correctly) unless you can find a sample that does exactly what you need.
The line that will not compile for me is:
const struct pwm_dt_spec pwm = PWM_DT_SPEC_GET(DT_NODELABEL(pwm0));
It clearly does not like the way I've defined my pwm device. I have tried following the two (different) examples:
https://blog.golioth.io/adding-pwm-sound-in-zephyr/
Nothing I do makes the compiler happy. Can you also give me the contents of the .overlay file that will make the code sample you've provided compile?
This is *incredibly* frustrating; the whole DTS thing is certainly powerful, but unless you are already an expert (and I am not), it is virtually impossible to produce code that will compile (never mind work correctly) unless you can find a sample that does exactly what you need.
OK, I've got it to compile (I ended up using C:\ncs\v2.7.0\nrf\samples\bluetooth\fast_pair\locator_tag\ as a model):
However, when I execute this function:
I only get output from the second channel (GPIO 0.23); GPIO 0.22 just stays low.
This should have been a very simple thing, sorry that it is taking this long, i will test this tomorrow on DK, it shouldn't be this difficult to generate an inverted signal on two pins using a PWM.
Through much trial-and-error, I finally got it working. First, I gave up on trying to use PWM_DT_SPEC_GET; in the end, I just used the PMW device directly. Also, the other bit of magic which was not obvious was that each channel needs to use a different function (so, PMW_OUT0 and PMW_OUT1 below) So, here's the overlay file:
And here's the source file; the final bit of magic was to use PWM_POLARITY_NORMAL for one channel and PWM_POLARITY_INVERTED for the other. Now I get identical (but inverted) waveforms on the two channels: