This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52832 buttonless dfu IAR

Hi.

I did the secure bootloader DFU. I attained step 8 in document.


I instal softdevice and secure bootloader to flash nRF52832. After make the ble_app_buttonless_dfu start download and debug but program not start.

If install only softdevice and buttonless_dfu then I got error "No bootloader was found".

If install softdevice and bootloader after buttonless dfu then I got not start programs.

Although security bootloader work. 
The verification was performed in the following steps:

E1. Generate new firmware.

E2. Generate new DFU .zip package.

E3. Switch the device to DFU mode, do DFU update and verify new image is running.

Help me.

Parents
  • Hi Alex, 

    Could you test first with a normal application instead of the buttonless example ? For example ble_app_hrs ? 

    Buttonless example requires bootloader setting to be generated and flashed. 

    I would suggest you to follow the tutorial here

  • I made the following:

    Step A. Generating keys.

    Step B. Build the bootloader.

    B1. Compile the uECC library.

    I download the library to the SDK folder.

     start building uECC.

    Copy the public_key in IAR.

    Build the bootloader.

    Step C.

    generate bootloader setting.

    mergehex


    zip file



    watch the video here

    What do I do wrong? 
  • Hi Alex, 

    I'm not sure why you merge the bootloader setting with the application. It's not needed in this case.

    Please try to follow my blog that I mentioned in last answer. 

    I can see when you create the .zip file you used --sd-reg 0xA9, why you used A9 ? Please use the correct softdevice code according to this table: 

    SoftDevice FWID (sd-req)
    s112_nrf52_6.0.0 0xA7
    s112_nrf52_6.1.0 0xB0
    s130_nrf51_1.0.0 0x67
    s130_nrf51_2.0.0 0x80
    s132_nrf52_2.0.0 0x81
    s130_nrf51_2.0.1 0x87
    s132_nrf52_2.0.1 0x88
    s132_nrf52_3.0.0 0x8C
    s132_nrf52_3.1.0 0x91
    s132_nrf52_4.0.0 0x95
    s132_nrf52_4.0.2 0x98
    s132_nrf52_4.0.3 0x99
    s132_nrf52_4.0.4 0x9E
    s132_nrf52_4.0.5 0x9F
    s132_nrf52_5.0.0 0x9D
    s132_nrf52_5.1.0 0xA5
    s132_nrf52_6.0.0 0xA8
    s132_nrf52_6.1.0 0xAF
    s140_nrf52_6.0.0 0xA9
    s140_nrf52_6.1.0 0xAE
Reply
  • Hi Alex, 

    I'm not sure why you merge the bootloader setting with the application. It's not needed in this case.

    Please try to follow my blog that I mentioned in last answer. 

    I can see when you create the .zip file you used --sd-reg 0xA9, why you used A9 ? Please use the correct softdevice code according to this table: 

    SoftDevice FWID (sd-req)
    s112_nrf52_6.0.0 0xA7
    s112_nrf52_6.1.0 0xB0
    s130_nrf51_1.0.0 0x67
    s130_nrf51_2.0.0 0x80
    s132_nrf52_2.0.0 0x81
    s130_nrf51_2.0.1 0x87
    s132_nrf52_2.0.1 0x88
    s132_nrf52_3.0.0 0x8C
    s132_nrf52_3.1.0 0x91
    s132_nrf52_4.0.0 0x95
    s132_nrf52_4.0.2 0x98
    s132_nrf52_4.0.3 0x99
    s132_nrf52_4.0.4 0x9E
    s132_nrf52_4.0.5 0x9F
    s132_nrf52_5.0.0 0x9D
    s132_nrf52_5.1.0 0xA5
    s132_nrf52_6.0.0 0xA8
    s132_nrf52_6.1.0 0xAF
    s140_nrf52_6.0.0 0xA9
    s140_nrf52_6.1.0 0xAE
Children
Related