[FDS] PeerManager error -> try to find record which recently has been invalidated

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Thu, 05 Sep 2019 13:32:41 GMT

That is good news. You should use the compilers that are listed in the SDK release notes.

GCC: GCC ARM Embedded 4.9 2015q3

Can you test with an unmodified SDK and armgcc version 4.9 2015q3?

As I mentioned in an earlier reply, I the LESC example, updated to the same application via DFU (a newer application version), and I am not able to reproduce this issue. Maybe you can give some instructions on how to reproduce your issue with an unmodified SDK?

Best regards,

Edvin

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

patlas — Thu, 05 Sep 2019 11:40:01 GMT

I have finally solve problem - I've been using newer gcc compiler (version 5.4.3). When I switch to 4.9.3 sdk example builds starts working like a charm. Assuming it as a reason of my examples problem this mean that somewere in SDK/SD code there is missing ALIGNMENT or another issue - try to reproduce it.

Since now I am switching to my base topic question with FDS hazardous.

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Thu, 05 Sep 2019 09:26:14 GMT

Ok. I agree, it doesn't work, but I don't know why. Looks like your bootloader crashes somewhere.

This set works (not that it helps much)

devzone.nordicsemi.com/.../BL.hex devzone.nordicsemi.com/.../lesc_5F00_1.zip devzone.nordicsemi.com/.../s132_5F00_nrf52_5F00_4.0.2_5F00_softdevice.hex devzone.nordicsemi.com/.../lesc_5F00_2.zip

Nothing fancy done to the bootloader (except changing the advertising name from "DfuTarg" to "Dfu_Targ" to separate it from other DFU devices in the office).

Have you done any changes to the bootloader project?

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

patlas — Thu, 05 Sep 2019 08:43:16 GMT

SDK: nRF5_SDK_13.0.0_04a0bfd.zip
SoftDevice: from SDK
chip: nRF52832 (DK10040)
nrfutil: 5.2.0 (try 3.2 and 3.4)

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Thu, 05 Sep 2019 08:32:37 GMT

What SDK version do you use? What chip do you use? nRF52832? nRF52840? What Softdevice do you use?

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

patlas — Wed, 04 Sep 2019 13:53:19 GMT

In attachment you will see two logs file (dfu_log_file.log and logs.txt - more precise with error capture), and I attache bootloader hex file and zipped and signed lesc application to perform otau.

devzone.nordicsemi.com/.../bl.hex

devzone.nordicsemi.com/.../lesc_5F00_bug_5F00_test_5F00_1.zip

devzone.nordicsemi.com/.../dfu_5F00_log_5F00_file.log

devzone.nordicsemi.com/.../logs.log

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Wed, 04 Sep 2019 11:18:33 GMT

Ok. Can you try to use nrfutil with the following commands? dfu_image.zip should be the path to your DFU image, and COMX should be the com port that the connectivity DK (not the DK containing the bootloader) is using, and __name__ should be the advertising name of your device. In an unmodified Bootloader project, that would be "DfuTarg".

PS: run "nrfjprog -e" on the DK that is working as your connectivity DK (the same DK that you used with nRF Connect for Desktop).

nrfutil -v -v -o dfu_log_file.log dfu ble -pkg dfu_image.zip -ic NRF52 -p COMX -n "__name__" -f

Then attach the log file: dfu_log_file.log, that is generated in the same folder as you run your cmd window from.

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

patlas — Wed, 04 Sep 2019 10:37:09 GMT

I have perform all steps mention in "how to perform DFU" and thats why I am asking that question.
Yes I have generated my custom key, add it to project and sing application.zip with my private key as mention in "how to...".

The only logs I receive comes from nrfconnect application which I show you in previous message.

Can you please provide me full flow you are doing to prepare bootloader and lesc app (including full path from sdk13 and how you are generating keys and where you are putting them)? Maby I miss something which it is crutial to have same start as You to try figure out issue I have mention in beginning post.

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Wed, 04 Sep 2019 10:27:22 GMT

What does it say in the log where you try to perform the DFU from?

Without knowing more, I can't help much other than pointing to the guide on how to perform DFU.

The precompiled hex file in examples\dfu\bootloader_secure_ble\hex probably contains the softdevice as well. Also, remember that you need to use a DFU image signed with the same key as you use in your bootloader, so they probably doesn't match. Read through the guide on how to generate your own set of keys.

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

patlas — Wed, 04 Sep 2019 08:54:55 GMT

I have tried to reproduce my problem with bare sdk13 but I cannot perform OTAU. I have called everything like you share in *.bat file. Unfortunately each time (on PC nrfconnect app) I am receiving:

Scan started
10:32:22.022
Disconnected from device E9:AD:02:C5:09:48, reason: BLE_HCI_CONNECTION_TIMEOUT
10:32:22.487
Scan stopped
10:32:23.327
Connecting to device
10:32:23.388
Connected to device E9:AD:02:C5:09:48
10:32:23.645
Attribute value read, handle: 0x03, value (0x): 44-66-75-54-61-72-67
10:32:29.793
Disconnected from device E9:AD:02:C5:09:48, reason: undefined
10:32:29.796
Performing DFU with file: lesc_test_1.zip
10:32:36.216
Aborting DFU.

After flashing bl + sd to DK (pca10040) both LED1 and LED3 lit but after connection nothing has changed. Compared to *.hex file provided precompiled (examples/dfu/bootloader_secure_ble/hex) after connection LED1 turns off and LED2 start lit.What am I doing wrong?

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Tue, 03 Sep 2019 14:01:48 GMT

I did now, and it works here (again, one phone and one DK using nRF Connect).

I flashed the bootloader on one DK, updated to the LESC application via DFU, bonded with 1: my phone, and 2: the DK that I used with nRF Connect to update the firmware.

