Marking the image for testing and resetting

Use the ble image-hash subcommand to mark a specific image for testing after uploading it, and the ble reset subcommand to reset the device and apply the new image.

Complete the following steps to mark for testing a new firmware image on a device that advertises with the Nordic_LBS name:

1. Check the hash of the image you want to mark for testing by using one of the following two options:

   • The ble image-list subcommand with correct option values:

     nrfutil mcu-manager ble --hci-serial-port COM35 image-list --device-name Nordic_LBS
     

   • The image-hash subcommand with the name of the firmware image file you uploaded:

     nrfutil mcu-manager image-hash --firmware mcuboot_secondary_app_update.bin
     

2. Note down the hash of the image you want to mark for testing.

3. Run the following ble image-test command with correct option values and the hash value of the image:

   nrfutil mcu-manager ble --hci-serial-port COM35 image-test --device-name Nordic_LBS --hash 74e62f0ce9c2045f8f56f650e2667c531be55b1289dc8109ba6445409a8a072f
   

4. Run the ble image-list subcommand with correct option values to confirm the operation:

   nrfutil mcu-manager ble --hci-serial-port COM35 image-list --device-name Nordic_LBS
   

   The output will look similar to the one after the initial upload, but the new application image in slot 1 will now be in pending state (pending: true), in addition to the application image in slot 0 that is currently active (active: true):

   v Device found: F9:9F:F3:7E:B3:D6, Nordic_LBS
   v Connected to device: F9:9F:F3:7E:B3:D6
   Image
           slot: 0
           version: 1.0.0
           hash: a111cd40c001b75439dfd0d4ecaa1c9b2de71b80fd49a8f0f6a3c151055e45b5
           bootable: true
           pending: false
           confirmed: true
           active: true
           permanent: false
   Image
           slot: 1
           version: 2.0.0
           hash: 74e62f0ce9c2045f8f56f650e2667c531be55b1289dc8109ba6445409a8a072f
           bootable: true
           pending: true
           confirmed: false
           active: false
           permanent: false
   

5. Run the ble reset subcommand to reset the device and boot into the new image:

   nrfutil mcu-manager ble --hci-serial-port COM35 reset --device-name Nordic_LBS --hash 74e62f0ce9c2045f8f56f650e2667c531be55b1289dc8109ba6445409a8a072f
   

   The device reboots. The output will look similar to the following one:

   v Device found: F9:9F:F3:7E:B3:D6, Nordic_LBS
   v Connected to device: F9:9F:F3:7E:B3:D6
   v Reset was applied for Nordic_LBS
   

6. Run the ble image-list subcommand with correct option values to confirm the operation:

   nrfutil mcu-manager ble --hci-serial-port COM35 image-list --device-name Nordic_LBS
   

   The output will look similar to the one shown above, but the new application image in slot 1 will not be in pending state anymore (pending: false) and it will be marked as currently active (active: true):

   v Device found: F9:9F:F3:7E:B3:D6, Nordic_LBS
   v Connected to device: F9:9F:F3:7E:B3:D6
   Image
           slot: 0
           version: 1.0.0
           hash: a111cd40c001b75439dfd0d4ecaa1c9b2de71b80fd49a8f0f6a3c151055e45b5
           bootable: true
           pending: false
           confirmed: true
           active: false
           permanent: false
   Image
           slot: 1
           version: 2.0.0
           hash: 74e62f0ce9c2045f8f56f650e2667c531be55b1289dc8109ba6445409a8a072f
           bootable: true
           pending: false
           confirmed: false
           active: true
           permanent: false