devel@lists.zephyrproject.org

Re: Bluetooth Mesh Advertisement issues

Hi Paul, Are you saying the controller doesn't seem to do what it's directed to do through HCI? We'd need the controller folks to comment on that then. This might work, but it looks quite

By Johan Hedberg · #1745 ·

Re: [Bluetooth] Is BT 5.0 specific features supported by Zephyr for nRF52840 board yet?

Hi Cufi, Thanks for fast response. With the help of your pointer, now I am able to at-least verify the basic HCI LE 2M PHY commands like - Read PHY, LE Set Default PHY, LE Set PHY By the way, the

By Anupam Roy · #1747 ·

Bluetooth Mesh Advertisement issues

Hi again, I believe I’ve found 2 issues in the BLE Mesh implementation – could someone check on that? The following measurements were done with a Friend Poll at the LPN (nRF52-PCA10040).

By Gavrikov Paul <Paul.Gavrikov@...> · #1744 ·

Re: (#BluetoothMesh) just binding APP-key allow SRV to process the message

I'm still waiting for reply. Is it bug or I'm doing something wrong ?

By Vikrant More <vikrant8051@...> · #1743 ·

Re: Bluetooth Mesh: Bad values for continuous scan

Hi Vinayak, I re-ran my analysis with 0x4, 0x10, 0x100 and 0x4000 values (continuous scan, 1000 sent advertisements, re run 3x). I do see an improvement of roughly 5% for 0x10. A very slight

By Gavrikov Paul <Paul.Gavrikov@...> · #1742 ·

Re: [Zephyr-users] Power Configuration of nrf52840

Thanks everyone !!! Adding these lines does the job. NRF_NVMC->CONFIG = NVMC_CONFIG_WEN_Wen; while (NRF_NVMC->READY == NVMC_READY_READY_Busy){ } NRF_UICR->EXTSUPPLY = 0x01; while

By ashish.shukla@corvi.com <ashish.shukla@...> · #1741 ·

Re: [Bluetooth] Is BT 5.0 specific features supported by Zephyr for nRF52840 board yet?

Hi Anupam, All the features you mention are supported on the nRF52840 *except* LE Extended Advertising. I suggest you take a look at the controller feature list in order to enable/disable

By Carles Cufi · #1740 ·

Re: "dummy-flash" device tree possible bug?

Hi Diego. Looks like Maureen has pointed you in the right direction. Thanks Maureen! -- Michael

By Michael Hope <michaelh@...> · #1739 ·

Re: "dummy-flash" device tree possible bug?

Hello Maureen, Thanks for the suggestion. This is an interesting approach as well. I still want to understand how to use the "dummy-flash" and if I can assign the same memory node for the flash and

By Diego Sueiro · #1738 ·

Re: "dummy-flash" device tree possible bug?

Hi Diego, Take a look at the mimxrt1050_evk board. The SoC doesn’t have embedded flash, so I mapped the flash entry to ITCM which is in SRAM. “zephyr,sram” is mapped to DTCM, which is a

By Maureen Helm · #1737 ·

Re: Building Zephyr like there's no CMake

Hi, these scripts are great (albeit not upstreamable), these are my aliases, I combine them with "export BOARD": alias t='~/zephyr/scripts/sanitycheck -T$PWD' alias gn='git clean -ffdx' alias

By Sebastian Boe · #1736 ·

[Bluetooth] Is BT 5.0 specific features supported by Zephyr for nRF52840 board yet?

Hello Zephyr Developers, I am looking for zephyr based application for verifying BT 5.0 specific features like LE Extended Advertising, LE Long Range (2M PHY), LE High Speed (2M PHY) etc. on my

By Anupam Roy · #1735 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

Hi Vikrant and Neves, I have submitted a PR that will correctly “disable” Coded PHY support in nRF52840, in turn avoiding the PPI channels 14 to 19 and hence usable by pwm_nrf5_sw.c

By Chettimada, Vinayak Kariappa · #1734 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

Hi Felipe, Thanks for you support. I also used this style to take advantage of SoC built-in PWM module. But was not able to generate PWM with different pulse_width using same instance. Now it is

By Vikrant More <vikrant8051@...> · #1733 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

Hello guys. @Vikrant you are right, the current implementation of nrf pwm's driver uses a software based PWM combined with the PPI. Here in my work we are using zephyr built for nordic target with

By Felipe Neves <ryukokki.felipe@...> · #1732 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

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 ?

By Vikrant More <vikrant8051@...> · #1731 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

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

By Chettimada, Vinayak Kariappa · #1730 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

>> 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 ;) ) Means ?? I am using h/w PWM only !! Have you looked

By Vikrant More <vikrant8051@...> · #1729 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

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

By Chettimada, Vinayak Kariappa · #1728 ·

Re: [Zephyr-users] Buggy PWM driver for nRF52

Hi Vinayak, fade_led sample runs as expected. We are trying to generate PWM on two channels. Adding pwm_pin_set_usec(pwm_dev, PWM_CHANNEL0,PERIOD, pulse_width); pwm_pin_set_usec(pwm_dev,

By ashish.shukla@corvi.com <ashish.shukla@...> · #1727 ·

Messages