dfu fails only if bonded

RE: dfu fails only if bonded

seanbites — Tue, 15 Mar 2016 16:59:37 GMT

Yes, this is what I feared. I will port my code to the SDK11 this weekend. Thanks a lot for your help!

RE: dfu fails only if bonded

Hung Bui — Tue, 15 Mar 2016 13:37:35 GMT

Hi Sean,

Just to clarify we don't have SDK v9.2 it's nRF52 SDK v0.9.2.

This SDK is alpha and is not production grade, especially the S132 v1.0.0-3alpha. You could have an issue if you want to qualify your product with S132 v1.0 alpha.

So I strongly suggest you to move to the production version S132 v2.0.

Note that the SDK v11 still use device manager. You should not have too much problem porting to the new softdevice and the SDK.

However, I also did some investigation on the issue with bonding and DFU on SDK v0.9.2. Yes, there are some modification needed:

Please copy and replace function pstorage_flash_page_end() in your pstorage_platform.h the one in the same file in SDKv11\examples\ble_peripheral\ble_app_hrs\config. This will solve the issue that storing bond information will overwrite the bootloader.
Replace the nRF_UICR->BOOTLOADER_ADDRESS with NRF_UICR->NRFFW[0] in dfu_app_handler.c

I attached in the answer the updated files.

P/S: Sorry I was confused between 2 version, yes in SDK v11 production in some examples we switched to peer manager, but there are still some examples use device manager such as ble_app_hts

RE: dfu fails only if bonded

seanbites — Mon, 14 Mar 2016 18:28:59 GMT

The bootloader from sdk11 works fine on its own as long as I use the newer version of the softdevice. However, my application is based on the sdk 9.2 so I cannot use the newer softdevice. I believe the newer SD uses a different device manager, the peer manager, and I assume it has numerous other differences, not to mention that I have heavily modified the bootloader in order to support functionalities I need, so I would prefer not to have to migrate to sdk11. Note, however, that the bonding issue is present when I use an unmodified version of the bootloader. This would indicate that either 1. the bootloader as it is given in the sdk9.2 is incapable of exchanging peer information or 2. my application has a fault in it. Would you be able to test on your end if the bootloader from 9.2 is capable of peer information exchange when bonded? That would isolate one variable and I can then confirm that the issue is not memory mapping from the linker file or an inherent flaw of the bootloader from 9.2, but rather an issue with my application. Thanks!

RE: dfu fails only if bonded

Hung Bui — Fri, 11 Mar 2016 15:40:56 GMT

Hi Sean,

I tried with the latest SDK v11 production (released yesterday) and compile with gcc and tested here, it worked fine with and without bonding. I attached here the hex file of the bootloader and the .zip file for updating, could you test on your side ?

Note that you need to use the S132 v2.0.0 production. To trigger bonding you can try to write to CCCD of the heart rate service

myapp.zip

bootloader_s132.hex

Update 15 Mar:

For SDK 0.9.2

RE: dfu fails only if bonded

seanbites — Fri, 11 Mar 2016 14:47:13 GMT

Yes, that is correct.

RE: dfu fails only if bonded

Hung Bui — Fri, 11 Mar 2016 14:46:28 GMT

Hi Sean, I assume that mean you have tested without bonding and it worked ?

RE: dfu fails only if bonded

seanbites — Fri, 11 Mar 2016 14:12:14 GMT

I uploaded the file using drop box and that issue is solved! The problem was with google drive not recognizing the .zip file as a .zip file. Interesting!

So that still leaves us with the failure on bonding. It appears to fail at the same spot everytime. I will set up the bootloader for debugging and I will figure out exactly where it fails and get back to you. Thank you so much for your help!

RE: dfu fails only if bonded

Hung Bui — Fri, 11 Mar 2016 13:10:24 GMT

Hi seanbites,

It could be the problem here. If you connect your phone to PC and copy the file to PC do you have the same issue ? On my phone the same file "dfu_test_app_hrm_s132.zip" is not grayed out.

RE: dfu fails only if bonded

seanbites — Thu, 10 Mar 2016 21:12:02 GMT

I have added a screenshot in the original question. Notice that, at the very bottom, myapp.zip is grayed out. Am I not using nrfutil.exe properly? Here is an example of the types of commands I write:

