BLE_DFU BL653dvk Mcumgr error()

Hi,

    I am testing the DFU via BLE . and  while checking the logs I found out that it is saying  11:40:29.851 [McuMgr] Error: NOT_SUPPORTED (8) . after that msg , it is calling reset board cmd. and board is getting reset. am following below link for DFU from external flash( https://devzone.nordicsemi.com/f/nordic-q-a/83402/ncs1-8-0-52840-mcuboot-spi-external-flash-can-t-build-pass)

while searching in forum I found out this post ( https://devzone.nordicsemi.com/f/nordic-q-a/76399/ble-dfu-mcu-mgr-error-not_supported-8 ), and  I  have verified all the things which are mentioned in that post. still am getting this issue. 

Regards,

Vinay s

Parents
  • yes i will try that example and i will update here .

    Hi Hung Bui,

                       I am able to build your file and i have checked my modified files .I am able to build it and after flashing to the board, the DFU is not happened which is expected. here is the logs.

    *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
    Starting Bluetooth Peripheral LBS example
    build time: Jun  1 2022 17:58:18
    
    I: 2 Sectors of 4096 bytes
    I: alloc wra: 0, fd0
    I: data wra: 0, 1c
    I: SoftDevice Controller build revision:
    I: 0e e7 c5 66 67 18 3c ac |...fg.<.
    I: b3 d2 cc 81 a3 dc f1 c0 |........
    I: c0 36 02 22             |.6."
    I: No ID address. App must call settings_load()
    Bluetooth initialized
    Advertising successfully started
    Connected
    
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    
    *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
    I: Starting bootloader
    W: Cannot upgrade: not a compatible amount of sectors
    I: Bootloader chainload address offset: 0xc000
    I: Jumping to the first image slot
    
    *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
    Starting Bluetooth Peripheral LBS example
    build time: Jun  1 2022 17:58:18
    
    I: 2 Sectors of 4096 bytes
    I: alloc wra: 0, fd0
    I: data wra: 0, 1c
    I: SoftDevice Controller build revision:
    I: 0e e7 c5 66 67 18 3c ac |...fg.<.
    I: b3 d2 cc 81 a3 dc f1 c0 |........
    I: c0 36 02 22             |.6."
    I: No ID address. App must call settings_load()
    Bluetooth initialized
    Advertising successfully started
    Connected
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    
    *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
    I: Starting bootloader
    W: Cannot upgrade: not a compatible amount of sectors
    I: Bootloader chainload address offset: 0xc000
    I: Jumping to the first image slot
    
    *** Booting Zephyr OS build v2.7.99-ncs1-1  ***
    Starting Bluetooth Peripheral LBS example
    build time: Jun  1 2022 17:58:18
    
    
    I: 2 Sectors of 4096 bytes
    I: alloc wra: 0, fd0
    I: data wra: 0, 1c
    I: SoftDevice Controller build revision:
    I: 0e e7 c5 66 67 18 3c ac |...fg.<.
    I: b3 d2 cc 81 a3 dc f1 c0 |........
    I: c0 36 02 22             |.6."
    I: No ID address. App must call settings_load()
    Bluetooth initialized
    Advertising successfully started
    Connected
    
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    I: Swap type: test
    
    

    In app also , it will say validating and after that ,it will disconnect immediately and board went for reset. Can you help me to figure this out 

  • Please describe what exactly you did for testing ? Did you test my example alone or you tested by integrating to your app ? 
    How did you do DFU ? Via UART or via BLE ? 


    If you did via BLE did you select CONFIRM instead of TEST & CONFIRM ? 

Reply Children
No Data
Related