SDK15.3 buttonless dfu example cant get into dfu mode on pca10040 using armgcc build.

RE: SDK15.3 buttonless dfu example cant get into dfu mode on pca10040 using armgcc build.

Sigurd — Mon, 28 Oct 2019 09:27:56 GMT

Hi Ming Xian,

Please create a new question for this. See this link.

RE: SDK15.3 buttonless dfu example cant get into dfu mode on pca10040 using armgcc build.

Ming — Mon, 28 Oct 2019 08:19:30 GMT

Hi,

Now I have encountered a similar problem. In SDK 15.3, the bootloader setting is used. But the program still can't directly execute the application. After that, I used the two instructions you said, but still did not solve the problem.

best wish.

RE: SDK15.3 buttonless dfu example cant get into dfu mode on pca10040 using armgcc build.

Sigurd — Fri, 20 Sep 2019 13:02:32 GMT

Hi,

I don't see anything wrong in the log. The DFU bootloader is found, and the DFU service is started.

11:04:27.532 [DFU] Scanning for the DFU Bootloader...
11:04:27.798 [DFU] DFU Bootloader found with address D3:CD:8A:FD:E1:52
11:04:27.834 [DFU] DFU service started
11:04:27.834 [DFU] Firmware file opened successfully

Did you connect manually here? If yes, could you upload a log where you don’t manually connect?

RE: SDK15.3 buttonless dfu example cant get into dfu mode on pca10040 using armgcc build.

Mark P. Mendelsohn — Tue, 17 Sep 2019 18:15:38 GMT

We use a separate script to merge all 4 components before flashing the pca10040 so this does not seem to be the issue we are experiencing.

Additional info on this issue. nRF Connect on Android can see the Buttonless device, DFU is requested, the device goes into DFU mode since DfuTarg can be seen but stops. Manually connecting to the Dfutarg advertising device and retrying the DFU will go to completion. So the issue seems to be nRFConnect cannot complete the DFU without manual intervention or SDK15.3 is not allowing it.devzone.nordicsemi.com/.../5672.log.txt devzone.nordicsemi.com/.../loadallthree.sh

RE: SDK15.3 buttonless dfu example cant get into dfu mode on pca10040 using armgcc build.

Sigurd — Tue, 17 Sep 2019 16:11:51 GMT

Hi,

In 15.3.0 we started using the MBR section to hold the bootloader start address instead of UICR.

Are you using make flash and make flash_softdevice commands for flashing the application/bootloader ?

If yes, see this post :

flash_sdbl: default
	@echo Flashing Softdevice and bootloader
	mergehex -m $(OUTPUT_DIRECTORY)/nrf52832_xxaa_s132.hex $(SDK_ROOT)/components/softdevice/s132/hex/s132_nrf52_6.1.1_softdevice.hex -o sdbl.hex
	nrfjprog --program sdbl.hex --chiperase -r

Similar post for Keil can be found here.