nrfutil dfu genpkg --application nrf52832_xxaa_s132.hex --application-version 0xffffffff --dev-revision 0xffff --dev-type 0xffff --sd-req 0xfffe myapp.zip

Is it possible that this is a problem with Google drive, which does not recognize that this is indeed a .zip file format? When I use my phone to check information on this file, it says "unknown type".

RE: dfu fails only if bonded

Hung Bui — Thu, 10 Mar 2016 16:47:21 GMT

@seanbites: It worked fine on my Galaxy S6. Make sure you have the latest version of Master Control Panel. I don't see any reason it allowed to selected the file if you use bootloader from SDK v0.9 but not if you bootloader from SDK v11. Could you take a screenshot ?

I would suggest you to update the bootloader so that you can run it in debug mode. Please have a look here. You can debug and find why the bootloader won't jump to the application.

But I suggest to fix the stuff step by step, by first make the bootloader does its job, do DFU.

If you plan to use the sniffer on nRF52 board, you may need to match the UART pins with what we have on the PCA10028 or PCA10031 (08=RTS, 09 = TXD, 10= CTS, 11= RXD)

I don't think you need any modification to make the bootloader work with bonding in SDK v0.9.2

RE: dfu fails only if bonded

seanbites — Thu, 10 Mar 2016 13:52:50 GMT

In the SDK 9.2, are bond informations shared properly between the application and the bootloader, or am I going to have to do some modifications?

RE: dfu fails only if bonded

seanbites — Thu, 10 Mar 2016 13:17:45 GMT

Hello, thank you for answering,

When I flash the device with the bootloader from sdk11 and the v2.0.07 s132 softdevice, it advertises and I can connect to it using the master control panel from my nexus 5.
However, when I try to upload a new firmware (dfu_test_app_hrm_s132.zip taken directly from the examples in the sdk11), the master control panel does not seem to recognize it (the file is displayed but it is grayed out and I cannot select it).
I cannot enter the application from the bootloader, even if I write a 0x01 to 0x7F000. Also, if I flash the device with s132 v 2.0.07 and my application, the application does not run seeing as it was conceived using a previous version of the softdevice/sdk. If I flash my device using the older softdevice and bootloader from sdk9.2, I am capable of doing a dfu perfectly fine so long as the device is not bonded.

