Migrating to Peer Manager

RE: Migrating to Peer Manager

user98446 — Thu, 06 Jan 2022 09:13:10 GMT

SDK15.3，设备默认可以配对多少部手机？如果满了会被覆盖吗？仍然返回配对失败。

RE: Migrating to Peer Manager

user28192 — Fri, 12 Nov 2021 12:41:21 GMT

Hello,
I'm witrh SDK 17.0.2 and softdevice S140, following this guide give error about the nrf_ble_lesc file, altough is included into the project is not referred, wjat are the settings to do inside the sdk_config.h to get it working? Open the file into the SES editor give all the code grayed out as the #if NRF_MODULE_ENABLED(NRF_BLE_LESC) was not satisfied but inside the sdk_config.h file there is no trace about NRF_BLE_LESC key, I've only PM_LESC_ENABLED set to 1.
Scanning all the SDK files for the NRF_BLE_LESC label give no entry so what have to do now?

RE: Migrating to Peer Manager

user92189 — Wed, 26 Aug 2020 18:19:06 GMT

I am not seeing fstorage.h anywhere in my SDK. I am on version 17. I do see:

nrf_fstorage.h

RE: Migrating to Peer Manager

user18046 — Sat, 11 Feb 2017 11:37:31 GMT

Just to add one comment on #sajin comment... I re-burnt the SD132 on nRF52 DK and it started working good. I am not sure why it was not working before.

RE: Migrating to Peer Manager

user18046 — Sat, 11 Feb 2017 11:33:16 GMT

Hello, I am using SDK 11.0 and trying to migrate from DM to PM. While following the tutorial; I managed to compile successfully but when I try to connect my mobile phone with nRF52 DK, I get the following error EVT "PM_EVT_PEER_DATA_UPDATE_FAILED".

Here is the sequence of my main function.

ret_code_t err_code;
bool erase_bonds;

 err_code = NRF_LOG_INIT();
APP_ERROR_CHECK(err_code);

NRF_LOG_PRINTF("D App\r\n");

// Initialize.
//timers_init();
 APP_TIMER_INIT(APP_TIMER_PRESCALER, APP_TIMER_OP_QUEUE_SIZE, NULL);
  buttons_leds_init(&erase_bonds);
	 if (erase_bonds)
{
    NRF_LOG_PRINTF("Bonds erased!\r\n");
}

ble_stack_init();
//device_manager_init(erase_bonds);
peer_manager_init(erase_bonds);
//db_discovery_init();
	
gap_params_init();
conn_params_init();
services_init();
advertising_init();

// Start execution.
application_timers_start();
err_code = ble_advertising_start(BLE_ADV_MODE_FAST);
APP_ERROR_CHECK(err_code);

Please help

RE: Migrating to Peer Manager

user16454 — Tue, 17 Jan 2017 07:24:25 GMT

I'm using sdk12.2 which works perfectly ,but the bonding only takes place at first time when the softdevice is burned. When i forgot the device and bond it again it will not bond and get rejection error from nrf52

RE: Migrating to Peer Manager

user14317 — Mon, 08 Aug 2016 14:28:35 GMT

Does anyone could perform DFU using peer manager?

RE: Migrating to Peer Manager

user14646 — Wed, 13 Jul 2016 11:18:39 GMT

This guide doesn't mention using the FS_REGISTER_CFG as part of the fstorage initialisation. Is this an oversight, or because this initialisation is not required?

The fstorage docs don't go into enough detail to work out what to do with FS_REGISTER_CFG -- particularly what to set the num_pages attribute of the fst_config_t struct. They also don't state whether the FS_REGISTER_CFG call is required at all.

RE: Migrating to Peer Manager

user12904 — Sun, 27 Mar 2016 04:10:31 GMT

Hello, I am trying to migrate from device manager to peer manager using the latest SDK 11. The documentations have not caught up yet. For example, you said to call pm_ble_evt_handler() in ble_evt_dispatch(), but there is no such function. Instead, there is the sm_ble_evt_handler(), or the smd_ble_evt_handler(). sm_ble_evt_handler() is basically a wrapper around smd_ble_evt_handler, but I have not yet found an explanation of the SDK 11 peer manager API.

RE: Migrating to Peer Manager

user5573 — Tue, 19 Jan 2016 02:04:59 GMT

Thanks Einar for this guide.

I tried the nRF52 HRS example of nRF5_SDK_11.0.0-2\examples\ble_peripheral\ble_app_hrs\pca10040\s132, which worked well. Besides the updates you listed above, I also removed pstorage (header and code) from the project. The only update needed is in components\ble\ble_advertising\ble_advertising.c, that we do not need to check pstorage access status in ble_advertising_start() any more.

Memory footprint changes

---- Original code using Periheral Device Manager

Total RO  Size (Code + RO Data)                20228 (  19.75kB)
Total RW  Size (RW Data + ZI Data)             10888 (  10.63kB)
Total ROM Size (Code + RO Data + RW Data)      20256 (  19.78kB)

---- Updated code using Peer Manager

Total RO  Size (Code + RO Data)                30060 (  29.36kB)
Total RW  Size (RW Data + ZI Data)             11568 (  11.30kB)
Total ROM Size (Code + RO Data + RW Data)      30104 (  29.40kB)

RE: Migrating to Peer Manager

user6277 — Wed, 13 Jan 2016 18:13:06 GMT

While it isn't as straightforward

Here to comment that it is actually very straightforward, especially in Mars, to which the most recent GCC tutorials have been updated. Previously you needed to go into the Eclipse Plugins folder, add processor definitions, etc. Now, it's just

Add new software
Import project
Add code parse options
Add makefile targets
Make and flash

So far, it has been very consistent for us, and we spent far less than 5k/seat in engineering resources to set it up. Also, from a cursory glance, it looks like Keil Serial window does not support Telnet. We have found the RTT additions to nrf_log, which integrates with the Eclipse Terminal view, very useful. Strongly recommend re-evaluating the tooling since the landscape has changed in the past few months.

RE: Migrating to Peer Manager

user4532 — Thu, 07 Jan 2016 23:39:32 GMT

Paulus, if you need more than 32kB for your application, there are detailed tutorials on how to use Eclipse with GCC and the nRF SDK which allows you to use the full code space of the nRF family for free. While it isn't as straightforward, it is in my experience a far superior option over Keil. Not only is the IDE itself better, but you don't need to pay thousands of USD for a license.

RE: Migrating to Peer Manager

user9496 — Wed, 30 Dec 2015 19:44:03 GMT

I'm trying to migrate from device_manager, but unfortunatelly it doesn't work, and this is not the only issue for me. The biggest problem is the size of the generated code, after apllying peer manager to template application I saw that code size is about 27 KB. For comparison, size of the template with device_manager takes 15 KB. I'm studying yout product actually and I'm using Keil 5 without license so I can generate only 32KB of code. in my opinion you are going in totally wrong way.