Adding peer manager to multiperipheral example and getting FATAL ERROR

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Pawel Niedbala — Thu, 07 Jun 2018 08:47:46 GMT

Well now I am seeing multi_peer and it pairs but why does it matter that now I have:

*used the SoftDevice of the same name and same version but from different folder

*flashed the program from nRFgo studio programming tab instead of drag and dropping to JLINK folder?

anyway thanks Martin

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Martin Lesund — Thu, 07 Jun 2018 08:26:04 GMT

Hi Pawel,

The files you find in the "hex" folder is already precompiled .hex files from the unmodified SDK example (in this case the 'ble_app_multiperipheral' application). So when you are flashing one of the .hex files found there, you are just really running the unmodified "ble_app_multiperipheral" example. If you look into each example in the SDK you can see this folder.

To test the modified application Try this:

1. Erase whats on the chip.

2. Flash the SD [nRF5_SDK_15.0.0_a53641a\nRF5_SDK_15.0.0_a53641a\components\softdevice\s132\hex]

3. Flash the Application [nRF5_SDK_15.0.0_CUSTOM\examples\ble_peripheral\experimental\ble_app_multiperipheral - Copy\pca10040\s132\arm5_no_packs\_build]

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Pawel Niedbala — Thu, 07 Jun 2018 07:43:11 GMT

erase:

SD:

hex:

When I flash this (it WAS inside the .zip you have provided, Martin):

it advertises as nordic_blinky, shows up in terminal and behaves just like I described 2 hours ago (no bonding)

When I flash this hex ble_app_multiperipheral - Copy\pca10040\s132\arm5_no_packs\_build (after erasing and flashing SoftDevice):

it doesn't advertise (even the LED for advertising is off), doesn't show in nrfConnect app, no output to puTTY.

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Martin Lesund — Thu, 07 Jun 2018 07:08:54 GMT

Hi Pawel,

I am glad that you got it to work.

The reason there is no 'ses' folder is because I used Keil and delete the other folders to make the .zip file smaller. (You could use main.c/sdk_config.h as reference if you need to)

- You shouldn't worry about that.

Because it sounds that you have flashed another .hex file than what is in the .zip file. (it should show up as "multi_peer" in the app)

If you want to try it, Remember to erase whats on the chip ("nrfjprog -e") before you try to flash the .hex file in [\ble_app_multiperipheral - Copy\pca10040\s132\arm5_no_packs\_build] folder + the softdevice.

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Pawel Niedbala — Thu, 07 Jun 2018 05:48:55 GMT

Hi Martin,

Yes, in the last days I have added peer manager and it seems working. I used the method I described. I just don't know where I made a mistake or something. Also I have implemented passkey entry.

Thank you for your file, now I can use it in future for reference but there is something strange about it. There is no 'ses' folder which I can check and compile so I just moved hex file directly to JLINK, it flashes and "multiperipheral example started" shows in terminal, chip shows in the mobile app as nordic_blinky, I am able to connect but unable to pair. I press bond but app shows "pairing rejected...". Should I worry about this?

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Martin Lesund — Wed, 06 Jun 2018 14:27:33 GMT

Hi Pawel,

Have you had any progress on this?

I have added MultiPeripheral example with peer manager added which seem to work.devzone.nordicsemi.com/.../ble_5F00_app_5F00_multiperipheral-_2D00_-Copy.zip

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Pawel Niedbala — Fri, 25 May 2018 08:43:34 GMT

Hi Martin

Firstly thanks for the response, I was waiting for it. I have just opened fresh unmodified multiperipheral example to work with.

Secondly the "old blog" I was relying mostly comes from the documentation you have linked. There is a bug in this documentation, I believe: the function is peer_manager_event_handler but peer_manager_init calls pm_evt_handler. But I have added peer_manager_init, pm_evt_handler function definitions, security parameters and a call from main function. I have omitted "Storing data" and "Using whitelist" paragraphs.

Moreover setting PEER_MANAGER_ENABLED 1 is not enough, I do also have to set NRF_FSTORAGE_ENABLED 1 and FDS_ENABLED 1 to get rid of compiling errors.

I have also added many .c files which I listed in the 1st post.

Now my project compiles and flashed. I am able to connect masters to it but when I try to pair/bond I get the same Fatal Error and the identical CallStack when I debug this.

Maybe if there is no guide without errors and uncertainties you could provide a MultiPeripheral example with already implemented Peer Manager?

Below I am pasting all the changes I have done to the original project:

main.c

sdk_config.h

ble_app_multiperipheral_pca10040_s132.emProject (with listed all the files and libraries)

I really need help on this, whitout it I cannot procced.

thanks in advance

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Martin Lesund — Thu, 24 May 2018 14:12:47 GMT

Hi Pawel,

I am sorry, but it seems that you have followed some old blogs about older SDK versions, where SES support wasn't integrated and where you didn't have peer manager.

It will just cause more trouble and work continuing down that path, so instead I would recommend you to use the (unmodified) BLE MultiPeripheral example as a base then add the Peer Manager as described in the documentation.

Example found in [RF5_SDK_15\examples\ble_peripheral\experimental\ble_app_multiperipheral\pca10040\s132\ses]

-> Remember to enable Peer Manager in sdk_config.h

// <e> PEER_MANAGER_ENABLED - peer_manager - Peer Manager //========================================================== #ifndef PEER_MANAGER_ENABLED #define PEER_MANAGER_ENABLED 1 #endif

-> Then follow the descriptions in the documentation

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Pawel Niedbala — Thu, 24 May 2018 10:31:36 GMT

Update number 2 on this error:

I have added NRF_LOG_INFO("event nr: %x", p_ble_evt->header.evt_id); and commented below case

/* case BLE_GAP_EVT_SEC_PARAMS_REQUEST: // Pairing not supported err_code = sd_ble_gap_sec_params_reply(p_ble_evt->evt.gap_evt.conn_handle, BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP, NULL, NULL); APP_ERROR_CHECK(err_code); break; */

inside static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context) in main.c. I am able to connect AND bond. Here is the PuTTY log:

<info> app: Erase bonds! <info> app: Multiperipheral example started. <info> app: event nr: 10 <info> app: Connection with link 0x0 established. <info> app: event nr: 12 <info> app: event nr: 12 <info> app: event nr: 12 <info> app: event nr: 12 <info> app: event nr: 13 <info> app: event nr: 12 <info> app: event nr: 1A <info> app: Connection secured: role: 1, conn_handle: 0x0, procedure: 1. <info> app: event nr: 19 <info> app: event nr: 12 <info> app: event nr: 12

and for reconnection:

<info> app: event nr: 11 <info> app: Connection 0x0 has been disconnected. Reason: 0x13 <info> app: Connected to a previously bonded device. <info> app: event nr: 10 <info> app: Connection with link 0x1 established. <info> app: event nr: 14 <info> app: Connection secured: role: 1, conn_handle: 0x1, procedure: 0. <info> app: event nr: 1A

I don't like how I got no control over this. I mean the case inside the switch isn't supposed to be just commented out, right?

RE: Adding peer manager to multiperipheral example and getting FATAL ERROR

Pawel Niedbala — Thu, 24 May 2018 09:20:30 GMT

Update on this error:

I have set breakpoint inside app_error_handler_bare function in app_error.c file and below there is call stack with error of invalid state.