• State Verified Answer
  • Replies 14 replies
  • Subscribers 62 subscribers
  • Views 8432 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

    @sidekick: It's my mistake in the presentation. As shown here the init packet is optional. I will update the slide. Sorry about that.

    Could you explain why you want to write 0x01 to 0x00003fc00 ?

    With nRFLogger, after you have done a DFU session in nRFToolbox, you should see the log in the logger app. You can also try to use nRF Master Control Panel to do DFU. You can swipe right when doing it to see the log.

    To be able to open a file on your phone, you can try to install a File manager app. There are several of them on Goolge Play.

    Which phone did you use to test ?

Reply
  • 0

    @sidekick: It's my mistake in the presentation. As shown here the init packet is optional. I will update the slide. Sorry about that.

    Could you explain why you want to write 0x01 to 0x00003fc00 ?

    With nRFLogger, after you have done a DFU session in nRFToolbox, you should see the log in the logger app. You can also try to use nRF Master Control Panel to do DFU. You can swipe right when doing it to see the log.

    To be able to open a file on your phone, you can try to install a File manager app. There are several of them on Goolge Play.

    Which phone did you use to test ?

Children
No Data
Related