Issue with OTA DFU on NRF 52832

RE: Issue with OTA DFU on NRF 52832

Hung Bui — Wed, 27 Jan 2021 09:59:22 GMT

Hi Pastagas,
Please send us the hex files you used for flashing. If possible please include the .zip file for DFU (you can test updating a dummy application, blinky for example) so we can test here.

Please do a hex dump after you flash in both cases, with and without the nRF Connect tool.

RE: Issue with OTA DFU on NRF 52832

pastagas — Tue, 26 Jan 2021 15:12:03 GMT

Hello,

I come back to you because I see that bug is not fixed on new programmer release V1.4.8.

When do you think solving this issue ?

Best regards

RE: Issue with OTA DFU on NRF 52832

pastagas — Thu, 20 Aug 2020 15:03:26 GMT

Hello Hung,

I used mergehex to merge both softdevice and bootloader and after I programmed the target using nrfjprog.exe...... and it works !!!!

your gui tool programmer seems to be bugged...I hope you will fix this issue.

Thx for helping.

Best regards

RE: Issue with OTA DFU on NRF 52832

Hung Bui — Wed, 19 Aug 2020 15:11:26 GMT

Hi,
After you do hex dump do you have the .hex files ?
You can use Notepad++ for example to compare the 2 hex files and can better see the difference.
From what you showed it's only the difference in the bootloader setting and the MBR page param.

Please try to test programming (and hex dumping) using the nrfjprog.exe tool.

RE: Issue with OTA DFU on NRF 52832

pastagas — Wed, 19 Aug 2020 14:06:37 GMT

Hello Hung,

Sorry for late reply, I was busy with another project.

You find below two pictures. They show memory mapping after a dump.

"Mapping_Bootloader_Only_SES" is a dump after programming device with SES. This image works well.

"Mapping_Bootloader_Only_Nrf_Programmer" is a dump after programming device with nrf programmer. In this case I have add separately bootloader.hex and softdevice 6.1.1.hex in the file memory layout window. After that I programmed the device. This image doesn't work

As you can see there are many differences that can explain why the second image doesn't work.

Best regards

Mapping_Bootloader_Only_SES"

Mapping_Bootloader_Only_Nrf_Programmer

RE: Issue with OTA DFU on NRF 52832

Hung Bui — Wed, 22 Jul 2020 15:30:26 GMT

Without logging it will be difficult to debug. So either you need to output UART to another GPIO pins on the chip and connect to PC (via a NRF52 DK for example) or output out log on RTT. Or you can do the test on a nRF52 DK before testing on your board.

Another thing you can do is to read out the flash content after you flash using Segger Embedded Studio and when you program using nRF Connect Programmer and compare them. I don't have any idea why flashing using nRF Connect Programmer would cause an issue. Please also try to program using nrfjprog.exe command line to as well.

Did you make any modification to the bootloader ?
If you can provide us the bootloader project, and the DFU files that you used so that we can reproduce the issue here, we can try to debug it from here.

RE: Issue with OTA DFU on NRF 52832

pastagas — Wed, 22 Jul 2020 12:07:07 GMT

Hello,

In brief again:

- when sdk + bootloader programmed with Segger Embedded Studio, updating works.

- when sdk + bootloader programmed from an image (sames binaries than those working SES) with nordic programmer V 1.4.2, updating works but application is not launched. Worst: With pca10040_ble_debug, I can upload the firmware but after nothing occurs. A new upload is impossible, device seems not working and there is not advertising anymore.

"f it's the case I would suggest to try printing out logging on UART and check what's the issue"

Bjorn asked me to do the same thing and my response was:

Which uart are you talking about ?

Ble module is soldered on our own card and its uart is connectect to MCU uart of the card. I put a breakpoint on MCU uart interrupt to see at least if ble module send log frames, but nothing happens...

Best regards

RE: Issue with OTA DFU on NRF 52832

Hung Bui — Wed, 15 Jul 2020 14:13:02 GMT

Hi Pasta,

Bjørn is on vacation and I will take over your case.

I'm summing up the issue you are having.

When you start on a blank chip you can upload the softdevice + bootloader and do DFU update an application. The application works fine. And you can do DFU update another application with no problem ?

