DFU project

RE: DFU project

František — Wed, 19 Feb 2020 06:57:49 GMT

I solved it, thank you.

RE: DFU project

Marjeris Romero — Tue, 18 Feb 2020 15:46:18 GMT

Hi Fran,

I don't see why this should not be possible. Could you send your code to see how you have implemented this so far?

Best regards,

Marjeris

RE: DFU project

František — Fri, 31 Jan 2020 15:38:10 GMT

it possible add to this dfu project coap client too? Now there is only coap server. I try add coap client but I have problems with communication. On the other site I dont get message.

RE: DFU project

Marjeris Romero — Fri, 25 Oct 2019 09:14:48 GMT

Hi Fran,

You should be able to run a debugger on the application itself as with any other project. But looking at the log output it seems that the settings in flash could be corrupted somehow. You can take a look at the memory layout here, the dfu settings (bootloader settings) are stored near the end. You should check your linker file and adjust your RAM and flash settings accordingly.

Best regards,

Marjeris

RE: DFU project

František — Tue, 22 Oct 2019 10:36:02 GMT

After wtite my code DFU wont start. There is log from flashing DFU:

Address not specified. Using ff03::1 (all Thread nodes)
Using connectivity board at serial port: COM12
Flashing connectivity firmware...
Connectivity firmware flashed.
Waiting for NCP to promote to a router...
Thread DFU server is running... Press <Ctrl + D> to stop.

And there is stoped.

There is log from RTT Viewer.

00> 
<00> info> background_dfu: state=DFU_DOWNLOAD_INIT_CMD event=DFU_EVENT_PROCESSING_ERROR
00> 
<00> error> background_dfu: Processing error while downloading init command.
00> 
<00> info> background_dfu: Current DFU Diag version: Oct 22 2019 10:11:58, 0xC808AC73
00> 
<00> info> COAP_DFU: DFU trigger request received
00> 
<00> info> background_dfu: DFU trigger: init (sz=140, crc=2A5AA774) image (sz=363752, crc=F26E4F73)
00> 
<00> info> background_dfu: state=DFU_DOWNLOAD_TRIG event=DFU_EVENT_TRANSFER_COMPLETE
00> 
<00> warning> background_dfu: Installed image CRC is different
00> 
<00> warning> nrf_dfu_settings: Settings write aborted since it tries writing to forbidden settings.
00> 
<00> error> background_dfu: Init commad has changed
00> 
<00> info> background_dfu: Init complete. Unicast Mode.
00> 
<00> info> background_dfu: state=DFU_DOWNLOAD_INIT_CMD event=DFU_EVENT_TRANSFER_CONTINUE
00> 
<00> info> COAP_DFU: Requesting [i] (block:0 mid:25575)
00> 
<00> info> background_dfu: Storing block (b:0 c:0).
00> 
<00> info> background_dfu: state=DFU_DOWNLOAD_INIT_CMD event=DFU_EVENT_TRANSFER_CONTINUE
00> 
<00> info> COAP_DFU: Requesting [i] (block:1 mid:25576)
00> 
<00> info> background_dfu: Storing block (b:1 c:1).
00> 
<00> info> background_dfu: state=DFU_DOWNLOAD_INIT_CMD event=DFU_EVENT_TRANSFER_CONTINUE
00> 
<00> info> COAP_DFU: Requesting [i] (block:2 mid:25577)
00> 
<00> info> background_dfu: Storing block (b:2 c:2).
00> 
<00> info> nrf_dfu_validation: Signature required. Checking signature.
00> 
<00> info> nrf_dfu_validation: Calculating hash (len: 63)
00> 
<00> info> nrf_dfu_validation: Verify signature
00> 
<00> info> nrf_dfu_validation: Image verified
00> 
<00> warning> nrf_dfu_settings: Settings write aborted since it tries writing to forbidden settings.
00> 
<00> info> background_dfu: state=DFU_DOWNLOAD_INIT_CMD event=DFU_EVENT_PROCESSING_ERROR
00> 
<00> error> background_dfu: Processing error while downloading init command.
00> 
<00> info> background_dfu: Current DFU Diag version: Oct 22 2019 10:11:58, 0xC808AC73
00>

RE: DFU project

František — Tue, 15 Oct 2019 08:01:43 GMT

Is exist any option how to debug dfu client project?

RE: DFU project

František — Fri, 11 Oct 2019 13:25:53 GMT

