NRF52840 dongle light-switch example need help

[Di-sheng]

Dear Nordic Team!

I am verifying my tools chain for nrf52840 Mesh  project development by mesh light-switch example. I have 4 PCA10056 and make them to 1 provisioner, 1 client and 2 serves and they works. I need more serve to text. I want make my other 4 pca10059 to serve. As you know, the example is for PCA10056. Is there some one have the serve project code for PCA10059, So that I can make a mesh system with more node and test my tools chain can program pca10059 correct.

Thanks,

 Dison 

[Con]

Tried 3.1.0 as per Bjorns instructions.
I get same expected identifier error. tried also defining in main orin simple_hal.h and calling output power function during initialisation asap with no luck:
Compiles, i flash it along with softdevice but i cannot find it as unprovisioned. I have never provisioned the dongle since it's the first time i attempt this so i guess it just crashes.
All leds are on on the dongle after flashing (except LED2_G maybe?) so perhaps it crashes indeed.
The sniffer can't locate any mesh packets either so i am not sure what goes wrong.
Tried 4.0.0, exact same output.
Also i have tried the other tutorial according to which just changing from PCA10056 to PCA10059 should be adequate.
Only it's not, and i end with the LED start/stop situation and again we end up in the same scenarios.
Bjorns folder didn't include anything precompiled either in the build folder. If i flash it on PCA10056 i can detect everything with no problem though.

Could you please link to whole project folders that actually work without us modifying anything in any SDK version?

[Amanda Hsieh]

Hi Con,

Without the log of segger, I do not what caused the expected identifier error in your environment. However, the most problem that is caused by the incorrect version. Please be aware that the nRF5 SDK for Mesh 3.1.0 requires the nRF5 SDK 15.2.0 to compile. See Installing the toolchain for more information. 

Following everything from the nRF52840 Dongle Tutorial should generally lead to a working application, so it is hard to tell what may be missing.

The best way to figure out what happens is to connect the Dongle to a programmer, either using a 10 pin Tag Connect cable or soldering wires directly on the Dongle. Not having a debugger connected severely limits the debugging capabilities. From your description, it sounds like you get an assert and end up in the fault handler. From a debug session you should easily get a file and line number.

If you have further questions, Please create a new support case for your own issue. 

-Amanda H.