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

DFU buttonless with SDK11

Hi all,

I have a custom board with a nRF51 and a DSP connected to eachother (SPI, UART and I2C) and since I have no connection to the nRF directly or any buttons I need to make upgrades on the nRF via serial DFU. To accomplish this I want to implement the DFU buttonless but I am using the SDK11 and SD130. Is there any example of this using the SDK11?

I always worked with SDK11, and I am not sure if it is better to update my code to work on the SDK12 or check the "dfu_buttonless_example" and try to downgraded it to the SDK11:

Does anyone have a idea what is the better option? Does the example work with the SDK11 without any changes?

Parents
  • Hi Jorge,

    It's always suggested to use the latest SDK. But if you want to use SDK v11 , you can find the buttonless example in \examples\ble_peripheral\ble_app_hrs\pca10028\s130_with_dfu

    Documentation is on info center as well.

    image description

  • I think I confused you with my question. On my project I already have the SD130 and the bootloader (single_bank_serial_130 with a few changes). I can download my application via HCI when I have only the SD130 and BL, but if I have my app already running I cannot download a new one.

    I thought I had to trigger something on my app to go to the bootloader after receiving the start packet to accomplish this.

    I reset the board (using the reset pin) but it always goes to the application on the bootloader.

Reply
  • I think I confused you with my question. On my project I already have the SD130 and the bootloader (single_bank_serial_130 with a few changes). I can download my application via HCI when I have only the SD130 and BL, but if I have my app already running I cannot download a new one.

    I thought I had to trigger something on my app to go to the bootloader after receiving the start packet to accomplish this.

    I reset the board (using the reset pin) but it always goes to the application on the bootloader.

Children
No Data
Related