eshaulx opened a new issue #69: mcumgr firmware update over BLE: Error: 6 on 
image confirm
URL: https://github.com/apache/mynewt-mcumgr/issues/69
 
 
   Hi,
   I am running Zephyr 2.1.99-ncs1 on an NRF52840 target with MCUbootloader.
   I have 2 applications smp_svr1 & smp_svr2 the former is loaded to slot 0 and 
slot 1 is free.
   I am trying to update the board with the smp_svr2 to slot 1 over BLE using 
mcumgr CLI as follows:
   ` 
   ~/workspace/go/src/mynewt.apache.org/mcumgr/mcumgr>sudo ./mcumgr --conntype 
ble --connstring 'peer_name=Zephyr' image list
   
   Images:
    image=0 slot=0
       version: 0.0.0
       bootable: true
       flags: active confirmed
       hash: 77f2bde082227506df7fc92519485963992dcb81b44400c9c144b22ffa9e44fc
   Split status: N/A (0)
   ~/workspace/go/src/mynewt.apache.org/mcumgr/mcumgr>sudo ./mcumgr --conntype 
ble --connstring 'peer_name=Zephyr' image upload 
~/workspace/canary/Canary_Application/smp_svr_2/build/zephyr/app_update.bin
    119.82 KiB / 119.82 KiB 
[===============================================================================================================]
 100.00% 2.67 KiB/s 44s
   Done
   ~/workspace/go/src/mynewt.apache.org/mcumgr/mcumgr>sudo ./mcumgr --conntype 
ble --connstring 'peer_name=Zephyr' image list
   
   Images:
    image=0 slot=0
       version: 0.0.0
       bootable: true
       flags: active confirmed
       hash: 77f2bde082227506df7fc92519485963992dcb81b44400c9c144b22ffa9e44fc
    image=0 slot=1
       version: 0.0.0
       bootable: true
       flags: 
       hash: cab9aed73169e23ed588673a10a9f4fec47b09cf384da1c4177fa8ed0b7490bf
   Split status: N/A (0)
   ~/workspace/go/src/mynewt.apache.org/mcumgr/mcumgr>sudo ./mcumgr --conntype 
ble --connstring 'peer_name=Zephyr' image test 
cab9aed73169e23ed588673a10a9f4fec47b09cf384da1c4177fa8ed0b7490bf
   Images:
    image=0 slot=0
       version: 0.0.0
       bootable: true
       flags: active confirmed
       hash: 77f2bde082227506df7fc92519485963992dcb81b44400c9c144b22ffa9e44fc
    image=0 slot=1
       version: 0.0.0
       bootable: true
       flags: pending
       hash: cab9aed73169e23ed588673a10a9f4fec47b09cf384da1c4177fa8ed0b7490bf
   Split status: N/A (0)
   ~/workspace/go/src/mynewt.apache.org/mcumgr/mcumgr>sudo ./mcumgr --conntype 
ble --connstring 'peer_name=Zephyr' reset        
   Done
   ~/workspace/go/src/mynewt.apache.org/mcumgr/mcumgr>sudo ./mcumgr --conntype 
ble --connstring 'peer_name=Zephyr' image confirm
   Error: 6
   ~/workspace/go/src/mynewt.apache.org/mcumgr/mcumgr>
   `
   The problem is that when pointing slot 1 hash and reseting, the application 
seems to be loaded from slot 0 (I have changed the printouts between both of 
the application)
   In addition, the command to confirm the image fails with Error: 6
   I appriciate any of your thoughts as to what is done wrongly.
   Both applications are using the configuration:
   `
   CONFIG_BOOTLOADER_MCUBOOT=y
   CONFIG_MCUBOOT_IMG_MANAGER=y
   `
   Thanks in advanced,
   Erez.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to