• State Not Answered
  • Replies 16 replies
  • Subscribers 25 subscribers
  • Views 309 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289853
Options

BLE_DFU BL653dvk Mcumgr error()

user106945

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

  • 0
    user106945 said:
    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 

  • 0 in reply to user106945

    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 ? 

  • 0
    Hung Bui said:
    Please describe what exactly you did for testing

    first I flashed board with one build along with changes of my board added and then i built it again by adding printf just to confirm , took that update.bin file and sent it to board through BLE.

    Hung Bui said:
    Did you test my example alone or you tested by integrating to your app ? 

    I tested it by integrating my changes.

    Hung Bui said:
    How did you do DFU ? Via UART or via BLE ? 

    Via BLE, UART I can't , Both UART we are utilizing for other purpose. So it has to be over BLE only.

    Hung Bui said:
    If you did via BLE did you select CONFIRM instead of TEST & CONFIRM ? 

    No ,I selected TEST and CONFIRM. 

  • 0 in reply to user106945

    Could you try doing with CONFIRM only ? 
    I would suggest to test my example with UART on a DK first before moving to your app. 


    At least the "NOT_SUPPORTED" error didn't show up ? and you managed to send the image ? Could you check what make the NOT_SUPPORTED disappear, from what I can see in the modifications you sent me it's almost the same like in my example. 

  • 0
    Hung Bui said:
    Could you try doing with CONFIRM only ? 

    Yes, i have tried . No luck .

    Hung Bui said:
    I would suggest to test my example with UART on a DK first before moving to your app. 

    agreed, am able to build it successfully , however I don't have relative board to test that and one more thing in your example you are using qspi , here i have to use SPI .

    Hung Bui said:
    At least the "NOT_SUPPORTED" error didn't show up ? and you managed to send the image ?

Related
Terms of service