Problem with DFU over BLE using west and mcuboot

[yayembedded]

I am building with west and then using this tutorial:

https://docs.zephyrproject.org/2.6.0/samples/subsys/usb/dfu/README.html

to create a .bin file.  I then use nrfConnect to do a DFU update.

The original firmware on the board (let's call it version 1) was built with nrfConnectSDK 1.4.1 and Segger Embeded Dtudio on a PC.

I am now building, same code base same prj.conf same board, on an Ubuntu machine and using the latest version of Zephyr and west, then signing manually with mcuboot. Let's call this version 2. Version of the firmware is signed using "root-rsa-2048.pem" file in mcuboot.  

I am able to update the board to from version 1 to version 2, but if I try to update version 2 to another version (same code base same prj.conf same board) I am not able to.  nrfConnect for mobile gives me an error stating that it timed out requesting an update.

[Hung Bui]

Hi Christopher, 

I assume the application version 2 is also based on usb-dfu sample ? And I assume you meant DFU over USB not "DFU over BLE" ?

Have you double check if it's running after the update from version 1 to version 2? I would suggest to blink an LED just to make sure if it's running. 
Also please slightly modify the application in version 2 so that the hex file is not identical. From my experience, mcuboot will ignore the update if the new firmware is identical to the one on one of the slot. 

[yayembedded]

Hi Hung

Both versions are based on subsys/mgmt/mcumgr/smp_svr

I am building with west, on an Ubuntu docker image from Zephyr, but unlike on my local machine building with west does not generate merged.hex and app_update.bin

I learned that running west with and without nrf connect sdk is not the same.  I wonder if I should redo my docker image for nrf connect sdk. 

By the way, it would be very convenient for the whole development community of Nordic released their docker images for everyone to use...avoiding all these build problems and questions on devzone.

[Hung Bui]

Hi Christopher, 

We actually do have a docker image for nRF Connect SDK provided by one of our employee here. It's not official thought. 

There is a different between our nRF Connect SDK and Zephyr vanilla. When you build with NCS you will have the merged.hex and app_update.bin that you don't have to sign the image manually every time you build. I strongly suggest to use NCS.

Please note that we also provide a Toolchain manager tool in nRF Connect for Desktop application that can help you to install the toolchain and the SDK automatically with just one click (WIndows&Mac). 

[yayembedded]

Thanks.  I experience bugs with NRF Desktop and Segger (both on Windows and Mac), so I am moving away from that.  But this exercise is specifically to create a CI/CD pipeline for firmware development so thats why I need to run from the command line.

Thanks for your explanation of NCS, now I know.  However I do have one more question. How do I Know which version of Zephyr is associated with a particular version of NCS?  For example I am using hte latest release NCS 1.5.2, but I can't find the Zephyr version NCS is using

[Hung Bui]

Hi Christopher, 

The latest version of NCS is v1.8.0. 
You can find the information about the zephyr version used here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/releases/release-notes-1.8.0.html#zephyr

You can also run "west list" to list the repo version information. 

We have improved a lot lately with the Toolchain manager tool. I would suggest to give it another try. 

[yayembedded]

Thank you.

For safety, I am using 1.5.2 because on Github that is the latest tagged release.  I thought that would be safer than using the latest.

[Hung Bui]

Hi Christopher, 
AFAIK version 1.5.2 is only a bug fix release for v1.5.1. That's why it's the latest tagged release. It doesn't mean that all version after that are not stable. Version 1.8.0 is the latest, stable and at production level. 
I would suggest to move to v1.8.0