Hello,

i successfully compiled a working version of the WF111 driver (the beta version provided by SL) on a ARM system with linux kernel 5. The armbian configuration of the network-manager is lacking, i had to kill the wpa supplicant launched by the the network-manager and use the old network/interfaces configuration in order to have the wlan0 up.

Leonardo

Hello,

now i'm able to compile the wf111 driver (beta) on the newer linux kernel, but it's not working. i followed all steps of the troubleshooting PDF with success, the module is correctly loaded, the "iwlist scan" does work. But i cannot join an access point. the interface is present as shown by the "iwconfig" command, but wpa_supplicant doesn't work. I think it may be a linux configuration problem. Should i use a specified network manager? The "ip a" command show the wlan0 interface with mac address 00:00:00:00:00:00, is it right? I tried the mac.txt without success, the mac address is zeroes. now i'm trying to re-compile the wpa_supplicant with the CONFIG_NO_ROAMING define. any hints?

Leonardo

Hello,

i have the some problem, i cannot compile the WF111 driver on a custom linux with kernel version 4.19.75. Is there any news about it?

Best Regards

Hello,

i found another "bug" in the example. The server (but also client) code does not support the EMBER_JOINED_NETWORK_NO_PARENT state, asserting an error in that case, because the server should never be in that state. BUT the server goes in that state, for sure when there are more routers in the same network. After some power-off and on of routers, may it loose its parent? Also routers have parents. That state must be managed with a emberAttachToNetwork() call.

Leonardo

Hello,

same problem with the Stack V2.10.2 and MGM12P22 GA and GE modules with 10dbm. The range is very poor compared to the previous version we used, the V2.8.1. We had to go back with the stack version.

Leonardo

thank you! i just read it, a big waste of time for me! i hope the switch to OpenThread will be easy, if i shall spend the time i spent on SL thread for learning all undocumented functions also on OT i'll drop SL products and i'll definitely switch to LORA. Mesh is a great thing, but not in this way. Programming a LORA module costs only 4 hours of code writing and it works very good.

I gave a look to OpenThread last year and it was not ready for EFR32. I found only a minimal porting for EFR32 on a github, but it was at an early stage. Now there is the officiale page about EFR32, the only good thing is that doing something worse than the ember stack is difficult!

Leonardo

Hello,

i am a EFR32 customer and i would like to develop my own border router. I do not use the Raspberry Pi, but another SOM with features i need for my own product. Since the Border Router example is too dependent from the Raspberry Pi Linux distribution (dependencies, configuration file changes, path) i decided to do a porting or to write a new software. But there is a big problem, the NCP-Host protocol is NOT documented. How can i develop a software managing a protocol without having the documentation of that protocol?

Leonardo

The Thread application architecture is simple, check the server/client examples or the Connection Manager sources codes. But it doesn't works, a lot of functions are not described, no solution for problems. Is anyone using Thread? Does the ember stack really works in real products and real installation?

Leonardo

read the source code and realize how it works, the documentation is very poor. i'm astonished how a big company investing a lot of resources on a hardware could forget the software & developer support.

Leonardo

Hello,

it's not a compiler problem. the stack is totally unstable. Its behaviour is unpredictable.

my setup:

Leader: MGM12P22F1024GE - Tried GCC v7.2.1 and IAR 8.32

Router (client): MGM12P22F1024GA - Tried GCC v7.2.1 and IAR 8.32

but i also tried the client example with the SLWSTK6000A demo boards.

Plugins and stack configuration is the same of the server/client example. I only customized the hwconf and the used serials.

Before flashing any modules i do a full flash erase.

some results:

- i read this from the Thread 2.10 API reference web page from the Silicon Labs site: " To forget the network and return to a status of EMBER_NO_NETWORK, please read cautions for emberResetNetworkState() " (written on the few rows of emberJoinNetwork() description). Furthermore i read these few and enigmatic words in the emberResetNetwork() description: " This function erases the network state stored in nonvolatile memory after which the network status will be EMBER_NO_NETWORK. This function should not be called to rejoin a former network; use emberResumeNetwork() instead. There may be difficulties joining a former network after resetting the network state, due to security considerations."

What does it mean? security conderations??? Meaning what? Basically what shall i do to leave a network and join another one? Or to leave, join another one and then re-join the first one? A detailed description of the Thread STACK functionality would be appreciated.

- i tried changing the network ID both on the leader (the router calling emberFormNetwork()) and on the client (emberJoinNetwork()), same behaviour, the client join fails with reason 0x02, then after some re-tries it joined.

- i tried powering off and on the client router, it resumed correctly the network, then i tried powering off and on the leader. The client router only after a minute goes to the network state EMBER_JOINED_NETWORK_ATTACHING and the re-attach to the leader correctly. It seems ok.

- i re-tried switching off and on the client router, it resumes the network, but it cannot receiver the leader advertisement. They seem to be in the same network (same name, channel, panID) but the advertisement of the leader is not received. why?? i tried also to reset the module and resume again the network without any result. if i reset the network i will loose the possibility to join that network again. waiting some minutes the client has begun to receive the leader advertisement again. Why? Is it a known delay or is it a random behaviour?

- i flashed another client router, the join fails with code 0x02. I tried to join as an end device, same result. it joined the network only after some minutes of retries (1 retries every 5 seconds). in the meantime the client router lost the attachment once, why? All devices are in the range of 3 meters.

In this forum there are very few posts about Thread, anyone using it without any problems? I think there is a major bug somewhere, maybe in the stack configuration created by the App Builder for the MGM12P.

Leonardo