Then updated the firmware again with DFU, to the same application with a higher application version. Then checked with both devices. They were still bonded.

The reason I asked you to test the experimental_ble_app_buttonless_dfu example is that it doesn't use LESC. I wanted to check if the issue was related to the actual bonding procedure or FDS. Not all phones support LESC. None of the phones that you listed are particularly new. Are you sure they both support LESC?

Can you please try either with a new unzip of the SDK that is not modified, and if it still doesn't work, can you test with the ble_app_buttonless example? Remember to change the line that I mentioned in the previous reply to trigger bonding.

In case you find it helpful, here is the script that I used to generate the images and flash the bootloader and the first DFU to get the LESC or buttonless application up and running with a bootloader. You need to adapt it to use your serial number (instead of 123456789) and the correct private.key and COM port for nrfutil.

:: compile the bootloader
make -j9

:: flash softdevice and bootloader 
nrfjprog -e --snr 123456789
nrfjprog --program ..\..\..\..\..\components\softdevice\s132\hex\s132_nrf52_4.0.2_softdevice.hex --verify --snr 123456789
nrfjprog --program _build\nrf52832_xxaa_s132.hex --verify --snr 123456789
nrfjprog --reset --snr 123456789

:: compile the buttonless example
make -j9 -C ..\..\..\..\ble_peripheral\experimental_ble_app_buttonless_dfu\pca10040\s132\armgcc
del files\buttonless_bonding.hex
copy ..\..\..\..\ble_peripheral\experimental_ble_app_buttonless_dfu\pca10040\s132\armgcc\_build\nrf52832_xxaa.hex files
ren files\nrf52832_xxaa.hex buttonless_bonding.hex

:: compile the LESC example
make -j9 -C ..\..\..\..\ble_central_and_peripheral\experimental\ble_app_multirole_lesc\pca10040\s132\armgcc
del files\lesc.hex
copy ..\..\..\..\ble_central_and_peripheral\experimental\ble_app_multirole_lesc\pca10040\s132\armgcc\_build\nrf52832_xxaa.hex files
ren files\nrf52832_xxaa.hex lesc.hex

:: generate buttonless images with 3 different application-versions
nrfutil pkg generate --application files\buttonless_bonding.hex --application-version 1 --hw-version 52 --sd-req 0x98 --key-file files\private.key files\buttonless_1.zip
nrfutil pkg generate --application files\buttonless_bonding.hex --application-version 2 --hw-version 52 --sd-req 0x98 --key-file files\private.key files\buttonless_2.zip
nrfutil pkg generate --application files\buttonless_bonding.hex --application-version 3 --hw-version 52 --sd-req 0x98 --key-file files\private.key files\buttonless_3.zip

:: generate lesc images with 3 different application-versions
nrfutil pkg generate --application files\lesc.hex --application-version 1 --hw-version 52 --sd-req 0x98 --key-file files\private.key files\lesc_1.zip
nrfutil pkg generate --application files\lesc.hex --application-version 2 --hw-version 52 --sd-req 0x98 --key-file files\private.key files\lesc_2.zip
nrfutil pkg generate --application files\lesc.hex --application-version 3 --hw-version 52 --sd-req 0x98 --key-file files\private.key files\lesc_3.zip

:: Perform the DFU to first application.
::nrfutil dfu ble -pkg files\buttonless_1.zip -ic NRF52 -p COM9 -n "Dfu_Targ" -f
nrfutil dfu ble -pkg files\lesc_1.zip -ic NRF52 -p COM9 -n "Dfu_Targ" -f

EDIT: This .bat script is placed in the armgcc folder of the bootloader project. The private.key is located in a folder called "files" inside this folder.

Best regards,

Edvin

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

patlas — Tue, 03 Sep 2019 13:14:23 GMT

You are right but it is not the flow I mention. Once again, you need:

bootloader programmed into device
using flashed bootloader perform DFU process and send to device Application (eg. ble_app_multirole_lesc)
Bond in ble_app_multirole_lesc (with 2 separate devices)
enter bootloader and once again perform dfu with the same lesc application
When device enter application (after dfu) mention recently bug should appear when you try to connect with phones

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Tue, 03 Sep 2019 13:09:30 GMT

I used the ble_app_buttonless_dfu application to perform the bonding.

[quote user="Edvin Holmseth"]SDK\examples\ble_peripheral\experimental_ble_app_buttonless_dfu. [/quote]

It also has the possibility to trigger DFU mode in nRF Connect. Not sure exactly how the Android version of nRF Connect works, but some phones needs a characteristic that is locked by a pairing requirement to trigger the pairing request.

I changed:

BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.write_perm);

BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM(&cccd_md.write_perm);

on line 144 in ble_dfu.c to trigger this. It means that the connected device needs to be paired to enable notifications or indications (indications in this example). This requirement will trigger the phone to request pairing.

Best regards,

Edvin

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

patlas — Tue, 03 Sep 2019 12:53:30 GMT

I can try, but what "application" have you use? You mention about bootloader but additionaly you need some application perform bonding (Bootloader + SD + App) and perform bonding in Application and then go back to new (fresh) application and try to connect.

RE: [FDS] PeerManager error -> try to find record which recently has been invalidated

Edvin — Tue, 03 Sep 2019 12:50:12 GMT

Hello,

I tried to perform the test that you described, but I couldn't reproduce it. It was one phone and one DK using nRF Connect for Desktop. Can you try to reproduce it using the example:

SDK\examples\ble_peripheral\experimental_ble_app_buttonless_dfu.

Does it happen if you use a "clean" SDK (That is just unzipped, and not modified in any way). Maybe you changed something in another project that affected some common files?

Best regards,

Edvin