Bug in nRF Mesh Bootloader?

RE: Bug in nRF Mesh Bootloader?

Hung Bui — Fri, 20 Sep 2019 08:12:26 GMT

@Thomas: This is indeed a bug in the bootloader. I have reported to the team. The fix is as you suggested we should use (1ULL<<offset)

@Geom: Maybe your issue is not related to this Could you please create a new case ?

RE: Bug in nRF Mesh Bootloader?

Geom — Thu, 19 Sep 2019 16:19:07 GMT

I believe, my issue is little bit different.

Target device receives segment 0 (DFU Start) and segments 2..64 (DFU Data) successfully.
But it always can't receive segment 1.
Sometimes it can't receive more than one segment at the very beginning.

Transfer stops on segment 64 because of segment 1 wasn't received.

Now I can build bootloader, and I am still working on code around segment 1 issue.

RE: Bug in nRF Mesh Bootloader?

Geom — Thu, 19 Sep 2019 07:18:39 GMT

Thank you for this post and proposal of the fix.
I will try to apply your recommendation today and then give you to know about results.

I need to learn how to build bootloader now.

RE: Bug in nRF Mesh Bootloader?

Thomas-Brilliant — Wed, 18 Sep 2019 19:15:59 GMT

Did you make any changes to your bootloader? This line should make sure that all new packets aren't marked as missing github.com/.../dfu_transfer_mesh.c

RE: Bug in nRF Mesh Bootloader?

Thomas-Brilliant — Wed, 18 Sep 2019 19:14:43 GMT

As an update, I made the change in my bootloader and now it's able to correctly acknowledge missing packets that are behind by 32 segments or more. I believe the fix works as expected and I haven't noticed any side effects.

RE: Bug in nRF Mesh Bootloader?

Geom — Wed, 18 Sep 2019 17:01:47 GMT

I have similar issue with 64th DFU segment
But PACKET_LOSS occurs each time in the same place
Log snippet is added below

00:02:31 nrf_mesh_dfu.c:325 Write complete (0x8C3D0, 16)
00:02:31 nrf_mesh_dfu.c:335 Flash idle
00:02:33 nrf_mesh_dfu.c:457 RADIO RX! Segment 63 of 8362
00:02:33 nrf_mesh_dfu.c:532 RADIO TX! SLOT 5, count 3, interval: exponential, handle: FFFC
00:02:33 nrf_mesh_dfu.c:325 Write complete (0x8C3E0, 16)
00:02:33 nrf_mesh_dfu.c:335 Flash idle
00:02:35 nrf_mesh_dfu.c:457 RADIO RX! Segment 64 of 8362
00:02:35 nrf_mesh_dfu.c:532 RADIO TX! SLOT 6, count 3, interval: exponential, handle: FFFC
00:02:35 nrf_mesh_dfu.c:325 Write complete (0x8C3F0, 16)
00:02:35 nrf_mesh_dfu.c:335 Flash idle
00:02:37 nrf_mesh_dfu.c:385 Abort event. Reason: 0x3
00:02:37 sf_dfu.c:132 DFU event, type: 10
00:02:37 sf_dfu.c:180 DFU: Firmware downloading is finished, Role: TARGET, Reason: ERR_PACKET_LOSS
00:03:00 sf_utils.c:91 Uptime: 00:03:00
00:04:00 sf_utils.c:91 Uptime: 00:04:00

RE: Bug in nRF Mesh Bootloader?

Mark Q — Mon, 16 Sep 2019 19:01:35 GMT

This is the line Thomas is referring to:
https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/08c60f6d8766bdb83bb108ec3fbd24d758689235/mesh/bootloader/src/dfu_transfer_mesh.c#L199