nRF Mesh scanner cannot see DKs

[tmwinjy]

Hello,

I am attempting to run the Nordic-Thingy52-mesh-demo using nRF Mesh v 1.1.0 for Android but the nRF Mesh app's scanner cannot see my DKs. I can see the mesh from nRF connect and have successfully run some commands by sending byte arrays. Does anyone know what could be the problem with my nRF Mesh Scanner?

 Background:

-Mesh is composed of 2 nRF52832 DKs (1 bridge and 1 node)

-using Nordic Thingy:52 SDK v2.1.0

-using Nordic nRF5 SDK for Mesh v1.0.1

Thank you in advance,

Takunda Mwinjilo

[Edvin]

Hello,

This is because the thingy nodes doesn't have the proxy service. I.e. they only speak Mesh, and not Bluetooth Low Energy.

This is a very old demo.

I suggest you rather start with this thingy demo if you need to use Thingys for your demo:

https://github.com/NordicPlayground/thingy52-mesh-provisioning-demo

This demo has the proxy BLE service, so you can use the nRF Mesh app for provisioning. There is also a video showing how to provision this demo in the readme.me file.

Best regards,

Edvin

[philbrock]

Hi Edvin,

I am following the instructions above for the newer thingy52-mesh-provisioning-demo.

I am using nRF Connect v2.6.2 on Windows 10 with an nRF52840 Dongle and a bunch of Thingys.

I have nRF5 SDK version 15.3.0 and nRF5 SDK for Mesh version 3.1.0 installed.

Using the prebuilt .hex files in Mesh SDK, I used the following nrfutil command to construct a DFU to flash a Thingy with a mesh based bootloader and soft device:

nrfutil pkg generate --hw-version 52 --bootloader mesh_bootloader_gccarmemb_nrf52832_xxAA.hex --bootloader-version 2 --softdevice s132_nrf52_6.1.0_softdevice.hex --sd-boot-validation NO_VALIDATION pjb_bl_sd.zip --sd-req 0xAF

I put the target Thingy in DFU mode, and connected to it within nRF Connect, and tried to perform an upgrade.

I get:

DFU failed with error: When writing 'EXECUTE' command to Control Point Characteristic of DFU Target: Operation code 4 (EXECUTE) failed on DFU Target. Result code 11 (EXTENDED_ERROR) Extended error code 3 (UNKNOWN_COMMAND).

What am I doing wrong?

Best Regards,

Phil