I am using nRF52840 for bluetooth mesh technology for industrial light control.Can anyone help me for my project, how can it be done,I have the light switch demo file, but how to use it.
I am using nRF52840 for bluetooth mesh technology for industrial light control.Can anyone help me for my project, how can it be done,I have the light switch demo file, but how to use it.
Hi,
Please have a look at the Light switch demo documentation on Infocenter. For running the demo, follow the instructions under "Running the demo" on that page. There you also find links to the Bluetooth Mesh Getting started sections for an introduction to the concepts involved in Bluetooth Mesh and how they relate to our nRF5 SDK for Mesh.
Regards,
Terje
to build the network is it necessary to install mesh toolchain
i didn't understand the toolchain requirement.
i'm using keil.
Hi,
nRF5 SDK for Mesh requires either CMake or SEGGER Embedded Studio (SES), but you can still use ARMCC/Keil for compiling, linking, etc. Just note that we do not have project files for the Keil IDE, so for IDE your choices are to use SES or to use any text editor together with CMake.
You may also port the project yourself to your favourite IDE, although I do not recommend doing so. Please note that our recommended IDE for all SDKs is SES, and it is free to use for nRF development.
Regards,
Terje
Hi
For light switch demo code i flash client code on 1 board and server code on other boards,
but had problem in execution, all 4 led on all board turn ON.
Demo is not implemented as per the step given.
What would be the problem.
Hi,
What IDE or tool did you use for programming the boards?
If you use Segger Embedded Studio then both application and SoftDevice is programmed onto the board, but with other IDEs or programmers you may have to program the SoftDevice separately. You find the SoftDevice as <nRF5 SDK for Mesh folder>/external/softdevice/s132_3.1.0/s132_nrf52_3.1.0_softdevice.hex.
If the above does not solve the issue, can you do a debug session and see if the code ends up in an assert handler, and/or check the log output from the boards?
Regards,
Terje
Hi. I use Segger for the programming. I managed to reproduce your situation. I accidentally hit the "Continue Executing"/Play/Green button while debugging and i got the 4 LEDS on. Correct procedure is :
1. Build solution.
2. Target the nRF you want to flash the firmware to.
3. Debug.
4. Stop debug by RED button not Green.
Then the example runs perfectly. I know it's late and you probably have the solution by now, but just in case someone hits the same bump.
Hi. I use Segger for the programming. I managed to reproduce your situation. I accidentally hit the "Continue Executing"/Play/Green button while debugging and i got the 4 LEDS on. Correct procedure is :
1. Build solution.
2. Target the nRF you want to flash the firmware to.
3. Debug.
4. Stop debug by RED button not Green.
Then the example runs perfectly. I know it's late and you probably have the solution by now, but just in case someone hits the same bump.
Hi. I use Segger for the programming. I managed to reproduce your situation. I accidentally hit the "Continue Executing"/Play/Green button while debugging and i got the 4 LEDS on. Correct procedure is :
1. Build solution.
2. Target the nRF you want to flash the firmware to.
3. Debug.
4. Stop debug by RED button not Green.
Then the example runs perfectly. I know it's late and you probably have the solution by now, but just in case someone hits the same bump.
