Questions of DFU over BLE example

Dear all

I following the example here , over the air one, and get it basically working, thanks for the tutorial.

Now I have a few questions:

1. It looks like it always keep 2 images at Slot 0 and slot 1, one active at a time, after I Uploaded successfully, It running with new updated image, however when I go to BASIC menu on the the Device Manger Mobile app, and hit SEND RESET COMMAND , it back to previous image, I wonder why and is there a reliable way  to choose which slot it runs?

2.  I am thinking of use it for production, and I got a warning message like below:

CMake Warning at D:\WORK\ncs\v1.9.1\nrf\modules\mcuboot\CMakeLists.txt:262 (message):

---------------------------------------------------------
--- WARNING: Using default MCUBoot key, it should not ---
--- be used for production. ---
---------------------------------------------------------

I wonder what more procedures are needed to make it suitable for production use. 

3. Also the option for CONFIG_MCUMGR_SMP_BT_AUTHEN, if I choose y for it, what is the rest of procedure ? do I still choose app_update.bin for upgrade?

Regard

Thank you!

Ping

Parents Reply
  • Hi, Vidar

    Thank you for your help - I tried to do a clean build and it shows which key file is used only with a clean build. BTW - I have to do a clean build by remove the build and add again as I don't see the pristine option in VS code ACTIONS window now since a upgrade.

    Then I factory programmed the image.hex into the board, and also tried to load a update file with default key. It updated successfully, but it doesn't run and log says "E: Image in the secondary slot is not valid!"

    I suppose this is expected. It works if I upload a new build file with same key file.

    So the procedure for future production is like what I just did? and keep the key file safe? If anyone uploaded another file, it won't work.

    Regards!

    Ping

Children
Related