Issue adding FDS module from BLE stack to the Mesh application

RE: Issue adding FDS module from BLE stack to the Mesh application

CodeLoader — Mon, 17 Sep 2018 13:48:59 GMT

Thanks for your answer.

I know that mesh examples use SDK 15.0.0, but I've decided to transfer it to use 15.1.0 because of all of the updates and no visible difficulties apart from changing paths and including files into the projects. So maybe I will also transfer it to newer mesh SDK.

So, now I've reworked my example on top of ble_app_proximity_coexist, which uses Peer Manager, and managed to initialize FDS in Peer Manager. Secure connections work correctly now with BLE functionality, but it's still not clear enough why FDS couldn't start in example where there was no Peer Manager to begin with.

I assumed that the fix provided here is enough to avoid overlapping of the BLE, but maybe it's not depending on the actual project. The difference from the coexist examples is that they use mesh client/server and not provisioner with Flash Manager like my app.

RE: Issue adding FDS module from BLE stack to the Mesh application

Bjørn Kvaale — Mon, 17 Sep 2018 08:53:39 GMT

Hi,

May I ask why you are using sdk v15.1 with mesh sdk v2.0.0? I believe all v2 releases of the mesh sdk require nRF5 SDK v15.0.0 as seen here.That might be a reason you are running into problems. Also, make sure to change the SDK_ROOT in SES like this: go to the Tools tab -> Options -> Building tab -> change SDK_ROOT global macro to point to the path to sdk 15.0.0.

Did you make sure that the flash areas are not overlapping? As the infocenter documentation states, overlapping flash areas might lead to errors. I would also recommend to at least upgrade to mesh sdk v2.0.1, as this is the first sdk with a qualified mesh stack.

If possible, I would recommend taking a look at the new flash manager in the latest mesh sdk v2.2.0. The flash manager has been updated significantly. This & this case may also be helpful.

Kind Regards,

Bjørn