Vikrant More <vikrant8051@...>
I'm not able to understand what you are saying.
Is that means Zephyr PWM (fade_led example) is using software to generate PWM instead of separate dedicated SoC's internal PWM module ?
On Thu, Feb 8, 2018 at 3:01 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:
Your main.c uses pwm_nrf5_sw.c driver which has conflict with BT features on nRF52840...
I do not see use of NRF_PWM0 in you main.c, of course, yes your code in the devzone does, hope you get some help there
and can contribute a Zephyr driver.
I am not familiar with NRF_PWM0, hence not much help for you.
We are in the process of contributing driver based on nRFx external interfaces, you may just have to wait for it.
On Thu, Feb 8, 2018 at 2:32 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@nordicsemi.no> wrote:
Hi Vikrant,
As i said, there is possible overlap of PPIs with BT Controller. PPI channel 16 and 17
overlap with Code PHY feature in nRF52840.
I will try to send a PR wherein you could (correctly) disable Coded PHY support in nRF52840
so as to have PPI Channels from 14 to 19 available for 3 LEDs.
Until then, use 3 LEDs and expect 2nd LED to malfunction.
Again, I will like to iterate that for nRF52840, h/w PWM driver has to be used, feel free
to contribute (isn’t it fun to develop than test ;) )
Regards,
Vinayak
From: Vikrant
More [mailto:vikrant8051@...]
Sent: Thursday, February 08, 2018 9:31 AM
Hi Vinayak,
I also able to generate & vary PWM as you did.
Problem arises when we create two channels from PWM0.
One channel -> LED1
Second Channel -> LED2
When I vary LED1 pulse width, sometimes it affects intensity of LED2
Similarly, when I vary LED2 pulse width it affects intensity of LED1
For details I've attached my main.c. Please have a look.
Use nRF connect to send data
send 0100 (ascii string) -> it is for LED1
send 1100 (ascii string) -> it is for LED2
And you will find what I'm saying.
On Thu, Feb 8, 2018 at 1:37 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@nordicsemi.no>
wrote:
Hi Vikrant,
I have run the upstream fade_led sample on nrf52840-PDK, I see no regression, the brightness
changes every second (up and then down so on).
I advice you to debug your implementation as I have no visibility to your design.
Regards,
Vinayak
I'm working nRF52840-PDK board.
On Thu, Feb 8, 2018 at 1:21 PM, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@nordicsemi.no>
wrote:
Hi Vikrant,
Please try the PWM without the BT Controller included. There could be some PWM regression
due to changes in controller implementation.
That said the nrf5_sw driver is software variant designed for older nRF51 SoCs. For newer
nRF52x series h/w PWM’s should be used.
Nrf5_sw will work provided careful mitigation of used PPI and timers between the driver
and BT controller use.
Which SoC are you using?
Regards,
Vinayak
Hi Marti,
>>Are you using the latest master?
Yes
On Thu, Feb 8, 2018 at 1:23 AM, Marti Bolivar <marti@...> wrote:
Hi Vikrant,
Are you using the latest master?
Three improvements to nRF PWM went in fairly recently:
3f1dbfda1 pwm: nrf5_sw: don't disable timer if another channel is still active
ab399a1cf pwm: nrf5_sw: do not use 'inversed' polarity by default
cec073c35 pwm: nrf5_sw: add support for SYS_LOG
On Wed, Feb 7, 2018 at 1:59 PM, Vikrant More <vikrant8051@...> wrote:
I took reference of $zephy/samples/samples/fade_led project
& add following parameters in my prj.conf
CONFIG_SYS_LOG_PWM_LEVEL=4
Could you please inform me, what I should do besides this ??
On Feb 7, 2018 11:36 PM, "Felipe Neves" <ryukokki.felipe@...> wrote:
Did you configure what pins are associated to pwm duty_cycles on the menuconfig?
Best
Felipe
2018-02-07 10:15 GMT-02:00 Vikrant More <vikrant8051@...>:
I've added following lines in my project main ()
pwm_dev = device_get_binding(PWM_DRIVER);
if (!pwm_dev)
{
printk("Cannot find %s!\n", PWM_DRIVER);
return;
}
while(1)
{
if(pwm_pin_set_usec(pwm_dev, PWM_CHANNEL0, PERIOD, pulse_width0))
{
printk("pwm pin set fails\n");
}
if(pwm_pin_set_usec(pwm_dev, PWM_CHANNEL1, PERIOD, pulse_width1))
{
printk("pwm pin set fails\n");
}
k_sleep(100);
}
And using bluetooth updating value of pulse_width0 & pulse_width1. Those two are defined as global variables.
pulse_width0 --> LED_1 on nrf52840_PDK
pulse_width1 --> LED_2 on nrf52840_PDK
I'm able to update value of both these variables using Bluetooth.
I used printk to check it. My logic is perfect.
But if I vary pulse_width0 then it affects intensity of LED2
& if I vary pulse_width1 then it affects intensity of LED1.
Why ? Is anyone found this BUG ?
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users
--
Felipe S. Neves
Embedded software & systems engineer
_______________________________________________
Zephyr-users mailing list
Zephyr-users@lists.zephyrproject.org
https://lists.zephyrproject.org/mailman/listinfo/zephyr-users
|
