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

original nRF51822 beacon firmware backup

Gentlemen: Do you have posted a copy of the original firmware that comes installed on the nRF51822 beacon? I have been experimenting writing my own app on that beacon, and so replaced that firmware with my own. But now, I need to put this aside for a while and would like to re-install the original app and bootloader (I presume I can used the S110 v6.2.1 with this). Thanks.

Parents
  • Hi.

    You can find older versions of the Beacon firmware here. Beacon version 1.0.x uses S110 v6.0.0 and SDK v5.1.0 (documented here).

    There is a trick for finding older releases of our firmware and that is to click on the version number instead of the code:

    image description

    It works for most of our software, SoftDevices, SDKs, etc.

    What build code do you have on your new and old chip variants? And when did you by your latest version? There is a CEAA version of all three silicon revisions so it is letter number 5 and 6 that will tell us what SDK and SoftDevice are to be used with your particular IC. Have a look at the Compatibility Matrix to learn more.

  • Yes, so far as the beacon app is concerned. If I just load the appropriate S110 hex file and firmware app, it will run on my beacons. In fact, I've been able to make all 3 versions of the app run - including the latest one indicated in your first response above. It turns out that the bootloader hex has been the problem all along. If you load that on, it seems to damage the image of the beaconware app in memory, and the beacon is always in bootloader mode. It will not respond to presses of SW1 or SW2, nor to a power recycle. I have tried this on several of my beacons. There could be a problem with my beacon version and the bootloaders that I have access to.

Reply
  • Yes, so far as the beacon app is concerned. If I just load the appropriate S110 hex file and firmware app, it will run on my beacons. In fact, I've been able to make all 3 versions of the app run - including the latest one indicated in your first response above. It turns out that the bootloader hex has been the problem all along. If you load that on, it seems to damage the image of the beaconware app in memory, and the beacon is always in bootloader mode. It will not respond to presses of SW1 or SW2, nor to a power recycle. I have tried this on several of my beacons. There could be a problem with my beacon version and the bootloaders that I have access to.

Children
No Data
Related