Tool/software: Linux
After several weeks of work we still have issues with the meshpoint mesh network based on the WL1835MOD.
We have solved one issue: we can keep the mesh stable if nothing happens in the mesh.
We reached this point when changing the kernel to: https://git.ti.com/processor-sdk/processor-sdk-linux ) with BRANCH = "processor-sdk-linux-04.03.00".
But from the moment we reboot one device in the mesh, the whole mesh is jammed and the mesh doesn't return to his "complete" state.
We started with 9 meshpoints, we start all the devices. We get a meshpoint mesh with 9 devices that stays stable for 17 hours. Then we reboot one of the devices. A few seconds later the whole mesh is messed up. We still have a few meshpoints in the mesh, but the others are disappeared. Not only the one that has rebooted, but more than the half of the meshpoints has disappeared.
The meshpoints that have disappeared do not come back in the mesh. The one that has rebooted, one time he comes back in the mesh, the other time not.
Is this a normal behaviour of a meshpoint mesh? Or do the other devices have to come back?
We also have issues with the SAE authentication. We followed the description of http://www.ti.com/lit/an/swaa166/swaa166.pdf .The meshpoints authenticate but you cannot reach the devices in the mesh.
We tried the buildscript described in http://processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts but these scripts doesn't work anymore. Some of the repository links used in the scripts are not existing anymore.
Can anyone give me some hints how we can solve these issues?