https://devzone.nordicsemi.com/f/nordic-q-a/77714/failure-with-mesh-ble-coexistence-around-flash-managementI am running into an issue around flash management when attempting mesh coexistance with BLE. The call I am failing on is during mesh_init(). Line 298 of flash_manager.c I am using nrf5SDK 17.02 and Mesh SDK 5.00. I have demonstrateden-USTelligent Community 13Thu, 29 Jul 2021 19:44:24 GMThttps://devzone.nordicsemi.com/thread/322539?ContentTypeID=1Thu, 29 Jul 2021 19:44:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4c13dd05-d970-4d75-822f-f42279787572ccasebeer<p>I was able to proceed by what seems like hitting the following define in the makefile:</p> <p><pre class="ui-code" data-mode="c_cpp">CFLAGS += -DCONFIG_APP_IN_CORE</pre></p> <p></p> <p>I had begun trying to check the areas of flash of fds() and peer_managers use of fds(), against the mesh flash management, but then I added this define and things cleared up.</p> <p></p> <p>Not 110% sure on this but it certainly helped.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/321241?ContentTypeID=1Thu, 22 Jul 2021 07:32:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8917a2f0-1635-4e50-8d33-4cb680259de7Simonr<p>Hi</p> <p>Due to the summer vacation period we are currently understaffed, so delayed replies must be expected. I am sorry about any inconvenience this might cause.</p> <p>What might be happening here is that the FDS is using the same area of Flash as the flash manager area that the Mesh stack uses? The flash manager from Mesh is usually located at the end of the flash except the bootloader area, defined by the flash recovery page (flash_area_end_get()). Please make sure that the FDS and Mesh flash manager use different areas of the Flash memory.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>