Thank you, it works.

RE: DFU project

Marjeris Romero — Wed, 09 Oct 2019 11:48:35 GMT

Hi Fran,

Sorry for the late answer here, I was on vacation. I have taken a closer look at the thread coap dfu example and the iot coap library. The coap dfu example already runs a coap server along coap client and the resources are registered in the endpoints_init function in coap_dfu.c.

Using the 'coap_resource_create' and 'coap_resource_child_add' APIs it should be possible to register custom resources. The endpoints_init function in coap_dfu.c can be extended to add the extra resources you need.

From what I see in your code you were on the right track but I think you forgot to call 'coap_resource_child_add'.

Keep in mind that usually one wants to avoid modifying the nordic libraries in the SDK, so directly modifying coap_dfu.c isn't the best approach... but since we can only have one instance of CoAP with IoT CoAP implementation we need to share some resources (i.e. the resource root), so what you could do is to add a function to the CoAP DFU API (coap_dfu.c) allowing to optain a pointer to the root resource of the current CoAP instance. This will allow you to add resources directly from your main application, minimizing CoAP DFU interference and keeping the design as neat as possible.

To help you on the way I have modified the coap_dfu example to include a light resource so I can test the coap dfu example using the simple_coap_client example commands for on/off (BSP_BUTTON_1). I used the iot coap server example in nRF5_SDK/examples/iot/coap/ipv6/server as a reference.

