ble_app_uart_coexist on pca10056(nrf52840) not advertising as mesh node

[kunal1234]

Hi,

I am using mesh SDK 4.0.0 and nRF SDK 16.0.0. I ported the ble_app_uart_coexist example from mesh SDK to build OK for pca10056 board (nRF52840) by following the instructions on Nordic Infocenter. I can successfully use the "ble_app_uart" part of the example by making BLE connection with the board but I don't see the node in nRF Mesh android app-> Add Node->'Looking for unprovisioned proxy nodes'. I assume it should show up as an unprovisioned node in the app. I have successfully run light-switch mesh example on this board previously. In this devzone case case48109 ,one reply says "The reason that you aren't seeing the device in the nRF Mesh app is probably cause it is advertising as a BLE device. The nRF Mesh app will only pick up devices that is broadcasting as a unprovisioned node." . While flashing the board, I did Erase All and then downloaded the firmware from Segger IDE. So I guess that removes any provisioning data that was on the board. I did not edit the coexist example code in any way. I only edited the DEVICE_NAME macro.

1) How do I get it to advertise as mesh node ? 

2) I ported a pca10040 example to use with pca10056 board. How do I verify that the right softdevice s140 and the mesh stack is really being flashed during the download process?

Thank you

-Kunal

[Mttrinh]

Hi,

You won't be able to see the device in nRF Mesh app. Like my colleague mentioned in the referred post, it is advertising as an BLE device and not as an unprovisioned node. To able to do that you need the PB-GATT and Proxy feature enabled, and this is not enabled by default in the UART coexist example. The light switch example have these features enabled by default, that is why you can see it in the app.

You need to use our static provisioner in the SDK to provision the device into the Mesh network.

Regarding the logs, what do you mean by "a good __LOG() message"? Log messages can be used to easier debug your application or see what is going on in run time. You can choose yourself where you want to put these log messages. Unfortunately, you won't be able to get the softdevice version/name. You just have to make sure you flash over the correct file.

[Mttrinh]

Thank you for the feedback. A note regarding enabling PB-GATT and proxy feature in Uart coexist example: I haven't done it myself but adding GATT provsioning to the coexistence example is not as straight forward and requires a bit of work. I suggest you have a look at Terje's reply in this post. He have described a way for you to implement GATT provisioning to the coexistence example. This might also be relevant: GATT provisioning and Proxy. Hope this helps.