Issues with DFU for SD v7

RE: Issues with DFU for SD v7

Asbjørn — Mon, 06 Oct 2014 13:59:12 GMT

@Anne, the first thread he recommends using the 32 kHz RC, that's not the same as the SYNTH.

RE: Issues with DFU for SD v7

Ignacio Lopez — Mon, 29 Sep 2014 15:22:11 GMT

I have started a new post about this issue. Follow this link:

devzone.nordicsemi.com/.../

RE: Issues with DFU for SD v7

Anne — Fri, 26 Sep 2014 21:54:49 GMT

No worries ^^ You're well into territory I've never explored (I never changed the bootloader) but those size numbers in the second screengrab look really, really broken. Maybe start a new thread asking about issues with the 128kB chip version?

RE: Issues with DFU for SD v7

Nguyen Hoan Hoang — Fri, 26 Sep 2014 13:23:17 GMT

I also use NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM on my boards. Works fine in both C0 and G0 revisions. I don't install the 32KHz on my custom boards. It increase BOM costs for no reason.

RE: Issues with DFU for SD v7

Ignacio Lopez — Fri, 26 Sep 2014 12:56:41 GMT

Hi anne,

Thanks a lot for you help. I managed to get it working with the dev board nRF6310+PCA10006. This is a configuration with a 256kb. Yes you are right, the 128kb only supports application update and this is exactly what i wanna do. I've modified the bootloader project to start at the address 0x1C000 and reduce the size of the ble_app_hrs_dfu project to 0x6000 (24kb). The device doesnt advertise. I am trying to debug it now.

Also I have observe that once the bootloader is flahsed the nRFgo Studio recognize the device as 256kb. I am going to attach some screen captures in the top comment.

It would be great if anyone could write a detailed step guide about how to get the bootloader working in the 128kb version. Remember that I want to be able to update only the application code.

RE: Issues with DFU for SD v7

Anne — Thu, 25 Sep 2014 22:19:01 GMT

@Ignacio. Ahhh, right. I was being unclear: the bootloader uses the scheduler but the heart rate app doesn't. I messed this up, I told the bootloader not to use the scheduler, and that's why my code didn't run.

Also, have you made sure that the Bootloader/DFU start address is set properly? Scroll down to the bottom of the Keil project page in the SDK, there's a screenshot of what the Keil configuration window for location should look like.

BTW, the SDK says the 128 kB version doesn't support DFU of the SoftDevice or Bootloader. You should still be able to update your application, though.

RE: Issues with DFU for SD v7

Ignacio Lopez — Thu, 25 Sep 2014 13:16:33 GMT

Hi Asbjørn

Thank you for your quick reply. I have the following error trying to flash the bootloader hex

Program Size: Code=14180 RO-data=328 RW-data=256 ZI-data=5988
FromELF: creating hex file... "._build\bootloader.axf" - 0 Error(s), 0 Warning(s). *** Completed Cross-Module-Optimization after 3 iteration(s). "nrfjprog.exe" --reset --program "C:\Keil_v5\ARM\Device\Nordic\nrf51822\Board\nrf6310\device_firmware_updates\bootloader\arm_build\bootloader.HEX" Parsing hex file(s). ERROR: Hex file(s) contain addresses outside the code, RAM and UICR areas.

I am using a 128kb version of the chip

RE: Issues with DFU for SD v7

Asbjørn — Thu, 25 Sep 2014 13:07:27 GMT

I'm not sure why you don't see it as advertising as a DFUTarg after you followed the steps and push back as stated in step 6. I would do a quick test with the bootloader example in the SDK just to make sure you are doing the app/MCP correct. Compile and flash the example from the SDK here(placed in my tree structure): C:\Nordic Semiconductor\nRF51 SDK\nrf51_sdk_v6_1_0_b2ec2e6\nrf51822\Board\nrf6310\device_firmware_updates\bootloader

Erase the chip, program softdevice and this example and you should by default see the DFUTarg advertising. Make sure you can upload a new FW from this first of all.

RE: Issues with DFU for SD v7

Ignacio Lopez — Thu, 25 Sep 2014 11:22:27 GMT

Hi Anne,

Thanks for your reply. I am using the ble_app_hrs_dfu project and I haven't modified any line after installing the SDK. The 'USE_SCHEDULER' is set to false as follows:

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, false);

I think this is correct because the project is not using the scheduler to organise the events. I cannot see the scheduler initialise in any part of the code.

RE: Issues with DFU for SD v7

Anne — Thu, 25 Sep 2014 02:34:02 GMT

Make sure that when you change the clock source SOFTDEVICE_HANDLER_INIT() that 'use scheduler' is still 'true'. I think part of my problem was that I copypasted a line over from the heart rate sensor which changed that.

RE: Issues with DFU for SD v7

Anne — Thu, 25 Sep 2014 02:29:46 GMT

Also, a quick heads up for you Nordic folks: this thread, and this one both recommend setting the clock source to NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM as a fix for the custom board issue (that's where I got the idea to do so in the first place). If that's changed with v7, you might want to make sure that the forums acknowledge this.

RE: Issues with DFU for SD v7

Anne — Thu, 25 Sep 2014 00:56:39 GMT

Success! I tested it with both the MCP app (v2.0.2 on a Nexus 5) and the PC program. Here are all the changes that I made in case they're useful to anyone else ^^

In ble_stack_init() of the heart rate sensor app, change "SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, false)" to "SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION , false)"
In ble_stack_init() of the bootloader, change "SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, true)" to "SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION, true)"

I also changed the LED pins used by the applications to those appropriate to my board but somehow I don't think that's what solved my problem.

Thanks for your help, guys ^^

RE: Issues with DFU for SD v7

Ignacio Lopez — Wed, 24 Sep 2014 17:24:54 GMT

I've found the same error. My configuration is as follows:

SDK 6.1.0.0 using ble_app_hrs_dfu project without any change.
s110_nrf51822_7.0.0_softdevice.hex
nRFgoStudio 1.17.0
MCP 3.6.0

I have used the following documentation:

devzone.nordicsemi.com/.../a00076.html

On the step 6, I click back but I can only see the device advertising again as 'Nordic_HRM'. I couldn't find the string "DfuTarg" searching files on the current project.

Debugging I could see that the code is calling the bootloader_start function.

Any other suggestion to test on my side?

I have also tried the dfu with the nRF Toolbox from a nexus 4 and iphone 5 without any luck.

Thanks.

Screen Captures

RE: Issues with DFU for SD v7

Stefan Birnir Sverrisson — Wed, 24 Sep 2014 12:15:42 GMT

This is working fine on my side with the standard ble_app_hrs.hex example from nRF51 SDK v6.1.0, S110 v7.0.0 and the default bootloader provided in nrf51 SDK v6.1.0. I upload the new application with the nRF Master Control Panel for Android v2.0.2 on Samsung Galaxy S4.

So I suggest you try what Asbjørn has suggested already to see if that fixes the problem

RE: Issues with DFU for SD v7

Asbjørn — Wed, 24 Sep 2014 12:05:00 GMT

The 32 kHz synthesized source is not tester or recommended with the S110 stack. Use NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION instead and that should enable you to use the bootloader and DFU.