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:
- Hardware: NRF51822QFAA (256KB flash)
- Softdevice version: s110, v7.1.0
- nRFGo studio for flashing: v1.18.0.9
- Bootloader sample code: From SDK v6.1.0 (nrf51_sdk_v6_1_0_b2ec2e6)
- Custom application: total size of application (around 30kB)
- 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:
memory layout for our application:
Thank you for your help.
