Lifght switch client example with DFU issue

RE: Lifght switch client example with DFU issue

Edvin — Mon, 06 Jan 2020 14:11:13 GMT

Have you called nrf_mesh_dfu_init()? nrf_mesh_dfu_enable() will return NRF_ERROR_NOT_SUPPORTED if m_cmd_handler == NULL. Is that the case?

RE: Lifght switch client example with DFU issue

UdjinPr — Sun, 22 Dec 2019 20:08:08 GMT

and nrf_mesh_dfu_enable() return NRF_ERROR_NOT_SUPPORTED

RE: Lifght switch client example with DFU issue

UdjinPr — Sat, 21 Dec 2019 20:42:01 GMT

I have tried to do it with mesh 4.0. Result the same - no events.

[quote userid="26071" url="~/f/nordic-q-a/55722/lifght-switch-client-example-with-dfu-issue/226296"][/quote]

nrfutil --verbose dfu serial -pkg dfu_test.zip -p <COM port> -b 115200 -fc --mesh

Please copy all the text from your cmd window after using this command

E:\Nordic\nrf5SDKforMeshv310src>nrfutil --verbose dfu serial -pkg dtest.zip -p COM3 -b 115200 -fc --mesh
Upgrading target on COM3 with DFU package E:\Nordic\nrf5SDKforMeshv310src\dtest.zip. Flow control is enabled.
Flushing com-port...
Opened com-port
Starting DFU upgrade of type 4, SoftDevice size: 0, bootloader size: 0, application size: 2468
Sending DFU start packet, afterwards we wait for the flash on target to be initialized before continuing.
PC -> target: 0502aabbccdd
target -> PC: 0582aabbccdd
Got echo response
Sending DFU init packet
PC -> target: 1378fdff040fb0d4b7c859000000010002000000
target -> PC: 16a6045900000001000200000059000000010001000000
target -> PC: 03847800
PC -> target: 1378fdff040fb0d4b7c859000000010002000000
target -> PC: 03847800
PC -> target: 1478fcff0000b0d4b7c8ffffffff6902000040000c
target -> PC: 0da2010459000000010002000000
target -> PC: 03847800
Sending firmware file
[------------------------------------] 1% 00:11:50PC -> target: 1978fcff0100b0d4b7c800fd0020456802006d6802006f680200
target -> PC: 03847800
PC -> target: 1978fcff0200b0d4b7c871680200736802007568020000000000
target -> PC: 03847800
[------------------------------------] 2% 00:11:41PC -> target: 1978fcff0300b0d4b7c800000000000000000000000077680200
target -> PC: 03847800
PC -> target: 1978fcff0400b0d4b7c879680200000000007b6802007d680200
target -> PC: 03847800
[#-----------------------------------] 3% 00:07:45PC -> target: 1978fcff0500b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
PC -> target: 1978fcff0600b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
[#-----------------------------------] 4% 00:06:11PC -> target: 1978fcff0700b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
PC -> target: 1978fcff0800b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
[##----------------------------------] 6% 00:05:16PC -> target: 1978fcff0900b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
PC -> target: 1978fcff0a00b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
[##----------------------------------] 7% 00:04:39PC -> target: 1978fcff0b00b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
PC -> target: 1978fcff0c00b0d4b7c87f6802007f6802000000000000000000
target -> PC: 03847800
[###---------------------------------] 8% 00:04:12PC -> target: 1978fcff0d00b0d4b7c87f6802007f6802007f6802007f680200
target -> PC: 03847800
PC -> target: 1978fcff0e00b0d4b7c87f6802007f6802007f68020000000000
target -> PC: 03847800
[###---------------------------------] 9% 00:03:51PC -> target: 1978fcff0f00b0d4b7c800000000000000000000000000000000

RE: Lifght switch client example with DFU issue

Edvin — Thu, 19 Dec 2019 08:44:11 GMT

Are you using nrfutil with this device directly, since you have NRF_MESH_SERIAL_ENABLE = 1? If not, can you please try?

What is the output from your nrfutil command? Can you please try to use the command with more verbose output:

nrfutil --verbose dfu serial -pkg dfu_test.zip -p <COM port> -b 115200 -fc --mesh

Please copy all the text from your cmd window after using this command

RE: Lifght switch client example with DFU issue

UdjinPr — Wed, 18 Dec 2019 13:51:29 GMT

[quote userid="26071" url="~/f/nordic-q-a/55722/lifght-switch-client-example-with-dfu-issue/226108"]But then you basically have the same project as the DFU, except that you don't have the same project settings as in the DFU project. Is your plan to add the light switch client afterwards?[/quote]

I did it because i couldn't adjust light switch example to work in DFU mode and at the very last just had replaced main.c.

[quote userid="26071" url="~/f/nordic-q-a/55722/lifght-switch-client-example-with-dfu-issue/226108"]Have you tried to do any debugging? Did you receive any of the DFU events?[/quote]

I am debugging via RTT and yes there are no events.

RE: Lifght switch client example with DFU issue

Edvin — Wed, 18 Dec 2019 10:49:32 GMT

But then you basically have the same project as the DFU, except that you don't have the same project settings as in the DFU project. Is your plan to add the light switch client afterwards?

Have you tried to do some debugging? Can you explain what you mean by "DFU doesn't work"?

Have you tried to do any debugging? Did you receive any of the DFU events?

BR,

Edvin

RE: Lifght switch client example with DFU issue

UdjinPr — Wed, 18 Dec 2019 09:30:31 GMT

Yes I have, I thought in this case it must work.

RE: Lifght switch client example with DFU issue

Edvin — Wed, 18 Dec 2019 08:20:24 GMT

Have you just replaced the main.c in the light_switch\client example with the main.c file from the dfu example?

RE: Lifght switch client example with DFU issue

UdjinPr — Tue, 17 Dec 2019 21:17:17 GMT

Hello, Thank you for your reply. As i sad before I copied main.c from dfu exampel and replaced it main.c in ls example.

[quote userid="26071" url="~/f/nordic-q-a/55722/lifght-switch-client-example-with-dfu-issue/225969"]Also, I suggest that to get thing up and running, you should use the default DFU example with NRF_MESH_SERIAL_ENABLE = 1 to broadcast the DFU images.[/quote]

Yes, It is enaeble.

[quote userid="26071" url="~/f/nordic-q-a/55722/lifght-switch-client-example-with-dfu-issue/225969"]So in your light switch clients, you need the bootloader, that you use when you test the default DFU examples, which you can find in:[/quote]

I use bootloader and a device page as in the dfu example.

[quote userid="26071" url="~/f/nordic-q-a/55722/lifght-switch-client-example-with-dfu-issue/225969"][/quote]

hen, you make sure that inside main() -> initialize() -> mesh_init() -> nrf_mesh_evt_handler_add(&m_evt_handler);

with m_evt_handler.mesh_evt_handler;

I have nrf_mesh_evt_handler_add() in main.c becouse of i use main.c from dfu example.

[quote userid="26071" url="~/f/nordic-q-a/55722/lifght-switch-client-example-with-dfu-issue/225969"][/quote]

Also, make sure that nrf_mesh_dfu_enable() is called, like it is in the dfu example:

main() -> start() -> mesh_stack_start() -> nrf_mesh_enable() -> nrf_mesh_dfu_enable()

I double checked, it is called.

and about HOST. I suppose it is difined, but i couldn't finde place where.

RE: Lifght switch client example with DFU issue

Edvin — Tue, 17 Dec 2019 17:29:14 GMT

Hello,

Did you add the mesh event callback for the DFU events in your light switch clients?

static void mesh_evt_handler(const nrf_mesh_evt_t* p_evt)
{
    switch (p_evt->type)
    {
        case NRF_MESH_EVT_DFU_FIRMWARE_OUTDATED:
        case NRF_MESH_EVT_DFU_FIRMWARE_OUTDATED_NO_AUTH:
            if (fw_updated_event_is_for_me(&p_evt->params.dfu))
            {
                ERROR_CHECK(nrf_mesh_dfu_request(p_evt->params.dfu.fw_outdated.transfer.dfu_type,
                                                 &p_evt->params.dfu.fw_outdated.transfer.id,
                                                 (uint32_t*) bank_addr));
                hal_led_mask_set(LEDS_MASK, false); /* Turn off all LEDs */
            }
            else
            {
                ERROR_CHECK(nrf_mesh_dfu_relay(p_evt->params.dfu.fw_outdated.transfer.dfu_type,
                                               &p_evt->params.dfu.fw_outdated.transfer.id));
            }
            break;

        case NRF_MESH_EVT_DFU_START:
            hal_led_mask_set(BSP_LED_0_MASK | BSP_LED_2_MASK, true);
            break;

        case NRF_MESH_EVT_DFU_END:
            hal_led_mask_set(LEDS_MASK, false); /* Turn off all LEDs */
            hal_led_mask_set(BSP_LED_0_MASK | BSP_LED_1_MASK, true); /* Yellow */
            break;

        case NRF_MESH_EVT_DFU_BANK_AVAILABLE:
            hal_led_mask_set(LEDS_MASK, false); /* Turn off all LEDs */
            ERROR_CHECK(nrf_mesh_dfu_bank_flash(p_evt->params.dfu.bank.transfer.dfu_type));
            break;

        default:
            break;

    }
}

Also, I suggest that to get thing up and running, you should use the default DFU example with NRF_MESH_SERIAL_ENABLE = 1 to broadcast the DFU images.

So in your light switch clients, you need the bootloader, that you use when you test the default DFU examples, which you can find in:

SDK\bin\bootloader\gccarmemb\mesh_bootloader_gccarmemb_nrf52832_xxAA.hex

Then, you make sure that inside main() -> initialize() -> mesh_init() -> nrf_mesh_evt_handler_add(&m_evt_handler);

with m_evt_handler.mesh_evt_handler;

and mesh_evt_handler() is the one that I pasted in the snippet above.

Also, make sure that nrf_mesh_dfu_enable() is called, like it is in the dfu example:

main() -> start() -> mesh_stack_start() -> nrf_mesh_enable() -> nrf_mesh_dfu_enable()

Is "HOST" Defined in your light_switch client project?

Best regards,

Edvin

RE: Lifght switch client example with DFU issue

UdjinPr — Tue, 17 Dec 2019 09:47:12 GMT

and some important details: on master node(board which is used for transmission) is used original dfu example, and on the slave board I off serial driver, becouse it clashes with saadc.