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]

Not exactly. I was guessing that the previous version stored the values somewhere in the flash and not necissarily in the UICR registers. If yes, he needs to read these first and afterwards either flash them to the UICR registers - which means he has to change his implementation - or write them back to the correct place in flash. That would mean that he has to have 0xFFFFFFF values in his implementation so that it is possible writing to this location in flash without erasing the full page. The UICR approach would be best of course.