• State Not Answered
  • Replies 18 replies
  • Subscribers 74 subscribers
  • Views 1907 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 321056
Options

Questions about SDFU implentation and security

i_4556

Hello and thanks for reading,

We are developing for the NRF5340 and one of the features we are very excited about is the OTA firmware updates via the SDFU.

I have followed the instructions here :  Add DFU support to your application and things seem to be working in that the correct services appear when I then look using the NRF app.

I have not yet been able to fully test DFU, because every time I try the app crashes to the homescreen. This is unfortunate; it looks to me like a problem with the mobile app, hopefully it gets fixed soon.

In the meantime, I have two questions about SDFU.

Firstly, does the bootloader perform a full chip erase when new firmware is loaded? Like if I use the DFU to upload a new firmware that is substantially smaller in size, is there a bunch of old code in flash waiting to be stolen?

Secondly, is there any way to tell the NRF to only accept firmware images that are signed or otherwise authenticated? I assume there must be, could you provide me a link to a guide or example or something of how to implement that?

Thank you very much!

Parents Reply
  • 0 in reply to Amanda Hsieh

    Thank you for your reply. I am using an Iphone 12 running IOS 16.6. I am using the NRF connect app on the phone. I am using SDK 2.5.0, and per the example simply added

    CONFIG_BOOTLOADER_MCUBOOT=y
    CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

    to my proj.config file for my existing codebase.

    If the firmware just swaps the images, what is to stop a malicious actor uploading firmware that then dumps the old code out the serial port or otherwise bypasses readback protections? I assume the only solution is, as described in your second link, I need to add keys or something to block those uploads in the first place?

    Regarding the second link, is there anything special I need to know because I am using the nrf5340 with its seperate BLE processor, or will I still be able to use the code broadly as shown?

    Thank you!

