DFU reconnect problem

RE: DFU reconnect problem

Sejl — Sat, 22 Apr 2017 08:51:06 GMT

I found it. Problem was in bootloader. File dfu_ble_svc.c has to be configured in Keil in following manner: Right click on file, select "options for dfu_ble_svc.c" and set IRAM2 for Zero Initialized Data.

Hopefully, someone will find this helpful :)

Bjorn, thank you again for patience! Have a beautiful weekend!

Best regards, Sejl

RE: DFU reconnect problem

Sejl — Fri, 21 Apr 2017 16:19:12 GMT

Ok. I have tried, but with no success. I guess problem is somewhere in code.

I am using UICR_ADDR_0x84 and 0x88 for holding info about device serial number; do you thing this could mess things with DFU?

Another thing is - DFU procedure correctly starts bootloader, and bootloader correctly carries on DFU update. Only thing missing is detection of active bootloader from the nrfConnect side. Somwhere I have read that this is maybe due to different address of bluetooth device while in bootloader. How can I send info to DFU to expect different device address?

RE: DFU reconnect problem

bjorn-spockeli — Fri, 21 Apr 2017 15:53:30 GMT

Yes, those values look correct.

RE: DFU reconnect problem

Sejl — Fri, 21 Apr 2017 15:13:21 GMT

Ok, just to confirm memory settings:

Bootloader:
IROM1: 0x3C000/0x3C00
IRAM1: 0x20002C00/0x1380
IRAM2: 0x20003F80/0x80 (noinit)

Application:
IRAM1: 0x1B000/0x21000
IROM1: 0x20002800/0x1800

Is this correct?

RE: DFU reconnect problem

bjorn-spockeli — Fri, 21 Apr 2017 14:54:21 GMT

Sure, if you're using SDK v11.0.0, then you'll have to set the following memory settings

RE: DFU reconnect problem

Sejl — Fri, 21 Apr 2017 13:51:13 GMT

I have tried with SDK 11.0.0 and S130 v2.0.0. Same thing. Can we try to debug this using SDK 11? I don't need secure DFU, and all code is already written for S130 v2.0.0.

Btw, thank you for helping me :)

RE: DFU reconnect problem

Sejl — Fri, 21 Apr 2017 13:36:52 GMT

Well, I am using softdevice s130 v2.0.1 from SDK v12.2.0, everything else is from SDK v11.0.0. Of course, I have updated softdevice headers and source files. I will try to go back to S130 from SDK v11 just to test if it is working with older version.

RE: DFU reconnect problem

bjorn-spockeli — Fri, 21 Apr 2017 12:34:31 GMT

Are you sure that you're using the bootloader from SDK v12.2.0? The Secure bootloader does not have any IRAM2 section. I have attached a screenshot of the correct settings below

RE: DFU reconnect problem

Sejl — Fri, 21 Apr 2017 12:20:27 GMT

Yes, I am using DFU button. IRAM/IROM settings are as follows:

Application: IROM1: 0x1B000/0x24000 IRAM1: 0x20002800/0x1800 (noinit deselected)

Bootloader: IROM1: 0x3C000/0X4000 IRAM1: 0x20002800/0x1780 (noinit deselected) IRAM2: 0x20003F80/0x80 (noinit selected)

RE: DFU reconnect problem

bjorn-spockeli — Fri, 21 Apr 2017 12:14:15 GMT

You're using the DFU button in the upper right corner to perform DFU right? You not writing to the control point characteristic manually. Furthermore, since you're using the nRF51822 QFAA, have you adjusted the IRAM settings so that they correspond to 16kB of RAM and not 32kB? (The SDK examples are designed for the QFAC variant).

RE: DFU reconnect problem

Sejl — Fri, 21 Apr 2017 11:50:59 GMT

I am using SDK 12.2.0. Programming in Keil v5

RE: DFU reconnect problem

bjorn-spockeli — Fri, 21 Apr 2017 11:48:59 GMT

Which SDK version are you using?