Debug why DFU start packet not starting DFU

[cswanson420]

Firstly, platform: Sparkfun 52832 breakout board, DFU using UART, flashing an application, using nrfutil.

The problem fundamentally is the nRF52832 is not sending an ack that it received the DFU start packet. The packet is formatted correctly as defined by infocenter.nordicsemi.com/.../bledfu_transport_serial.html

the nrfutil code indicates a timeout as a result of not receiving the ack for the start packet.

I have the capability to use the nRF52DK with J-Commander to look at various places in memory and the registers, I just don't know how to go about determining why the SoC is not replying.

I also am guessing that there is the possibility the CPU in the nRF52832 may not actually be running the bootloader code, although from the appearance of the flashing LED the hardware presents itself as being in the bootloader mode.

Questions:

1. Is there a means to derive whether the code executing is the bootloader code,
2. If the code is bootloader code, how could one determine why the start packet is not being acknowledged and subsequently moving the the next state in the DFU state machine.

[bjorn-spockeli]

I downloaded the repository and compiled the bootloader for the PCA10040 board (just uncommented CFLAGS += -DBOARD_PCA10040 and commented out #CFLAGS += -DBOARD_CUSTOM in the Makefile).I flashed it to the DK along with the Softdevice from the hex folder. I had to enable flow control with nrfutil in order to perform a serial DFU, i.e.

nrfutil dfu serial -pkg ble_app_hrs.zip -p COM51 -fc