Children
  • 0 in reply to i_4556

    Hi, 

    i_4556 said:
    Thank you for your reply. I am using an Iphone 12 running IOS 16.6. I am using the NRF connect app on the phone. I am using SDK 2.5.0, and per the example simply added

    Does it work with your iPhone now? Could you test with peripheral_lbs? Does peripheral_lbs also make the app crash or does it only happen with your code? Could you provide the project?

    i_4556 said:
    If the firmware just swaps the images, what is to stop a malicious actor uploading firmware that then dumps the old code out the serial port or otherwise bypasses readback protections? I assume the only solution is, as described in your second link, I need to add keys or something to block those uploads in the first place?

    That's true. 

    i_4556 said:
    Regarding the second link, is there anything special I need to know because I am using the nrf5340 with its seperate BLE processor, or will I still be able to use the code broadly as shown?

    The setting is the same as other chips to set the configs in child_image/mcuboot.conf

    -Amanda H.

  • 0 in reply to Amanda Hsieh

    Hello and thank you for your reply. I have made no real progress in trying to get this to work. As a workaround I have tried installing the DFU app on my iphone. That also doesnt work; when I try to select the .zip package, I get an "invalid manifest" error.

    I figured at this point I might as well try to advance the project on my own, and implemented the code from this example: https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/keys_and_signatures/mcuboot_smp_custom_key this way only our company will be able to push new firmware to our device. I have added the example's .config and CMakeLists changes, and the mcuboot.conf changes.

    I then tried using my coworker's android phone. This also doesnt work; although it doesnt crash immediately like on my iphone, it also doesnt work. It tries to update and gets stuck on the "Connecting" stage.

    I cannot provide my entire project, but I can provide the .config files and other files like that if that helps.

    I will test with the LBS and report back.

    EDIT: tested with the LBS and just adding the two CONFIGs from the first example, and did not work with android or iphone, With iphone I still have the crash to the home-screen, and with android it looks like it worked but nothing actually happens on the device, the firmware is not updated.

    EDIT2: I re-tested with the peripheral hids mouse sample, as I have already gotten this working on my device, and the OTA update in the simplest case worked on android. I will re-test on IOS, and then we just need to get signed keys working, and figure out why it doesnt seem to want to work on my main app.

    EDIT3: Still broken with IOS, app crashes when I try to update.

  • 0 in reply to i_4556

    It's good to know it works with the Android phone now. Please be aware that the mcuboot will not do anything if you upload an unmodified file.  

    I can reproduce the issue with iOS and check with the team now. I will be back if I have any updates from the team. 

  • 0 in reply to Amanda Hsieh

    Hello, thank you for your reply.

    I look forward to the IOS issues being fixed, as it would be nice to be able to update the firmware from my phone (and to return my coworker's phone to him).

    In the meantime, I am still having issues with the DFU when I try to implement keys. In the app on android it seems to rapidly flash through the connecting/uploading/validating (too fast to actually see them), and on the firmware side I get the following message in the terminal "I: Image index: 0, Swap type: none" and then nothing has actually happened.

    Could the problem be as simple as the key being somehow wrong?

    Here is my prj.config file:

    #
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_MAX_CONN=2
CONFIG_BT_MAX_PAIRED=2
CONFIG_BT_L2CAP_TX_BUF_COUNT=5
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="HIDS_mouse"
CONFIG_BT_DEVICE_APPEARANCE=962

CONFIG_BT_BAS=y
CONFIG_BT_HIDS=y
CONFIG_BT_HIDS_MAX_CLIENT_COUNT=2
CONFIG_BT_GATT_UUID16_POOL_SIZE=40
CONFIG_BT_GATT_CHRC_POOL_SIZE=20

CONFIG_BT_CONN_CTX=y

CONFIG_BT_DIS=y
CONFIG_BT_DIS_PNP=y
CONFIG_BT_DIS_MANUF="NordicSemiconductor"
CONFIG_BT_DIS_PNP_VID_SRC=2
CONFIG_BT_DIS_PNP_VID=0x1915
CONFIG_BT_DIS_PNP_PID=0xEEEE
CONFIG_BT_DIS_PNP_VER=0x0100

CONFIG_MAIN_STACK_SIZE=1536
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

CONFIG_DK_LIBRARY=y

#DFU settings
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUMGR=y
#changed for BT instead of UART
CONFIG_MCUMGR_TRANSPORT_BT=y
#changed, dont want to require a passcode to send dfu image
CONFIG_MCUMGR_TRANSPORT_BT_AUTHEN=n

CONFIG_MCUMGR_GRP_IMG=y
CONFIG_BASE64=y
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y
CONFIG_STREAM_FLASH=y
CONFIG_NET_BUF=y
CONFIG_ZCBOR=y
CONFIG_FLASH_MAP=y

    And my CMakeLists

    #
# Copyright (c) 2019 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
cmake_minimum_required(VERSION 3.20.0)

set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE \"${CMAKE_CURRENT_SOURCE_DIR}/custom_key_dir/custom_priv.pem\")

find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(peripheral_hids_mouse)

FILE(GLOB app_sources src/*.c)
# NORDIC SDK APP START
target_sources(app PRIVATE ${app_sources})
# NORDIC SDK APP END

zephyr_library_include_directories(${ZEPHYR_BASE}/samples/bluetooth)

    And finally in my child_image folder I have an mcuboot file with CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y

    I followed the instructions exactly like here for the keyfile:

    ${NCS_PATH}/bootloader/mcuboot/scripts/imgtool.py keygen -k custom_priv.pem -t ecdsa-p256

    Do you have any suggestions for what could be wrong, why I cant seem to use DFU in signed mode? Do I still upload the app_update.bin file like with the insecure mode?

    Thank you!

    EDIT: Tested the base case with no signature on my other coworker's iphone 13 and that works fine. Not sure if its all Iphone12 or just mine it doesnt work on...

    EDIT2: Tested with my old android phone running Android 7.0 and once again app crashes when trying to perform DFU. It doesnt crash on my Android 9.0 but also doesnt work, just flashes through the screens like above.

  • 0 in reply to i_4556

    Hi,



    Here is my example peripheral_hids_mouse.7z. After uploading with the update_image/nRF53_HID_app_update.bin, it would show "build time: Jan 29 2024 09:51:56"

    Beware that this code/configuration is not fully tested or qualified and should be considered provided “as-is”. Please test it with your application and let me know if you find any issues.

    i_4556 said:
    EDIT: Tested the base case with no signature on my other coworker's iphone 13 and that works fine. Not sure if its all Iphone12 or just mine it doesnt work on...

    Could you try to use the nRF Connect Device Manager App https://apps.apple.com/us/app/nrf-connect-device-manager/id1519423539? Please make sure it's the latest version v1.5.3. 

    The minimum required iOS version is 9.0, originally released in Fall of 2015.

    i_4556 said:
    EDIT2: Tested with my old android phone running Android 7.0 and once again app crashes when trying to perform DFU. It doesnt crash on my Android 9.0 but also doesnt work, just flashes through the screens like above.

    Please try to use the nRF Connect Device Manager app https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrfconnectdevicemanager&hl=en_US 

    The minimum required Android version is 5.0 (Android Lollipop) due to a requirement for high MTU.

    -Amanda H.

Related
Terms of service