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

nRF Beacon S110 v8 DFU upgrade

Olivier

I've developed an application on the nRF51 DK, now for further testing purposes I need to upload it to the nRF Beacon (PCA20006).

My software uses SDK8 (S11 v8) and it seems I can't find any documentation on upgrading to this soft device from the iOS application.

So: how does the S110 v8 need to be prepared for the OTA DFU update? I read in the pdf form the second link that you should delete some lines in the hex file, however the newer version looks quite different.

I have read this and this. The first link states that one should use an exe-file, but my MCP does not seem to have that specific file in the given directory. screenshot

I have only an iPhone and nRF51 DK at my disposal. So an upgrade must be done OTA.

Update

I now have MCP 3.8 installed and am able to locate nrf.exe. I have successfully created a bin file using: nrf.exe dfu genkpg --softdevice s110_nrf51_8.0.0_softdevice.exe --application-version 0xffffffff --dev-revision 0xffff --dev-type 0xffff --sd-req 0x64 C:\Noridic\myzip.zip

I then uploaded the zip-archive to my iPhone (latest nRF Toolbox). But when I press Update I get: Error on Init Packet. Message: Operation Failed.

Parents
  • 0

    Hi Olivier

    I can not make it work either with MCP 3.8 and the nrf.exe method described here to generate zip file for SDK 7.1.0 bootloader. The Beacon kit 1.1.0 contains S110 7.1.0 and bootloader from SDK 7.1.0

    One thing I noticed though is that you have option --sd-req 0x64 which is the FWID for S110 8.0.0 softdevice, see this thread. You should include the ID of that sofdevice instead in your init packet, i.e. --sd-req 0x5A. Including a wildcard option should also work great, i.e. to have --sd-req 0xFFFE

    For now, I can only recommend to use MCP 3.7.1 and the method described on this link in order to upload softdevice/bootloader/application to the beacon kit 1.1.0. I think anyway you would need to update both softdevice and bootloader at once, in order to have compatible S110 8.0.0 and SDK 8.0.0 bootloader after the update. Otherwise you will end up with S110 8.0.0 and SDK 7.1.0 bootloader, which are not compatible, see the nRF51 compatibility matrix.

Reply
  • 0

    Hi Olivier

    I can not make it work either with MCP 3.8 and the nrf.exe method described here to generate zip file for SDK 7.1.0 bootloader. The Beacon kit 1.1.0 contains S110 7.1.0 and bootloader from SDK 7.1.0

    One thing I noticed though is that you have option --sd-req 0x64 which is the FWID for S110 8.0.0 softdevice, see this thread. You should include the ID of that sofdevice instead in your init packet, i.e. --sd-req 0x5A. Including a wildcard option should also work great, i.e. to have --sd-req 0xFFFE

    For now, I can only recommend to use MCP 3.7.1 and the method described on this link in order to upload softdevice/bootloader/application to the beacon kit 1.1.0. I think anyway you would need to update both softdevice and bootloader at once, in order to have compatible S110 8.0.0 and SDK 8.0.0 bootloader after the update. Otherwise you will end up with S110 8.0.0 and SDK 7.1.0 bootloader, which are not compatible, see the nRF51 compatibility matrix.

Children
Related
Terms of service