The error message shows up after building the mesh demo code to thingy 52

[William]

Hi

I following the steps listed in the document Thingy Mesh Demo v0.1

https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo

When i perform the step 5  "Open the workspace under "Thingy_node\pca20020_s132\ses",
compile and download the firmware into multiple Thingy devices which will play the role as "Nodes"."

In Segger Embedded Studio, select Target on toolbar > Download Thingy node

After compiling, the error message shows up when downloading to Thingy as below:

How to solve this problem?

Thanks!

[Jui-Chou (Rick) Chung]

Hello William,

Would you please help me to check:

1. Have you executed the "setup_sdk.bat" which inside the "Nordic-Thingy-52-FW" folder? Have you met any error messages?

2. Is there a folder "sdk_components" inside the "Nordic-Thingy-52-FW" folder?

3. Under the path "Nordic-Thingy52-FW\sdk_components\softdevice\s132\hex", is there the softdevice file "s132_nrf52_4.0.2_softdevice.hex" inside ?

[William]

1. I rerun all step from 1 to 5(delete old, create new), After executed the “setup_sdk.bat”, The log capture as attach file. (seems to no error?)

Fullscreen bat.txt Download

�w�إ� sdk_components ���s�� <<===>> external\sdk13\components
�w�إ� external\nano-pb ���s�� <<===>> external\sdk13\external\nano-pb
�w�إ� external\segger_rtt ���s�� <<===>> external\sdk13\external\segger_rtt
"micro-ecc not found! Let's pull it from HEAD."
Cloning into 'external\sdk13\external\micro-ecc\micro-ecc'...
remote: Counting objects: 1086, done.
remote: Total 1086 (delta 0), reused 0 (delta 0), pack-reused 1086
Receiving objects: 100% (1086/1086), 647.95 KiB | 672.00 KiB/s, done.
Resolving deltas: 100% (637/637), done.
mkdir _build
Compiling file: uECC.c
Creating library: ../../nrf52_armgcc/armgcc/micro_ecc_lib_nrf52.a
C:\Program Files (x86)\GNU Tools ARM Embedded\7 2017-q4-major/bin/arm-none-eabi-
ar: creating ../../nrf52_armgcc/armgcc/micro_ecc_lib_nrf52.a
Done
mkdir _build
Compiling file: uECC.c
Creating library: ../../nrf52_keil/armgcc/micro_ecc_lib_nrf52.lib
C:\Program Files (x86)\GNU Tools ARM Embedded\7 2017-q4-major/bin/arm-none-eabi-
ar: creating ../../nrf52_keil/armgcc/micro_ecc_lib_nrf52.lib
Done
����N���~�� . . .

2. The folder “sdk_components” is available in the “Nordic-Thingy-52-FW” folder

3. There is no file “”, in the foldar Nordic-Thingy52-FW\sdk_components\softdevice\s132\hex, Where can i find this file?

[Jui-Chou (Rick) Chung]

Hello William,

Great that now the firmware can be compiled

Regarding with your questions now:

1. No, it is not correct. The bridge should not change it color. Would you please use nrfjprog to erase the Thingy and reprogram it? If it still doesn't help, please attach the J-Link and open the RTT viewer to see if there's any error log? Or please program the precompiled hex to see if the bridge works or not 
https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo/tree/master/precompiled_hex

2. The AUTO_PROV is in here
https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo/blob/master/Thingy_bridge/pca20020_s132/ses/sdk_mod/provisioner.c#L60

3. For now the nRFMesh is only for internal test and is not available to the public at current stage.

I would like to suggest you use nRFConnect on Android with the newest macro for demo
https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo/tree/master/nRFConnect_macros/nRF%20Connect%204.18%20or%20newer

[William]

Thanks!

After use the nrfjprog to erase the Thingy and reprogram, The problem is solved!
The Thingy bridge and Thingy node can auto connection, And the bridge can control light via button on the Thingy.

After use the RFConnect on the Android phone and loaded the macro from link,

My procedure is "menu => Configure GATT server => press "Sample configuration" on the top bar => press the "downlaod icon" => load the [Thongy Mesh Demo.xml].

The error message "attribute 'lang' does not have a match in class no.nordicsemi.android.mcp.server.domain.ServerConfiguration at line 8" shows up.

How to solve this problem?

[Jui-Chou (Rick) Chung]

Hello William,

Glad to hear that the demo works

I would like to suggest you check the following link for import the "Thingy Mesh Demo.xml"

https://www.youtube.com/watch?v=rWOws3uhN6o

This video was prepared for old macros, but we can use the same way to import the "Thingy Mesh Demo.xml".

[William]

Thanks!

I load the Thingy Mesh Demo.xml to the nRF Connect and The mesh demo macros(thingy mesh demo) is work properly!

I tried send the bleow command to the thingy bridge via Nordic UART Service/ RX Characteristic, But the specified node is not work after send command.
Command: 0x0002030100FF00

Operation procedure:

1. Connect to the Thingy Bridge node use the nRF Connect,
2. Select the Client page
3. Send command "0x0002030100FF00" to the Nordic UART Service/ RX Characteristic
4. The specified node is not work after send command.

My Operation procedure is right or not?
How to solve this problem?

[Jui-Chou (Rick) Chung]

Hello William,

Glad to hear that the Thingy mesh demo macro works

Would it possible for me to know how many nodes do you have in your mesh network now?

[William]

I have 4 Nordic thingy:52
1 for mesh bridge
3 for node (node 0~2)
Use the demo morcos( Mesh Demo.xml ) can work properly,
But i send the code directly via Nordic UART Service/ RX Characteristic
The specified node is not work...

Thanks

[Jui-Chou (Rick) Chung]

Hello William,

Would you please help me to check if you already"unchecked" the "Parse known characteristics" in the nRFconnect on Android ? Please leave that item checkbox in blank :)