Dimming Example Client on nRF52840 DK not detected by nRF Mesh Provisioning App.

[Armin]

An nRF5 SDK for Mesh v2.2.0 dimming example client running on a nRF52840 Preview DK is not detected for provisioning by a nRF Mesh smartphone provisioner.

Running the example in debuger delivers the following output on startup:

<t:          0>, main.c,  353, ----- BLE Mesh Light Switch Client Demo -----
<t:          0>, mesh_softdevice_init.c,  117, Initializing SoftDevice...
<t:          0>, mesh_softdevice_init.c,   75, Enabling BLE...
<t:         16>, mesh_softdevice_init.c,  109, sd_ble_enable: app_ram_base should be adjusted to 0x20002DA0
<t:        479>, main.c,  320, Initializing and adding models
<t:       5328>, main.c,  385, Device UUID : 0059CCBB0000000050B5B3E4BD11F856

[awneil]

Armin said:

app_ram_base should be adjusted to 0x20002DA0

So have you done that, then?

[Armin]

No. Please can you assist me how to do that?

However, I doubt if this is the reason for the reported issue because it is just a warning.

I'm wondering if you ever have tested the dimming example client on a nRF52840 Preview DK with nRF Mesh smartphone provisioner. I use all parts of the firmware and app exactly as you provide them without any change and they don't run. That lets me doubt if you ever have tested it.

[Armin]

I guess the same applies for the "EnOcean switch translator client demo", right?

Will this also be considered in the next mesh release?

[Bjørn Kvaale]

Armin said:

I guess the same applies for the "EnOcean switch translator client demo", right?

 I do not fully understand. Does the example not work or do you somehow want to integrate the proxy node into this example?

If you are wondering what could make it into the next mesh release or the next mesh release data, please contact your local Regional Sales Manager. If you are unsure who this is, send me a private message & I can put you in touch.

[Armin]

Yes, the question was, if the proxy fuctionality could also be integrated to the EnOcean switch translator client demo.

[Armin]

I do not understand what is meant in your instruction above with:

Bjørn Kvaale said:

In app_config.h, I added the following lines under

/** Override default sdk_config.h values. */

C:\NordicSemi\SDKs\nRF5_SDK_15.0.0_a53641a\components\libraries\experimental_log\src\nrf_log_internal.h

For now I ignored this instruction and it is possible to build correctly. However when running the example on an nRF52840-DK there is an error:

<t:       5555>, app_error_weak.c,   95, Mesh assert at 0x0003E792 (:0)

[Bjørn Kvaale]

Sorry for the delayed response. I have been travelling for work & have unfortunately not had time to reply to this case. I have reported this issue internally a few weeks ago & the mesh team have implemented a fix for the proxy functionality on the dimming example client. The next mesh SDK should have a fix & should be available soon.

Regarding a fix for the mesh sdk v2.2.0, I have taken a closer look, but the I have had issues with the provisioning via nRF Mesh (i.e. the app hangs once I press the Identify button). I also received the same assert issue you had, but managed to fix that. It seemed to me that it was ok for you to wait for the next mesh sdk, which should have the fix.

I am not certain about the enocean switch translator client with proxy, but I believe it will be possible. I think the proxy feature will be updated, so that only a flag has to be set to enable the proxy functionality. This will hopefully be regardless of which example you use, but please do not quote me on that!