• State Verified Answer
  • Replies 14 replies
  • Subscribers 63 subscribers
  • Views 8471 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 107382
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

DFU OTA issue on NRF51822AA

sidekick

I'm trying to implement DFU-OTA (Bluetooth transport) for our custom board and currently i'm facing problems in flashing the different elements (softdevice, bootloader, application). I think It's mostly a setup problem.

configuration:

  1. Hardware: NRF51822QFAA (256KB flash)
  2. Softdevice version: s110, v7.1.0
  3. nRFGo studio for flashing: v1.18.0.9
  4. Bootloader sample code: From SDK v6.1.0 (nrf51_sdk_v6_1_0_b2ec2e6)
  5. Custom application: total size of application (around 30kB)
  6. IDE: Keil uVision 5.14

To build bootloader, I've used the sample bootloader (without any modification at the moment, except some include path changes for linking). The bootloader builds fine and I use nRFGo Studio to flash the three elements (softdevice, bootloader and the application). I'm able to successfully flash all the three but when i do the verification of our application using "verify" tab in nRFGo studio, it says "Verification failed". Our custom board also has a LED that turns "ON", when there is some issue with the NRF51822QFAA. I do not know the workings of this feature yet, but the point is that i'm very much sure that there is some problem (maybe one being overwritten or being only written only partially).while flashing these three components

I'm attaching the memory ranges snapshot below, which I see in the Keil uVision for bootloader and our application. Please suggest.

memory layout for bootloder: image description

memory layout for our application: image description

Thank you for your help.

Parents
  • 0

    If you're flashing all three parts using Jlink, it won't work as is. When starts, bootloader checks BANK_VALID_APP variable that is not set in your case. You have few options:

    1. Flash SD and bootloader, and write your app over DFU - bootloader will handle BANK_VALID_APP for you.

    2. After flashing SD, bootloader and the app, manually program BANK_VALID_APP to 0x01

    3. Flash SD and your app only. Your app will start, but DFU obviously won't work without the bootloader.

    More details: devzone.nordicsemi.com/.../

  • 0 in reply to Pektusin

    Thank you Hung Bui for following up on this. As I'm reading more about DFU-OTA, my issue is turning multifaceted.

    1. I'm not using nRFgo Starter Kit (No button #7 as mentioned here) to go into bootloader mode, it's a custom board and has nrf51822QFAA SOC.
    2. Cannot use Experimental, sample PC applications*(~/\ble_dfu_send_hex/*) to perform device firmware update as I do not have Master Control Panel dongle. Initially I wanted, SD + Bootloader + App on our custom board and perform application upgrade later, but as I've understood so far, I've to implement a logic using GPREGRET register, both in Bootloader and in our application. So currently, just to test DFU, I should not write 0x01 to 0x00003fc00 and try only with SD and Bootloader.
Reply
  • 0 in reply to Pektusin

    Thank you Hung Bui for following up on this. As I'm reading more about DFU-OTA, my issue is turning multifaceted.

    1. I'm not using nRFgo Starter Kit (No button #7 as mentioned here) to go into bootloader mode, it's a custom board and has nrf51822QFAA SOC.
    2. Cannot use Experimental, sample PC applications*(~/\ble_dfu_send_hex/*) to perform device firmware update as I do not have Master Control Panel dongle. Initially I wanted, SD + Bootloader + App on our custom board and perform application upgrade later, but as I've understood so far, I've to implement a logic using GPREGRET register, both in Bootloader and in our application. So currently, just to test DFU, I should not write 0x01 to 0x00003fc00 and try only with SD and Bootloader.
Children
No Data
Related