Do you recommend that I port all of my code to the new sdk or is there a way around all of this, where I can still use the older bootloader/s132 from sdk9.2 and still share bonding information? I am getting Sniffer working (mind you, I'm working on a nrf52, which does not appear on the list of required hardware in the sniffer user guide) and I will get you a trace of the failure when bonded using sdk9.2. Thank you so much for your help, by the way!

RE: dfu fails only if bonded

Hung Bui — Thu, 10 Mar 2016 12:26:20 GMT

Hi Seanbites,

S132 from SDK v0.9.2 is v1.0.0-3 alpha when the S132 from SDK v11 is v2.0.07 alpha. They are not interchange able. Could you let me know what happens when you :

Flash the S132 softdevice from SDK 11 and bootloader (with no modification) from SDK v11. Would the bootloader advertise ?
Use the bootloader to update the application firmware (let's start with an SDK example application) Would the DFU success ? If not, please track a sniffer trace
If it manages to update the application, please try to do buttonless (switch from application to bootloader) and try update without bonding then with bonding.

RE: dfu fails only if bonded

seanbites — Wed, 09 Mar 2016 19:08:53 GMT

Here is a log of the original bootloader and application that works except when bonded.

nRF Master Control Panel, 2016-03-09
SeanHalo (C5:FA:0B:E9:06:FB)
V	14:04:31.854	Connecting to C5:FA:0B:E9:06:FB...
D	14:04:31.870	gatt = device.connectGatt(autoConnect = false)
D	14:04:32.189	[Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
D	14:04:32.206	[Broadcast] Action received: android.bluetooth.device.action.ACL_CONNECTED
I	14:04:32.218	Connected to C5:FA:0B:E9:06:FB
D	14:04:32.233	wait(600ms)
V	14:04:32.859	Discovering services...
D	14:04:32.874	gatt.discoverServices()
D	14:04:32.899	[Callback] Services discovered with status: 0
I	14:04:32.917	Services discovered
V	14:04:33.047	Generic Access (0x1800)
- Device Name [R W] (0x2A00)
- Appearance [R] (0x2A01)
- Peripheral Preferred Connection Parameters [R] (0x2A04)
Generic Attribute (0x1801)
- Service Changed [I] (0x2A05)
   Client Characteristic Configuration (0x2902)
Nordic UART Service (6e400001-b5a3-f393-e0a9-e50e24dcca9e)
- TX Characteristic [N] (6e400003-b5a3-f393-e0a9-e50e24dcca9e)
   Client Characteristic Configuration (0x2902)
- RX Characteristic [W WNR] (6e400002-b5a3-f393-e0a9-e50e24dcca9e)
Device Firmware Update Service (00001530-1212-efde-1523-785feabcd123)
- DFU Packet [WNR] (00001532-1212-efde-1523-785feabcd123)
- DFU Control Point [N W] (00001531-1212-efde-1523-785feabcd123)
   Client Characteristic Configuration (0x2902)
- DFU Version [R] (00001534-1212-efde-1523-785feabcd123)
V	14:04:44.421	Starting pairing...
D	14:04:44.437	device.createBond()
D	14:04:44.508	[Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDING (11)
D	14:04:48.753	[Broadcast] Action received: android.bluetooth.device.action.BOND_STATE_CHANGED, bond state changed to: BOND_BONDED (12)
I	14:04:48.770	Device bonded
V	14:04:59.451	Disconnecting...
D	14:04:59.467	gatt.disconnect()
D	14:04:59.485	[Callback] Connection state changed with status: 0 and new state: DISCONNECTED (0)
I	14:04:59.498	Disconnected
D	14:04:59.512	gatt.refresh()
D	14:04:59.525	gatt.close()
V	14:04:59.696	[DFU] DFU service started
V	14:04:59.715	[DFU] Opening file...
D	14:04:59.803	[Broadcast] Action received: android.bluetooth.device.action.ACL_DISCONNECTED
I	14:04:59.971	[DFU] Image file opened (19424 bytes in total)
D	14:04:59.983	[DFU] wait(1000)
V	14:05:00.989	[DFU] Connecting to DFU target...
D	14:05:01.009	[DFU] gatt = device.connectGatt(autoConnect = false)
E	14:05:31.018	[DFU] Connection failed (0x85): GATT ERROR
D	14:05:31.102	[DFU] gatt.close()
V	14:05:31.115	Connecting to C5:FA:0B:E9:06:FB...
D	14:05:31.126	gatt = device.connectGatt(autoConnect = false)
D	14:06:01.146	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	14:06:01.161	Error 133 (0x85): GATT ERROR
I	14:06:01.277	Disconnected
D	14:06:01.292	gatt.close()

RE: dfu fails only if bonded

seanbites — Wed, 09 Mar 2016 18:44:57 GMT

I have programmed the bootloader from sdk11 onto my device using the s132 softdevice from sdk9.2 and my bootloader no longer launches the application even though I write : nrfjprog --family nRF52 --memwr 0x7F000 --val 1, so forcing the application to start by writing 0x01 to the bootloader settings address. Additionnally, dfu no longer work either. I have also tried the same thing using the s132 softdevice from sdk11 and I get the same results. What can I do to fix this issue and what additionnal informations would you need to be able to help me? Thanks a lot!

RE: dfu fails only if bonded

seanbites — Wed, 09 Mar 2016 14:52:00 GMT

I am using the version 9.2 of the SDK, I have not modified the linker file mentioned above, let me find the v11 of the sdk and I will get back to you. Also I have set the IS_SRVC_CHANGED_CHARACT_PRESENT to 1 in my main.c. i will get you a sniffer log shortly

RE: dfu fails only if bonded

Hung Bui — Wed, 09 Mar 2016 13:50:32 GMT

Hi Sean,

Which SDK version are you testing ? Have you modified anything ? NOINIT is already configured correctly in the dfu_gcc_nrf52.ld file in SDK v11 alpha.

Have you made sure you enable IS_SRVC_CHANGED_CHARACT_PRESENT = 1 in your application to allow Service changed indication ? A sniffer trace and the log from the DFU tool can tell more on what could be wrong here.