https://devzone.nordicsemi.com/f/nordic-q-a/94757/ble-fds-write-failHi, I have a problem, When I first initialize Bluetooth and then initialize FDS for writing, it will fail. However, if I first initialize FDS and write data ,it is OK, then initialize Bluetooth, the two peripherals are normal, that is why? what Ien-USTelligent Community 13Mon, 12 Dec 2022 07:01:01 GMThttps://devzone.nordicsemi.com/thread/400053?ContentTypeID=1Mon, 12 Dec 2022 07:01:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e12ee0f9-7813-4615-8e74-3dcc20b774eaEinar Thorsrud<p>Hi,</p> <p>The order of initialization should not matter. The only thing I can think of is if the issue here is using FDS before and after the SoftDevice is enabled. If you use the&nbsp;fstorage implementation which is intended to be used without SoftDevice (nrf_fstorage_nvmc.c), that will not work when the SoftDevice is enabled. And similarly, the backend that is&nbsp;ntended&nbsp;to be sued with a SoftDevice (nrf_fstorage_sd.c) will not work without it.</p> <p>I would double check that you use&nbsp;nrf_fstorage_sd.c, and that you enable the SotDevice before you initialize FDS. This is the approach that is used in all the SDK exmaples that support pairing, for instance. There FDS is enabled as part of enabling the peer manager library, which is done after enabling the SoftDevice.</p> <p>If this does not help, then please let me know a bit more about your application (order of initialization), and elaborate on how things fail (for instance &quot;function X returns error code Y&quot;).</p><div style="clear:both;"></div>