DFU Zephyr using USB

[MPDeveloper89]

Hello,

In my application I'm using NORA B106 and I would like to update the firmware using USB.

In my device there isn't any FTDI and I want to use the USB layer available in Zephyr.

Can you help me to understand what are the steps to implement the application?

I think that I need to : 

• Enable the usb software module using Kconfig ( I found the following example)
• Install the driver in Windows to recognize the device

Can I use Zadig?

I tried but no Virtual COM has been detected

• Flashing the software using dedicated tool.

Thank you a lot for your support.

MP

[Vidar Berg]

Hello,

Attached below is an example based on the "Hello world" sample that includes MCUBoot configured with serial recovery support over USB ACM if you want to give it a try. You should not need to install any additional USB drivers for this unless you are working on Windows 7 or older. But you will need to install 'MCUmgr', the command line tool to perform the update: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/device_mgmt/mcumgr.html#command-line-tool 

hello_word_w_serial_recovery_nrf53_SDKv2.2.0.zip

Otherwise, if you need to rely on the USB class, you can try the USB DFU Sample Application in Zephyr instead. 

Best regards,

Vidar

[MPDeveloper89]

Hello Vidar,

Thank you for feedback.

I load your example where I added my board:

But, during compilation I found some errors.

In prj.conf

In mcuboot.overlay

Do you know the possible root cause?

Thank.

MP

[MPDeveloper89]

Hello,

Finally, I'm able to build using SDK 2.2.0.

Then, I back on the current task and I build  the example shared to print "Hello World" after flashing.

Based on this consideration, which software should be already uploaded in my device?

Could be  USB CDC ACM Sample Application ?

I suppose that, to perform the software update procedure , my device should be detected.

Are correct my assumptions?

Thank you again.

MP

[Vidar Berg]

Hello,

The USB interface will get enabled when the Bootloader enters the Serial recovery / DFU mode on startup. But you need a way to signal the bootloader to enter DFU mode. Otherwise, it will just proceed to boot the application as normal when you reboot the device.

Do you have a button on your Board you can use to enter DFU mode? If you do, you can assign the button by adding and editing the following Kconfig symbols in child_image/mcuboot.conf:

# Enter DFU mode if P0.23 is pulled low on startup

CONFIG_BOOT_SERIAL_DETECT_PORT="GPIO_0" 

CONFIG_BOOT_SERIAL_DETECT_PIN=23 

CONFIG_BOOT_SERIAL_DETECT_PIN_VAL=0

Here is where the bootloader decides whether to enter serial recovery mode or not:

https://github.com/nrfconnect/sdk-mcuboot/blob/main/boot/zephyr/main.c#L574 

[MPDeveloper89]

Hello Vidar,

Thank you for feedback.

Considering your example

Vidar Berg said:

hello_word_w_serial_recovery_nrf53_SDKv2.2.0.zip

I added configuration suggested and verified pin (in my case P0.08) status at the power on but something is not clear for me.

Probably, I forgot or missed that my device is vergin and based on procedure suggested to update the software: 

Vidar Berg said:

You should not need to install any additional USB drivers for this unless you are working on Windows 7 or older. But you will need to install 'MCUmgr', the command line tool to perform the update: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/device_mgmt/mcumgr.html#command-line-tool 

I think that for my device is mandatory recognize it like a device from windows due to procedure itself:

Then, I suppose that a software should be pre-flashed before the flashing procedure using the MCUboot and a possible example could be:

MPDeveloper89 said:

  USB CDC ACM Sample Applicatio

Are correct my assumptions?

[Vidar Berg]

If you hold the button (P0.08) on startup, the bootloader should enter serial recovery mode and enable the USB interface and make it appear as a VCOM on your PC. Had you tried that?

The USB interface enabled by the serial recovery mode shown in the device manager:

[MPDeveloper89]

Hello Vidar,

I found some trouble with driver installed with Zadig but I solved and finally using your example with a small adjastment for button to enter in DFU mode I can recognize the device in device manager.

Thank you very much.

Then, I created a new project (based on your) where i turned on a led when button is pushed.

Practically I used the same project shared but I updated the main.c file and updated the versioning:

CONFIG_MCUBOOT_IMAGE_VERSION="1.1.0+0"

So, I started the DFU procedure suggested after entering in DFU mode:

The procedure seems work but flash memory is not updated.

Versioning not updated and application not updated. 

At the next power on, led is not turned on.

I used the bin file app_update.bin (means signed variant) where I suppose that creation of public or private keys is not necessary for development phase.

Zephtr should be create them automatically.

Anyway, I tried also to generate them (following this guide) and updating the prj.conf but with negative result.

Do you have some suggestion?

Have I miss something?

Thank you again.

[Vidar Berg]

Hello,

Are you able to upload your project so I can try to have a look at it here? Alternatively, could you test again with the example I uploaded without making any modifications to it (apart from matching the pinout to your board) and see if you get the same problem?

[MPDeveloper89]

Hello,

Yes, sure. Attached the project used and.dts files (they could useful ).

Regarding your example, I cannot verify immediately your example because I don't have any additional usb driver on board to verify the "hello world" printing.

button_w_serial_recovery_nrf53_SDKv2.2.0.zip

ubx_evknorab10_cpuapp_common.zip 

[Vidar Berg]

Hello,

Thanks for uploading your project. It works as expected when I build it for the nrf5340dk_nrf5340_cpuapp board at least: 

Could you try the same to see if the version number gets updated as shown in the screenshot above? The button and LED assigment will not match your board but you can still check if the update succeeds. 

[MPDeveloper89]

Which .bin file are you used (from screenshot is not visible)?

I tried with the app_update.bin file but versioning is not updated.

MPDeveloper89 said:

So, I started the DFU procedure suggested after entering in DFU mode:

The procedure seems work but flash memory is not updated.

Regarding your consideration, please consider that I'm using a custom board based on the same Soc then external peripheral are custom configured.

[Vidar Berg]

I used the app_update.bin that was generated after I bumped the 'CONFIG_MCUBOOT_IMAGE_VERSION' value. 

MPDeveloper89 said:

Regarding your consideration, please consider that I'm using a custom board based on the same Soc then external peripheral are custom configured.

Yes, the reason I asked you to try with the same build target (i.e. nrf5340dk_nrf5340_cpuapp) was to see if it would work if we had the same configuration settings. Anyway. I have built the project again for 'ubx_evknorab10_nrf5340_cpuapp' and included the hex files below. Please test with these and see if you still experience the same problem.

Test

1. Program 5153.GENERATED_CP_APPLICATION_merged_domains.hex and 8880.GENERATED_CP_NETWORK_merged_domains.hex to your board with nrfjprog or the Programmer app in nRF connect for desktop

2. Upload 7713.app_update.bin with mcumgr.

Expected result