Retaining Beacon Minor after upgrading Firmware

[james.eberhardt]

Hello;

I'm developing an application that advertises as a connectable peripheral. As such, it has an ID (think of it like a beacon minor).

I have 2000 of these devices.

How can I update the firmware on the device without needing to reset the ID of the device?

At the moment we are changing a "config.h" file in the project, compiling with Keil, and flashing the application onto the chip. Needless to say, it's taking an extremely long time.

[Marius Heil]

Hi, I implemented an over-the-mesh firmware update with my beacons, which saves a lot of time for these kind of use-cases ;-) But that won't help you right now. I'd suggest, you write yourself a batch script that reads the "minor" from the beacons. You can use nrfjprog with the --memread option. You only have to know the address where it was saved to memory.

Then, you flash the new firmware to the beacon and use memwrite afterwards to save the value to the new location in the new firmware.