-----Original Message-----
From: <users@...> on behalf of Venkat Rao Vallapaneni <vallapaneni@...>
Date: Thursday, 25 October 2018 at 3:14 PM
To: "users@..." <users@...>
Subject: [Zephyr-users] BT840F EV mesh without crystal

Hi,
I have tried mesh on-off sample program on nRF52 DK with and without using crystal and it works fine. I am able to provision nRF52 DK using bluez.
When I try mesh program on Fanstel BT840F evaluation board with crystal, I am able to provision BT840F. But when I disable by crystal by adding these below lines to my prj.conf, I am not able to provision. I am able to see it as unprovisioned node which
means advertising is fine but not sure why provision fails. Any quick help/hint on debug is appreciated. BT840F is nrf52840 based and nrf52 DK is nrf52832 based. As RC is internal to SoC, I am not expecting any issues with DK or EV as they are working fine
with crystal. I am using nrf52840_pca10056 as board definition.

Is there anything wrong in configuration for nrf52840 as compared to nrf52832 in relation to crystal?


prj.conf:
CONFIG_CLOCK_CONTROL_NRF5_K32SRC_XTAL=n
CONFIG_CLOCK_CONTROL_NRF5_K32SRC_RC=y

Bluez meshctl log:
[meshctl]# discover-unprovisioned on
SetDiscoveryFilter success
Discovery started
Adapter property changed
[CHG] Controller 00:1A:7D:DA:71:13 Discovering: yes
Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
Device UUID: 9f05b4608cd600000000000000000000
OOB: 0000
Mesh Provisioning Service (00001827-0000-1000-8000-00805f9b34fb)
Device UUID: c911d60241cf00000000000000000000
OOB: 0000
[meshctl]# provision c911d60241cf00000000000000000000
Trying to connect Device CF:41:02:D6:11:C9 nRF52DK
Adapter property changed
[CHG] Controller 00:1A:7D:DA:71:13 Discovering: no
Failed to connect: org.bluez.Error.Failed
[meshctl]#


Thanks,
Venkat.