Setting Up OTA DFU for BMD-350-EVAL Board Windows 10

[Caleb Dueck]

Hello,

I've been struggling to follow along with this tutorial:  Getting started with Nordic's Secure DFU bootloader, a step by step guide 

Is this the most up to date instructions for how to update the device over bluetooth?

I'm using SEGGER 5.68 and nRF 17.1.0

Thanks,
Caleb

[Einar Thorsrud]

That depends on what type of transport you want and which board you are using. Are you using the nRF52832 as a target device, if so PCA10040 (not suffixed with e) is the correct board type, so projects for that boards are suitable. Which transport do you want? BLE or UART? If you want BLE, select a project with that in the name. And while learning, I suggest you pick a project suffixed with "_debug" as it has extensive RTT loggign"

[Einar Thorsrud]

I would suggest sticking with micro-ecc if you want as small flash usage as possible, as you do not do that much crypto in the bootloader so size is probably more important than performance in that case, ans micro-ecc is the smallest. That said, flash adjustment is the same in the bootloader as with any other project. See Adjustment of RAM and Flash memory.

[Caleb Dueck]

I've installed the GOW package using GOW.exe
However I am getting a different error.

C:\Users\Caleb(CDUE)\Documents\FW\OTA Work\nRF5SDK153059ac345\nRF5_SDK_15.3.0_59ac345\external\micro-ecc\nrf52nf_armgcc\armgcc>make
mkdir _build
'C:\Users\CALEB' is not recognized as an internal or external command,
operable program or batch file.
make: *** [../../../../components/toolchain/gcc/Makefile.common:254: _build] Error 1

The contents of nRF5_SDK_15.3.0_59ac345\components\toolchain\gcc\makefile.windows

I've modified this to point to where GNU is installed on my PC so I am now getting a new error.

GNU_INSTALL_ROOT ?= C:/Program Files (x86)/GNU Tools ARM Embedded/5.4 2016q3/bin/
GNU_VERSION := 5.4.1
GNU_PREFIX := arm-none-eabi

I'm confused as to why this needs to be referenced as one of the features of GOW is that it adds all binaries to the windows path.

[Caleb Dueck]

Thank you. I am using a a BMD-350 eval board which is based on the NRF52832.
I am trying to configure DFU with BLE so I will use: nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_bootloader\pca10040_ble_debug

[Einar Thorsrud]

Hi,

Did you get to the bottom of this?

Regarding the first issue, I think there may be issues with parenthesis in the path, so that may be the issue there.

Regarding GNU_INSTALL_ROOT etc in the makefile.windows, that must be set to be correct for your specific environment. The reason for this not using whatever is in your path is that in some cases you may have different SDKs etc installed, each which you for some reason want to use with different specific versions of ARM GCC (typically you want to use the version that was used in release testing, and which is specified in the release notes).