Feature request: Please allow APP+BL DFU upgrades in nrfutil

RE: Feature request: Please allow APP+BL DFU upgrades in nrfutil

Hung Bui — Fri, 04 Mar 2022 12:01:15 GMT

Thanks Bruno. Seems to be very simple. The question is if R&D have someone to look into this :) I'm still waiting for their update.

RE: Feature request: Please allow APP+BL DFU upgrades in nrfutil

Bruno Randolf — Tue, 01 Mar 2022 11:46:57 GMT

See github.com/.../371

RE: Feature request: Please allow APP+BL DFU upgrades in nrfutil

Bruno Randolf — Tue, 01 Mar 2022 11:38:59 GMT

In the mean time I have modified pc-nrfutil, and it was easier than expected:

diff --git a/nordicsemi/__main__.py b/nordicsemi/__main__.py
index f9697c1..be2afcb 100755
--- a/nordicsemi/__main__.py
+++ b/nordicsemi/__main__.py
@@ -664,7 +664,7 @@ def generate(zipfile,

* BL + SD: Supported.

- * BL + APP: Not supported (use two packages instead).
+ * BL + APP: Supported.

* BL + SD + APP: Supported.

@@ -672,10 +672,6 @@ def generate(zipfile,
"""
zipfile_path = zipfile

- # Check combinations
- if bootloader is not None and application is not None and softdevice is None:
- raise click.UsageError("Invalid combination: use two .zip packages instead.")
-
if debug_mode is None:
debug_mode = False

diff --git a/nordicsemi/dfu/init_packet_pb.py b/nordicsemi/dfu/init_packet_pb.py
index ad72202..7cc0b82 100644
--- a/nordicsemi/dfu/init_packet_pb.py
+++ b/nordicsemi/dfu/init_packet_pb.py
@@ -132,10 +132,6 @@ class InitPacketPB:
raise RuntimeError("sd_size is not set. It must be set when type is SOFTDEVICE")
elif self.init_command.type == pb.BOOTLOADER and self.init_command.bl_size == 0:
raise RuntimeError("bl_size is not set. It must be set when type is BOOTLOADER")
- elif self.init_command.type == pb.SOFTDEVICE_BOOTLOADER and \
- (self.init_command.sd_size == 0 or self.init_command.bl_size == 0):
- raise RuntimeError("Either sd_size or bl_size is not set. Both must be set when type "
- "is SOFTDEVICE_BOOTLOADER")

if self.init_command.fw_version < 0 or self.init_command.fw_version > 0xffffffff or \
self.init_command.hw_version < 0 or self.init_command.hw_version > 0xffffffff:

```

RE: Feature request: Please allow APP+BL DFU upgrades in nrfutil

Hung Bui — Tue, 22 Feb 2022 08:27:35 GMT

Hi Bruno,

I have reported the request to the team internally. Hope that it would be updated soon.

In the meantime maybe you can just write a script to do the task of editing the .bin and .dat file automatically ?

RE: Feature request: Please allow APP+BL DFU upgrades in nrfutil

Bruno Randolf — Fri, 18 Feb 2022 17:25:51 GMT

Yes, the update is actually done in two phases: first the BL and then the APP, just like with APP+SD+BL updates. Thank you!

RE: Feature request: Please allow APP+BL DFU upgrades in nrfutil

Hung Bui — Fri, 18 Feb 2022 10:05:02 GMT

Hi Bruno,
Thanks for the information.
I just want to clarify here that after you have manipulated and created the .zip file containing APP+BL, when you do DFU update, did it perform in one go or under the hood it's actually 2 phases: The BL got updated first and then nrfutil sends the app after that ? Or both the app and the bootloader were sent at the same time ? (You may need to use a sniffer or use the log on the bootloader to detect that). As far as I know the bootloader doesn't support APP+BL in one image.

But even if it's sent in 2 phases or not, for the end customer it's still transparent, which is important. So I think your information is very useful and the request is legit. I will forward your request to the team.