After that if you flash the softdevice + bootloader (a modified bootloader ? ) then you still can see the DFUTarg advertising but if you do application DFU the DFU succeed but nothing happens after that ?
And if you run the bootloader in debug mode, it worked ?

If it's the case I would suggest to try printing out logging on UART and check what's the issue , why the bootloader didn't jump to the application, or if it jump to the application but the application couldn't start.

In SDK v15.3 we implemented secure booting with boot validation. I'm not sure it's the root cause but there is a chance it's the reason.

RE: Issue with OTA DFU on NRF 52832

pastagas — Fri, 26 Jun 2020 14:03:43 GMT

Hello,

With pca10040_ble_debug, behaviour is not the same. I can upload the firmware but after nothing occurs. A new upload is impossible, device seems not working and there is not advertising anymore.

Note that:

- If pca10040_ble_debug is programmed with the ide segger, it works fine too...

- If I make a dump of device once programmed with segger IDE and I program it with nrfconnect programmer, it works too

Which uart are you talking about ?

Best regards.

RE: Issue with OTA DFU on NRF 52832

bjorn-spockeli — Thu, 25 Jun 2020 08:31:17 GMT

Yes I have understod that. What I would like to know is if you see the same behaviour, i.e. DFU not working if you have the the debug version of the bootloader, i.e. nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_bootloader\pca10040_ble_debug, flashed to your nRF device and then perform a bootloader + SoftDevice + app update.

If this fails, then you will get the debug log output over UART from the bootloader, which can assist in figuring out where things go wrong.

So I kindly ask you to

Flash the nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_bootloader\pca10040_ble_debug example to your nRF device ( remember to switch the public key so that its compatible with your image)
Open a terminal, e.g. Putty to see the log output.
Start the DFU process from your smartphone or through nRF connect for Desktop.
Attach log output to this ticket so I can take a look at it.
You can also attach the log from your smartphone or nRF Connect as well so that we have logs from the nRF side and the mobile/pc side.

RE: Issue with OTA DFU on NRF 52832

pastagas — Thu, 25 Jun 2020 08:19:39 GMT

I am not sure I have well explained the issue. In debug mode, it works. The problem occurs only when I programm the device with a full image (bootloader + sdk + app)

RE: Issue with OTA DFU on NRF 52832

bjorn-spockeli — Wed, 24 Jun 2020 19:40:13 GMT

Ok, I though you were not able to debug. If it works in a debug session, then you can try to use the debug version of the bootloader, i.e. nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_bootloader\pca10040_ble_debug. This will print log information, so you can see whats going on without debugging.

RE: Issue with OTA DFU on NRF 52832

pastagas — Tue, 02 Jun 2020 06:59:58 GMT

Hello,

Sorry for late reply, I was in holidays. Yes I use SES.

"then you should be able to attach to the running code with a debugger the bootloader project to see whats going on."

What do you mean ?

It works in debug mode, so i will not able to see what is going on.....

Best regards

RE: Issue with OTA DFU on NRF 52832

bjorn-spockeli — Mon, 18 May 2020 06:54:40 GMT

Which IDE are you using? I you are using SES, then you should be able to attach to the running code with a debugger the bootloader project to see whats going on.

Do you see the same behavior if you flash the debug bootloader, i.e. nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_bootloader\pca10040_ble_debug. using nRF Programmer?

Best regards

Bjørn

RE: Issue with OTA DFU on NRF 52832

pastagas — Thu, 14 May 2020 09:47:02 GMT

Hi Bjorn,

I am using SDK 15.3.0.

nrf_bootloader_fw_activate() returns ACTIVATION_SUCCESS.

dfu_enter_check() returns false.

Note that in debug mode, the application is well launched by the bootloader once it has been updated.

The problem occurs when I use the bootloader programmed with the programmer of nRF Connect (windows 10).

In this case, I can't debug the bootloader and give you the values.

Regards

RE: Issue with OTA DFU on NRF 52832

bjorn-spockeli — Wed, 13 May 2020 13:01:59 GMT

Hi pastagas,

which SDK version are you using?

Can you debug the bootloader after the application update and check teh return value of nrf_bootloader_fw_activate() called in nrf_bootloader_init() in nrf_bootloader.c as well as the return value of dfu_enter_check() in the same function and file?

If there is a valid application present, then dfu_enter_check should return false.

Best regards

Bjørn