How to do USB DFU for nRF7002DK

RE: How to do USB DFU for nRF7002DK

Vidar Berg — Fri, 21 Feb 2025 08:31:54 GMT

Hello,

Image 1 is for the netcore, see Assigned image numbers.

[quote user="Yoshihiro Goto"]Why does mcumgr's image list command not show image number 1?[/quote]

The primary "flash" partition for the network core image is only emulated in RAM in MCUBoot is running and is not accessible when the application is running.

Image number is passed to the mcumgr cli with the -n/--image argument:

RE: How to do USB DFU for nRF7002DK

Yoshihiro Goto — Fri, 21 Feb 2025 00:08:44 GMT

Hello,

I have additional question.
I use sysbuild and not multi image build, what is image 1?

RE: How to do USB DFU for nRF7002DK

Yoshihiro Goto — Thu, 20 Feb 2025 08:20:40 GMT

Why does mcumgr's image list command not show image number 1?

RE: How to do USB DFU for nRF7002DK

Yoshihiro Goto — Thu, 20 Feb 2025 08:15:49 GMT

Hello Vidar,

>Notice that the image number is 1

Great!
Finally I have succeeded in DFU with my multi-core CPU!

I have some additional question.
- Multi-core CPUs need to perform as many uploads as there are cores in the USB DFU. Is that correct?
- Then what is dfu_multi_image.bin used for?
- I think AuTerm is a wrapper for mcumgr, how do I specify the image number in mcumgr?

Best Regards,
Yoshihiro Goto

RE: How to do USB DFU for nRF7002DK

Vidar Berg — Thu, 20 Feb 2025 06:41:59 GMT

Hello,

I tried the dfu_usb_ext.zip project and was able to update the hci_ipc FW on the network core. Notice that the image number is 1 (Assigned image numbers).

Best regards,

Vidar

RE: How to do USB DFU for nRF7002DK

Yoshihiro Goto — Wed, 19 Feb 2025 09:02:10 GMT

Hello Vidar,

Both projects are almost identical in content, so you can choose any.

----- Repeated -----

I have created two sample projects. Mostly copied from DevAcademy samples, and I have also added some configuration to enable nRF700x.

These are a slight difference to execute DFU.
- Using extended advertising.
- VERSION number is 2.
- LED blinking cycle slowed down.

RE: How to do USB DFU for nRF7002DK

Vidar Berg — Wed, 19 Feb 2025 08:46:04 GMT

I can have have a look at the project you uploaded, but which one of them should I be looking at, dfu_usb_ext.zip or dfu_usb.zip?

RE: How to do USB DFU for nRF7002DK

Yoshihiro Goto — Wed, 19 Feb 2025 01:55:17 GMT

Sorry for not replying for long time.

I did not try your sample project at the time which I received above reply. Because I didn't know about sysbuild.

I was learning about sysbuild during the period. The DevAcademy lessons were also updated Just recently.
By the way, This thread is about USB DFU, may I talk about USB DFU again?
I want to update the network core with USB DFU because our recent project uses BLE scanner mode, not advertising.

devzone.nordicsemi.com/.../dfu_5F00_usb.zip devzone.nordicsemi.com/.../dfu_5F00_usb_5F00_ext.zip

I have created two sample projects. Mostly copied from DevAcademy samples, and I have also added some configuration to enable nRF700x.

These are a slight difference to execute DFU.
- Using extended advertising.
- VERSION number is 2.
- LED blinking cycle slowed down.

I tried to execute DFU from AuTerm following the DevAcademy, but AuTerm displayed 'MCUboot header was not found.'

I thought
SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_MCUBOOT=y
might be needed, didn't work for the reason of dependency.

Extra information, the DFU works properly when I use zephyr.signed.bin(App core).
Needless to say, but the network core was not updated with DFU. So the firmware will cause the fail with extended advertising at next startup.

I was trying a lot of configuration, my conclusion is that the network core cannot be updated with the USB DFU. Is that correct?

RE: How to do USB DFU for nRF7002DK

Vidar Berg — Mon, 30 Sep 2024 09:15:49 GMT

Hello,

Please try the sample attached below if the goal is to support FOTA over BLE. It is based on the peripheral_lbs sample in SDK v2.7.0 and is configured for sysbuild.

Demo sample

devzone.nordicsemi.com/.../peripheral_5F00_lbs_5F00_ble_5F00_fota.zip

The DFU package which contain the app and netcore FW will be placed in the build folder and is called dfu_application.zip. The update can be performed via the Device Manager app on Android or iOS. Just remember to bump the version number in the VERSION file between updates.

Best regards,

Vidar