NRF52 DFU Serial problem in SDK 15.3

RE: NRF52 DFU Serial problem in SDK 15.3

AndreasF — Mon, 08 Apr 2019 09:14:12 GMT

Hi.

Glad you got it working, good luck on the development!

Best regards,

Andreas

RE: NRF52 DFU Serial problem in SDK 15.3

dsasa — Mon, 08 Apr 2019 08:25:06 GMT

Hi Andreas,

I turned on logs in bootloader (level "Debug") to see what's happening. In logs I can see message that response is sent after last chunk, but it is not registered by the nrfutility. I suppose there is an issue with short time interval that nrfutil waits for a response and if it is not received it goes further. I tried this on development kit.

When I implemented a longer wait time in my firmware, it started working. I'm getting response to the last command now. So we can conclude that adding a delay at line 573. is a solution!

Thanks!

RE: NRF52 DFU Serial problem in SDK 15.3

AndreasF — Fri, 05 Apr 2019 11:41:15 GMT

Hi agian.

Sorry that did not work then.

Could you perhaps provide some log from the bootloader? (not nrfutil logs)

Also, if you want, I can make this case private if you don't wish to share that with other then me.

Best regards,

Andreas

RE: NRF52 DFU Serial problem in SDK 15.3

dsasa — Fri, 05 Apr 2019 11:08:05 GMT

Hi Andreas,

I already supposed there is an error in snippet and placed delay inside if statement at line 573. There is no difference, no response to the last execute object command.

RE: NRF52 DFU Serial problem in SDK 15.3

AndreasF — Fri, 05 Apr 2019 07:18:06 GMT

Hi.

I just noticed that I've copied the wrong code snippet, the delay should be added to the if statement, on line 573:

Can you try to place it there?

Best regards,

Andreas

RE: NRF52 DFU Serial problem in SDK 15.3

dsasa — Thu, 04 Apr 2019 13:42:52 GMT

Thank You for answering,

Unfortunately, adding a delay does not solve the problem. Same situation again. I experimented with delay values but with no results. Still no response to the last "execute object" command.

RE: NRF52 DFU Serial problem in SDK 15.3

AndreasF — Thu, 04 Apr 2019 12:22:27 GMT

Hi.

This is unfortunately a known problem that has been looked at, but that solution was left out due to size reasons.

Can you try to implement this workaround, it should work.

In the file components\libraries\bootloader\dfu\nrf_dfu_req_handler.c, add a delay on line 573:

        res.result = NRF_DFU_RES_CODE_SUCCESS;

        /* Provide response to transport */
        p_req->callback.response(&res, p_req->p_context);
        nrf_delay_ms(500); //ADDED A 500 MS DELAY
        if (NRF_DFU_SAVE_PROGRESS_IN_FLASH)
        {
            /* Allowing skipping settings backup to save time and flash wear. */
            ret = nrf_dfu_settings_write_and_backup(NULL);
            UNUSED_RETURN_VALUE(ret);
        }

You also need to use #include "nrf_delay.h" at the top of the file.

You can try various delays, it should work as long as you're delaying less then a second.

Best regards,

Andreas