(Note: I didn't implement pairing and toggle, which are also included in the original simple coap server/client example, so my example only supports messages send by BSP_BUTTON_1 on the simple coap client(light cmd on/off), nothing will happen when pressing BPS_BUTTON_0 or BPS_BUTTON_2).

In coap_dfu.c add the following function:

coap_resource_t * get_resources_root(void){
	return &(m_coap_dfu_ctx.root); 
}

And also add it in coap_dfu.h:

coap_resource_t * get_resources_root(void);

Then in main.c you can add any number of resources after coap_dfu_init have been called, and add them to the root resource using the function above. See the attached main.c file:

devzone.nordicsemi.com/.../main.c

You can then test the application using simple_coap_client to toggle LED4 on and off, and change LED 2 on/off when performing DFU with another board.

Best regards,

Marjeris

RE: DFU project

František — Fri, 27 Sep 2019 09:57:57 GMT

now it write this output:

Traceback (most recent call last):
File "C:\Python27\lib\site-packages\nrfutil-4.0.0-py2.7.egg\nordicsemi\thread\tncp.py", line 130, in _wpan_receive
receiver.receive(payload, src, dst)
File "build\bdist.win-amd64\egg\piccata\core.py", line 541, in receive
self._message_layer.receive(data, remote, local)
File "build\bdist.win-amd64\egg\piccata\core.py", line 206, in receive
self._transaction_layer.receive_message(message, remote, local)
File "build\bdist.win-amd64\egg\piccata\core.py", line 428, in receive_message
self._process_response(message)
File "build\bdist.win-amd64\egg\piccata\core.py", line 359, in _process_response
self._finish_transaction(response.token, remote, RESULT_SUCCESS, response)
File "build\bdist.win-amd64\egg\piccata\core.py", line 305, in _finish_transaction
self._handle_app_callback(callback, result, request, response)
File "build\bdist.win-amd64\egg\piccata\core.py", line 274, in _handle_app_callback
cb(result, request, response, *args, **kw)
File "C:\Python27\lib\site-packages\nrfutil-4.0.0-py2.7.egg\nordicsemi\thread\dfu_server.py", line 217, in _handle_trigger_response
assert (result == piccata.constants.RESULT_TIMEOUT)
AssertionError

RE: DFU project

Marjeris Romero — Thu, 26 Sep 2019 13:35:17 GMT

Hi Fran,

I am so sorry but I am going out on vacation so I will not be able to review your code before the 7th of October. Sorry for the inconvenience and thanks for your patience.

Best regards,

Marjeris

RE: DFU project

František — Tue, 24 Sep 2019 13:45:35 GMT

I use nRF5_SDK_for_Thread_and_Zigbee_v3.2.0_9fade31

I try example to DFU thread client and I add turn on LED. DFU was sucessfull. Next I add CoAP resources to code and it not start.

This is terminal output:

D:\IS\nRF5_SDK_for_Thread_and_Zigbee_v3.2.0_9fade31\examples\thread\dfu>nrfutil dfu thread -f -pkg app_dfu_package.zip -p COM12 --channel 11 --panid 43981
Address not specified. Using ff03::1 (all Thread nodes)
Using connectivity board at serial port: COM12
Flashing connectivity firmware...
Connectivity firmware flashed.
Waiting for NCP to promote to a router...
Thread DFU server is running... Press <Ctrl + D> to stop.

edited file: coap_dfu.c

added code:

#define MY_APP_RESOURCE_HELLO "hello"
coap_resource_t coap_resource_hello;

#define MY_APP_RESOURCE_READ "read"
coap_resource_t coap_resource_read;

#define MY_APP_RESOURCE_WRITE "write"
coap_resource_t coap_resource_write;

static void hello_request_callback(coap_resource_t * p_resource, coap_message_t * p_request)
{
NRF_LOG_INFO("Hello packet");

coap_message_t * p_response = NULL;

if (!is_addr_multicast(&p_request->local))
{
p_response = empty_reset_response_create(p_request);
}

// Send response, if created.
if (p_response != NULL)
{
coap_dfu_message_send(p_response);
}

}

static void read_request_callback(coap_resource_t * p_resource, coap_message_t * p_request)
{
NRF_LOG_INFO("Read packet");

coap_message_t * p_response = NULL;

if (!is_addr_multicast(&p_request->local))
{
p_response = empty_reset_response_create(p_request);
}

// Send response, if created.
if (p_response != NULL)
{
coap_dfu_message_send(p_response);
}

}

static void write_request_callback(coap_resource_t * p_resource, coap_message_t * p_request)
{
NRF_LOG_INFO("Write packet");

coap_message_t * p_response = NULL;

if (!is_addr_multicast(&p_request->local))
{
p_response = empty_reset_response_create(p_request);
}

// Send response, if created.
if (p_response != NULL)
{
coap_dfu_message_send(p_response);
}

}


static uint32_t MyAppCoapResource_init()
{
    uint32_t err_code = NRF_SUCCESS;
    
    do
    {
        err_code = coap_resource_create(&coap_resource_hello, MY_APP_RESOURCE_HELLO);
        err_code = coap_resource_create(&coap_resource_read, MY_APP_RESOURCE_READ);
        err_code = coap_resource_create(&coap_resource_write, MY_APP_RESOURCE_WRITE);
        if (err_code != NRF_SUCCESS)
        {
            break;
        }

        coap_resource_hello.permission = (COAP_PERM_POST | COAP_PERM_GET);
        coap_resource_hello.callback = hello_request_callback;

        coap_resource_read.permission = (COAP_PERM_POST | COAP_PERM_GET);
        coap_resource_read.callback = read_request_callback;

        coap_resource_write.permission = (COAP_PERM_POST | COAP_PERM_GET);
        coap_resource_write.callback = write_request_callback;

        NRF_LOG_INFO("Endpoints initialized");

    } while (0);

    return err_code;
}

//upgrade this existing function

uint32_t coap_dfu_init(const void * p_context)
{
    uint32_t err_code;

    do
    {
        memset(&m_coap_dfu_ctx, 0 , sizeof(m_coap_dfu_ctx));

        err_code = coap_protocol_init(p_context);
        if (err_code != NRF_SUCCESS)
        {
            break;
        }

        err_code = MyAppCoapResource_init();
        if (err_code != NRF_SUCCESS)
        {
            break;
        }

        err_code = endpoints_init(&m_coap_dfu_ctx);
        if (err_code != NRF_SUCCESS)
        {
            break;
        }

        nrf_dfu_settings_init(false);
        nrf_dfu_req_handler_init(dfu_observer);

        background_dfu_state_init(&m_dfu_ctx);

        app_timer_create(&m_send_timer, APP_TIMER_MODE_SINGLE_SHOT, delayed_send_handler);
        app_timer_create(&m_reset_timer, APP_TIMER_MODE_SINGLE_SHOT, delayed_reset_handler);
        app_timer_create(&m_coap_delayed_error_handling_timer, APP_TIMER_MODE_SINGLE_SHOT, coap_delayed_error_handler);

        APP_SCHED_INIT(SCHED_EVENT_DATA_SIZE, SCHED_QUEUE_SIZE);
    } while (0);

    return err_code;
}

RE: DFU project

Marjeris Romero — Thu, 05 Sep 2019 07:53:45 GMT

Hi Fran,

That's the buildt-in OpenThread coap library, the external coap library (the one used by the thread DFU client) is this one: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.iotsdk.v0.9.0%2Flib_iot_coap.html

RE: DFU project

František — Wed, 04 Sep 2019 12:03:25 GMT

If I understand it, I should use coap library which is used in DFU project?

RE: DFU project

František — Wed, 04 Sep 2019 09:02:47 GMT

We wanna use it for thousands devices an update firmware without DFU will not possible.

RE: DFU project

František — Wed, 04 Sep 2019 08:23:06 GMT

This is coap library which is best to use?

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v3.1.0%2Fgroup__api-coap-group.html&cp=5_3_5_0_0_6_3

RE: DFU project

František — Wed, 04 Sep 2019 07:57:23 GMT

And what is external coap library?

RE: DFU project

Marjeris Romero — Mon, 02 Sep 2019 15:43:36 GMT

Hi Fran,

Such an approach will have two CoAP implementations running at the same time which is not a good practice, it would be better to have a single one handling all communications, have a single port for all CoAP traffic and then based on the resource URI handle messages properly.

RE: DFU project

František — Mon, 02 Sep 2019 08:51:23 GMT

And if I use another port for coap server it will be ok?

RE: DFU project

Marjeris Romero — Wed, 28 Aug 2019 15:26:35 GMT

Hi Frantisek,

Sorry for the late reply. I have discuss the issue with a collegue of mine working in the Thread team. We don't think these two examples can run in parallel.

What is happening now is that enabling the built-in CoAP (from the OpenThread library) results in it getting all CoAP traffic, so the DFU packets are not handled by the second CoAP implementation, since the built-in CoAP binds to a specific port, so both DFU_UDP_PORT and OT_DEFAULT_COAP_PORT are defined as the same port.

#define OT_DEFAULT_COAP_PORT 5683 ///< Default CoAP port, as specified in RFC 7252

The OpenThread built-in CoAP is much simpler an limited than the external used in the DFU, therefore our recommendation is not enabling the OT CoAP, and rather build your server application using the external CoAP.

When using the external CoAP library you can create a separate resource with coap_resource_create(), it takes a callback and a resource name, which is the URI path. The examples in nRF5_SDK/examples/iot/coap/ipv6/client and server could be used as a reference.

Best regards,

Marjeris

RE: DFU project

František — Tue, 13 Aug 2019 08:36:57 GMT

Thanks! I am looking forward to your reply.

RE: DFU project

Marjeris Romero — Mon, 05 Aug 2019 18:15:41 GMT

Hi Frantisek,

Sorry for the delay with this case but I will need to consult with our Thread developers to see how to best implement this functionality. The Thread DFU client example is using another CoAP library (from the IoT SDK) and I am not sure what is the best way to merge these two examples.

The project works fine when thread_coap_init() is not called so my guess is that something is being initialized twice or in the wrong way when using the two coap libraries simultaneously.

For reference:

CoAP library used in Thread DFU coap client: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v3.1.0%2Fgroup__api-coap-group.html&cp=5_3_5_0_0_6_3

CoAP library used in simple_coap_server example: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.iotsdk.v0.9.0%2Flib_iot_coap.html

I will update you when I have more information.

Best regards,

Marjeris

RE: DFU project

František — Tue, 30 Jul 2019 14:58:31 GMT

i thning i edit any files out of directory. please use this sdk https://drive.google.com/open?id=1AuShaHKZaZVPQ6bmCRN7kgRvGazwLOfD

RE: DFU project

Marjeris Romero — Tue, 30 Jul 2019 12:00:15 GMT

Could you check that you have attached all the files needed to build the project? I am not able to build dfu_client_coap_server using Makefile located under dfu_client_coap_server/pca10056/blank/armgcc/

RE: DFU project

František — Tue, 30 Jul 2019 10:40:07 GMT

I used nRF5_SDK_for_Thread_and_Zigbee_v3.1.0. this project which I send is from directory SDK/exapmles/thread . You may use armgcc makefile

RE: DFU project

Marjeris Romero — Tue, 30 Jul 2019 10:31:34 GMT

Hi Frantisek,

Which version of the Thread & Zigbee SDK did you use to run the project? And in which path did you place your project folder? I am having some troubles building dfu_client_coap_server with the Makefile provided.