nrfutil DFU BLE and connectivity firmware

RE: nrfutil DFU BLE and connectivity firmware

MarcoTull — Fri, 19 May 2017 16:14:11 GMT

Thanks, for all the help. A last question my whole program was made on SDK13 is possible apply it for the SDK13? making the changes for myself and what values for RAM (rwx) : ORIGIN = 0x2000bcc0, LENGTH = 0x4340 should I put SDK13>

RE: nrfutil DFU BLE and connectivity firmware

tesc — Fri, 19 May 2017 15:59:46 GMT

Of course! We use the hci version, not uart, so you were trying with the wrong example. Sorry for missing that.

RE: nrfutil DFU BLE and connectivity firmware

MarcoTull — Fri, 19 May 2017 13:07:33 GMT

@Terje Schjelderup I was able to apply the patch :)

Now I am testing with the ser_s132_hci being a little slow about 2mins to perform the DFU and ser_s132_uart (unable to perform the DFU yet)

trying to improve the speed

RE: nrfutil DFU BLE and connectivity firmware

tesc — Fri, 19 May 2017 08:53:08 GMT

That is the last line. I suspect whitespace. Can you double check that you have the full last line, and try with the --ignore-whitespace option?

RE: nrfutil DFU BLE and connectivity firmware

MarcoTull — Thu, 18 May 2017 22:58:07 GMT

I tried using the patch, but I always got the following message :

Nordic/nRF5_SDK_12.1.0_0d23e2a
$ git apply < sdk121_connectivity.patch
error: corrupt patch at line 194

RE: nrfutil DFU BLE and connectivity firmware

tesc — Thu, 18 May 2017 15:33:38 GMT

If you apply the patch then it should recognise the firmware. Also, by default it should not flash the connectivity firmware. It will do so only if you provide the -f option. What is the nrfutil version?

RE: nrfutil DFU BLE and connectivity firmware

MarcoTull — Thu, 18 May 2017 15:20:40 GMT

@Terje SchjelderupTerje Thanks for the reply. Before I made any changes I am trying make to work the connectivity firmware with no luck. I am able to compile it using gcc, but when I runnrfutil DFU BLE it keeps programming other 'connectivity firmware' removing the one I programmed before

update:

I am getting the following error:

Thanks, Marco

RE: nrfutil DFU BLE and connectivity firmware

tesc — Thu, 18 May 2017 15:12:56 GMT

@marcotull Hi, I have given this some more thought, and it is definitely best to keep it at the SDK and SoftDevice it was originally made for. Porting it would quickly require changes in pc-ble-driver as well. You may have a wish to do all development using the same SDK, I can see great value in that, but in this case it simply is not worth the effort. If you miss functionality in the current version then please let us know, so that we can consider it for future releases.

RE: nrfutil DFU BLE and connectivity firmware

MarcoTull — Thu, 18 May 2017 14:08:59 GMT

@tesc I want to port it to another SDK version

@bjorn-spockeli Thank for the info now it is more clear for me

Marco

RE: nrfutil DFU BLE and connectivity firmware

bjorn-spockeli — Thu, 18 May 2017 13:14:32 GMT

The patch is SDK v12.1.0 specific, however it might work with SDK v13, but I have not tried that.

RE: nrfutil DFU BLE and connectivity firmware

tesc — Thu, 18 May 2017 13:12:38 GMT

The patch is based on SDK v12.1.0. It will not work on other SDK releases. If you need to base it on another version of the SDK then you must port this patched version to the target SDK on your own.

RE: nrfutil DFU BLE and connectivity firmware

MarcoTull — Thu, 18 May 2017 13:04:20 GMT

Does it works using SDK v13?

RE: nrfutil DFU BLE and connectivity firmware

bjorn-spockeli — Thu, 18 May 2017 12:55:27 GMT

Hi Marco,

in order to create connectivity firmware that is compatible with custom nRF52 hardware you have to apply the sdk121_connectivity.patch, found here in the pc-ble-driver GitHub repo, to the connectivity example in SDK v12.1.0. You can find the connectivity example in examples\ble_central_and_peripheral\ble_connectivity\pca10040\ser_s132_hci. You can then change the pinout in pca10040.h or create a custom_board.h to match your custom hardware.

Best regards

Bjørn