nRF52832 DK bootloader don't start application

RE: nRF52832 DK bootloader don't start application

Vidar Berg — Fri, 16 Mar 2018 12:34:19 GMT

This is issue appears to be different from the one you initially described? Now it fails at the pre-validate step which performs the signature and version checks. You can single step in the pre-validation code in dfu_req_handling.c do determine exactly why it fails. Did you use the same key set with the debug bootloader, and did you set the debug mode flag when you generated the zip package?

Generating DFU packages

RE: nRF52832 DK bootloader don't start application

Bilal Bouguerra — Thu, 15 Mar 2018 14:07:38 GMT

I can log debug infos:

0> :INFO:Prevalidate FAILED!
0> :INFO:Sending Response: [0x4, 0x5]

RE: nRF52832 DK bootloader don't start application

Vidar Berg — Thu, 15 Mar 2018 13:04:43 GMT

This should work:

RE: nRF52832 DK bootloader don't start application

Bilal Bouguerra — Thu, 15 Mar 2018 13:00:39 GMT

And what configuration do I need to enter in JLinkRTTViewer ?

RE: nRF52832 DK bootloader don't start application

Vidar Berg — Thu, 15 Mar 2018 12:55:46 GMT

RTT is enabled by default in the debug project. You can view RTT logs in JLinkRTTViewer.exe if you are working on Windows.

RE: nRF52832 DK bootloader don't start application

Bilal Bouguerra — Thu, 15 Mar 2018 12:51:48 GMT

I'm not using the debug project but if I do so how do I debug the code execution (RTT configuration, etc...) ?

RE: nRF52832 DK bootloader don't start application

Vidar Berg — Thu, 15 Mar 2018 12:45:19 GMT

Hi,

Are you using the _debug project (\examples\dfu\bootloader_secure\pca10040_debug)? In that case you can check the RTT log output to see if the bootloader reports any errors, maybe the DFU process fails at the post-validation step or during activation.

You could also try to rebuild the bootloader with the nrf_dfu_utils.c file I posted here: https://devzone.nordicsemi.com/f/nordic-q-a/31023/long-delay-after-dfu-completion-sdk-12-1. It should make the copy routine more robust against unexpected resets.

RE: nRF52832 DK bootloader don't start application

Bilal Bouguerra — Thu, 15 Mar 2018 12:28:32 GMT

When I debug the BLE Secure DFU Bootloader, I can see that the execution is stuck in this function:

static void wait_for_event()
{
    // Transport is waiting for event?
    while(true)
    {
        // Can't be emptied like this because of lack of static variables
        app_sched_execute();
    }
}

void app_sched_execute(void)
{
    while (!is_app_sched_paused() && !APP_SCHED_QUEUE_EMPTY())
    {
        // Since this function is only called from the main loop, there is no
        // need for a critical region here, however a special care must be taken
        // regarding update of the queue start index (see the end of the loop).
        uint16_t event_index = m_queue_start_index;

        void * p_event_data;
        uint16_t event_data_size;
        app_sched_event_handler_t event_handler;

        p_event_data = &m_queue_event_data[event_index * m_queue_event_size];
        event_data_size = m_queue_event_headers[event_index].event_data_size;
        event_handler   = m_queue_event_headers[event_index].handler;

        event_handler(p_event_data, event_data_size);

        // Event processed, now it is safe to move the queue start index,
        // so the queue entry occupied by this event can be used to store
        // a next one.
        m_queue_start_index = next_index(m_queue_start_index);
    }
}