There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Hung Bui — Wed, 28 Aug 2019 11:34:45 GMT

Hi Aser,

RAM overlapping shouldn't be a problem. The bootloader and the application wouldn't run at the same time. I just tested here and don't see the problem that you are having.

Could you let me know how exactly you flashed the bootloader and the application ? with step by step. For example:

1. Flash softdevice using nrfjprog. (please specify what exact command you used to test)

2. Flash bootloader

3. ....

I attached here the hex files (BL,SD,APP) that I read from my board. You can use this file to test.

I have modified the bootloader so that it by default will jump to the application. The sequence you would need to do with nrfjprog (don't use nrfconnect) is:

1. nrfjprog --eraseall

2. nrfjprog --program .\s132_nrf52_3.0.0_softdevice.hex

3. nrfjprog --program .\buttonless.hex --sectorerase

4. nrfjprog --program .\nrf52832_xxaa_s132_compressed.hex --sectorerase

Please use the exact sequence. If you flash the bootloader before the application you may risk erasing the bootloader setting.

devzone.nordicsemi.com/.../buttonless.zip

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Aser — Wed, 28 Aug 2019 08:36:24 GMT

Oh! I solved it.
I didn't know that I had to merge boot.hex and application.hex and download them to the chip in order to set the device to invoke boot mode without a button when the application is up.
I'm working on fixing that issue now and applying source to my project.

But I still can't find a command to call boot mode haha .... ㅠㅠ :(
Instead, the command you gave me seems to help a bit.
Is it right to call boot mode using that part?
I will try more. Thank you.

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Aser — Wed, 28 Aug 2019 04:54:44 GMT

I just found the source of this problem through the nRF Connect utility.
The problem was confirmed that the memory map areas overlap.
The bootloader area overlaps with the application (buttonless) area.
However, I do not understand that these two sources were tested using the original ones, and I do not understand that this phenomenon occurs.
Do you have a solution that you know?

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Aser — Wed, 28 Aug 2019 02:52:44 GMT

This file is a log of an issue where only the same log I talked about repeatedly is taken and DFU is not going on. This log is from Nordic's nRF Connect app.
Would you please take a look?

devzone.nordicsemi.com/.../Log-2019_2D00_08_2D00_28-11_5F00_37_5F00_52.txt

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Aser — Wed, 28 Aug 2019 01:51:33 GMT

Hello Bui. Good morning.
I've done a lot of DFU with the DFU Button you mentioned, but it's repeatedly output the same log as an infinite loop.
I don't know why.
When this is resolved, the phone sends a signal to the boot mode and it will be able to apply it to the My Project.
Thank you.

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Hung Bui — Tue, 27 Aug 2019 11:01:28 GMT

Hi Aser,

If you instead click on the DFU button can you do a DFU update ? The app should detect that it's a buttonless application and perform the DFU buttonless automatically.

The buttonless application is quite simple. It waits for a write request to write to a flag in flash and then reset to the bootloader.

You can debug the buttonless application quite easily. You can check if enter_bootloader() is called inside on_ctrlpt_write() when there is a BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST.

Please be aware that SDK v12.3 is pretty old. We changed the way we enter DFU bootloader (using GPREGRET instead of flash ) from SDK v13. The current SDK is v15.3

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Aser — Tue, 27 Aug 2019 08:38:43 GMT

I realized that I was doing something wrong after all my attempts.
First, mark the "↓x3" button and press the "↑" button.
I realized that I had to choose Request instead of Command in a pop-up window.
But even though I have tried to switch to boot mode countless times through this method, I still use Nordic Buttonless to do it.
:(What should I do?

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Aser — Tue, 27 Aug 2019 00:06:53 GMT

Hi, Bui.
Thank you very much for your reply.
Thanks to your kind Tutorial, the bootloader example has been successfully used.
Thank you for this, too.

After setting up the boot loader mode, when BLE Scan is done again, "DFU Targ" is not detected.
The application is original and no modifications have been made to Source.
Now I suspect that the red box button is the one that sets the Bootloader mode after the connection.
In the above test, we downloaded the Buttonless Application with only the Bootloader Source downloaded. In this case, the next buttonless application was downloaded while the update was completed.

RE: There is a question in Test Setp about the buttonless DFU sample using the nRF52832 DK board. (SDK is using 12.3.)

Hung Bui — Mon, 26 Aug 2019 16:14:38 GMT

Hi Aser,

I assume that you didn't see the device advertised as "DFU Targ" after you set it to bootloader mode? What was the behavior after the write ?

I suspect that the application has crashed, you may want to check if it enters any assert handler or if it resets.

Have you flashed the bootloader ? Do you have any issue if you test the bootloader (without the buttonless application)?