Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Thu, 23 Feb 2023 11:41:00 GMT

I didn't change anything in cmakedevzone.nordicsemi.com/.../4456.CMakeLists.txt.

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Shahin97 — Mon, 20 Feb 2023 17:02:43 GMT

I think I have isolated my issue, my light switch and dfu cmake files are different, I'm not entirely sure how to merge them, would I be able to have a look at your cmake file?

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Fri, 17 Feb 2023 17:52:59 GMT

m_evt_handler.evt_cb = mesh_evt_handler;//DFU
nrf_mesh_evt_handler_add(&m_evt_handler);//DFU
added this to the end mesh_init(void)

the rest of the functions you can compare they are the same

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Shahin97 — Thu, 16 Feb 2023 16:59:50 GMT

You've imported the DFU into the Light_switch Example

Did you do any changes to:

mesh_init(void)

initialize(void)

start(void)

or just copy the part of code.txt into the Light_switch Example?

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Wed, 15 Feb 2023 17:16:35 GMT

Yes, it only have the weak implementation of nrf_mesh_dfu_init() from nrf_mesh_weak.c.

I added
<folder Name="DFU">
<file file_name="../../../mesh/dfu/src/nrf_mesh_dfu.c" />
</folder>
the file path to .emProject now everything is working.

Thanks for the help. I hope in the future there will be Wizards app that will set everything up in one click.

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Edvin — Wed, 15 Feb 2023 14:46:04 GMT

Ok, did you include nrf_mesh_dfu.c and nrf_mesh_dfu.h in your project? Or does it only have the weak implementation of nrf_mesh_dfu_init() from nrf_mesh_weak.c?

If you already included the nrf_mesh_dfu.c, try to debug (or add logging) to see where it returns 0x06. Is it on line 692? Or is it one of the other calls inside nrf_mesh_dfu_init() that returns 0x06? Try to compare it to the dfu example to see where it behaves differently.

BR,
Edvin

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Wed, 15 Feb 2023 13:50:16 GMT

nrf_mesh.c, 358, Status nrf_mesh_dfu_init() : 0x6

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Edvin — Wed, 15 Feb 2023 13:29:23 GMT

Ok, what does nrf_mesh_dfu_init() in nrf_mesh.c return, then? What is the value of the parameter "status" after this line:

BR,
Edvin

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Wed, 15 Feb 2023 12:05:42 GMT

00> <t: 0>, main.c, 506, ----- BLE Mesh Light Switch Server Demo -----
00> <t: 8231>, main.c, 475, ---------------Start mesh_stack_init. -----------------
00> <t: 8775>, main.c, 453, Initializing and adding models
00> <t: 8779>, main.c, 307, App OnOff Model Handle: 2
00> <t: 8782>, main.c, 312, App DTT Model Handle: 3
00> <t: 8786>, main.c, 318, App Scene Model Handle: 5
00> <t: 8806>, main.c, 477, Status mesh_stack_init : 0x0000
00> <t: 8809>, main.c, 523, Initialization complete!
00> <t: 13661>, mesh_app_utils.c, 66, Device UUID (raw): 2AD4C6C6D0CF446E876C33B6966911D2
00> <t: 13665>, mesh_app_utils.c, 67, Device UUID : 2AD4C6C6-D0CF-446E-876C-33B6966911D2
00> <t: 13684>, main.c, 557,
00> -------------------------------------------------------------------------------
00> Button/RTT 1) LED state will toggle and inform clients about the state change.
00> Button/RTT 4) Clear all the states to reset the node.
00> -------------------------------------------------------------------------------
00> <t: 14256>, app_onoff.c, 154, msg: SET: 0

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Wed, 15 Feb 2023 10:39:54 GMT

as shown in attached file "part of code.txt" mesh_evt_handler() was completely added by me unchanged to the light_switch example.

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Edvin — Wed, 15 Feb 2023 10:19:59 GMT

[quote user="Sergnrf"]this is what the memory looks like after the first successful update
[/quote]

That looks correct. Just to clarify, the green lines at the top is the flash used for network credentials and stuff like that. This is not erased between DFUs. The green chunk in the middle is the new application. This is where it is stored while transferring. This will be erased and re-written the next time you do a DFU. The bottom green chunk is the current application. It is probably the same as the middle green chunk, since it is copied from there. The blue and orange are the SoftDevice and MBR. The bluetooth stack. This is not updated in an application DFU (only if the image contains a SoftDevice update).

So my guess is that your new application is not set up to handle DFUs. I don't know what your code looks like, but looking at the DFU example I would guess that you need all the events that says something with DFU in your mesh_evt_handler().

Also, does nrf_mesh_dfu_init() get called inside nrf_mesh.c -> nrf_mesh_init(). What does nrf_mesh_dfu_init() return?

Best regards,

Edvin

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Tue, 14 Feb 2023 22:10:17 GMT

when I run the update for the first time, I see the following message in RTT Viewer
5881588>, nrf_mesh_dfu.c, 418, New firmware!
when I run the updates for the second time, there are no messages related to the update

Сan you provide detailed instructions on how to combine your examples?

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Tue, 14 Feb 2023 21:59:49 GMT

this is what the memory looks like after the first successful update

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Edvin — Tue, 14 Feb 2023 12:27:46 GMT

Hello,

[quote user="Sergnrf"]I have a guess that by combining the two examples the total size of the hex file exceeds the amount of available memory for the update.[/quote]

That could be the case. Did you try checking the size of the old and the new application? (you can use nRF Connect for Desktop -> Programmer to see how much space the .hex file will take). Will they both fit in the flash at the same time in addition to the SoftDevice and Bootloader?)

I am not sure whether the LEDs not responding is due to the image not being transferred, or if the LEDs are set up to do other things. They are controlled by the application in the DFU sample. Are they set up the same way in your light_switch application?

You don't strictly need the LEDs to determine whether the DFU is ongoing. You can monitor the DFU related events, and for example write something to the log when they occur. Do any of the DFU related events from the dfu example trigger in your light switch implementation?

Best regards,

Edvin

RE: Mesh DFU not working after 1st successful update. Integrating DFU process into the application.

Sergnrf — Mon, 13 Feb 2023 14:34:50 GMT

I have a guess that by combining the two examples the total size of the hex file exceeds the amount of available memory for the update.
Has anyone been able integrating dfu mesh process to light_switch example? so that it is successfully updated every time?