Compiling Peer Manager and Flash Data Storage for a Linux desktop PC application

[InformatikWick]

I am compiling and running an application (my Simulator) on my Linux desktop PC. I am using nRF5 SDK v15.2.0.

This application uses the Serialization Interface and communicates with a nordic development board as described in:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v13.0.0%2Flib_serialization.html

Everythink works fine. Using my nRF-Connect App on my Smartphone, I can see my BLE device advertising and I can connect to it.

Now I want add bonding to my device. Therefore I need the Peer Manager:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Flib_fds.html

As I understod, I need to compile the Peer Manager for my Linux application. The Peer Manager itself requires the Flash Data Storage.

Trying to compile Flash Data Storage also, I am getting some comilation errors because the Flash Data Storage includes/uses the Atomic FIFO.

Those Atomic FIFO can not be compiled for my Linux application, because it contains some ARM asembler code.

I suppose those assembler code is required to be able for multi threading. Just for info, on I my application I have only a single thread.

Is there any Flash Data Storage sorces available, that I can compile for my Linux application?

Mybe there is another solution for my issue?

[Simon]

During the easter, a large part of the support team are on vacation, and you may not get an answer at first. The 23 of april, most of the staff will be back, and you can expect an answer that week.

Best regards,

Simon

[Simon]

In the Peer Manager the flash storage is used to persistently store the bonding information and the GATT data. You can not use the flash storage on the PC and have to implement a custom solution in order to store the encryption keys. See this thread.

Please ask if anything is unclear.

Best regards,

Simon

[Chencheng]

Hi Simon, if not referring to connectivity pc-ble-driver, so to say normal hex on an nRF chip, what is the memory area for Peer Manager to store encryption key? What are the parameters/variables for configure that?

I know each nRF devices varies with LD file when setting memory pages, but I am not sure how it is working with Peer Manager?

BR/Chencheng

[awneil]

I don't think that question has anything to do with this thread?

Start a new thread for a new / unrelated question ...