Change device name

RE: Change device name

wasifali — Mon, 02 Feb 2026 12:48:03 GMT

Thank you for giving solution in detail.

RE: Change device name

jimmyandrz — Fri, 31 Oct 2025 19:34:30 GMT

Yes, you can change the device name via the nRF Connect app, but only if your firmware allows it. You’d need to add code to handle a GATT characteristic for the device name and store it (e.g., in flash).

Yes, possible with J-Link command line using nrfjprog --memwr or similar, but you’d have to know the memory address where the name is stored not super convenient unless scripted.

Easiest quick fix: add a UART or BLE command in your firmware to change the name at runtime and save it to flash, so you don’t need to recompile every time.

Hope! it would be helpful.

myinfo kroger login

RE: Change device name

tony55723 — Thu, 04 Apr 2024 13:04:42 GMT

Hello Ylvisaker ,

Is sequential, the numbers are only used for production, actual connection relies on UUID filtering.

[quote userid="87869" url="~/f/nordic-q-a/109808/change-device-name/477115"]Please do not hesitate to open another ticket if you should have any issues or questions to the flash storage usage or samples.[/quote]

OK, Thank you

RE: Change device name

Karl Ylvisaker — Thu, 04 Apr 2024 12:57:37 GMT

Hello,

[quote user="tony55723"]The device number is assigned according to the quantity ordered by the customer. For example, if 100 units are ordered today, the numbers will be from 1 to 100. If 200 units are ordered tomorrow, the numbers will be from 101 to 300.[/quote]

Thank you for clarifying. Does the numbers need to be sequential and in order? If not then you could perhaps instead base them on a permutation of the device ID in the FICR register instead.
If they do need to be sequential, how will a device know which number it is?

[quote user="tony55723"]Thank you very much. In the infocenter you provided, I found examples\peripheral\flash_fstorage. Later, I will try to implement the write flash function.[/quote]

Great, I am happy to hear that you found it helpful! Please do not hesitate to open another ticket if you should have any issues or questions to the flash storage usage or samples.

Best regards,
Karl

RE: Change device name

tony55723 — Wed, 03 Apr 2024 14:20:49 GMT

Hello Ylvisaker ,

The device number is assigned according to the quantity ordered by the customer. For example, if 100 units are ordered today, the numbers will be from 1 to 100. If 200 units are ordered tomorrow, the numbers will be from 101 to 300.

Thank you very much. In the infocenter you provided, I found examples\peripheral\flash_fstorage. Later, I will try to implement the write flash function.

RE: Change device name

Karl Ylvisaker — Wed, 03 Apr 2024 13:43:43 GMT

[quote user="tony55723"]

const char* DEVICE_NAMES[] = {"Device0001", "Device0002", ....... ,"Device9999"};

nRF52811 Flash is so small

[/quote]

I would not recommend this approach if your list of potential names are as long as this, all but one of these entries actually will be useful to the device. In this case I would go with the approach using a single variable stored in flash, which you may later re-write if needed.

It is not quite clear to me how the number of the device name will be generated or determined, could you elaborate on this?

[quote user="tony55723"]But I have a question, the BLE data reception (NUS), or buttons, and what I consider UART (PCB copper wires), these all belong to external signals, so I still need to store data (Flash), right?[/quote]

Yes, all of these options would still need to store in flash in order to persist through a reset.

[quote user="tony55723"]The next time the device boots up, it will first read from the Flash. For example, if it reads 0x0a, it will advertise as 'Device' + '0x0a', which is 'Device0010', right?[/quote]

If you are using a variable for your name which you have stored in flash then this variable will be read upon startup and input as the device name to the GAP function, yes. Please see one of the three FLASH storage examples here as a reference for how you may store your variable in flash.

Best regards,
Karl

RE: Change device name

tony55723 — Wed, 03 Apr 2024 10:24:37 GMT

Hello Ylvisaker ,

[quote userid="87869" url="~/f/nordic-q-a/109808/change-device-name/476800"]you could have a list[/quote]

const char* DEVICE_NAMES[] = {"Device0001", "Device0002", ....... ,"Device9999"};

nRF52811 Flash is so small

I may not design it this way, but it should be achievable using the 'Device+xxx' approach.

But I have a question, the BLE data reception (NUS), or buttons, and what I consider UART (PCB copper wires), these all belong to external signals, so I still need to store data (Flash), right?

The next time the device boots up, it will first read from the Flash. For example, if it reads 0x0a, it will advertise as 'Device' + '0x0a', which is 'Device0010', right?

RE: Change device name

Karl Ylvisaker — Wed, 03 Apr 2024 09:29:40 GMT

Hello,

[quote user="tony55723"]But I hope that after changing the name, the advertising will use the new name the next time the power is restarted. Do I have to modify the DEVICE_NAME every time I want to change the name and wait for the 1-minute build time?[/quote]

If you use a variable instead of the compile-time DEVICE_NAME define then the device will start its advertising with whatever name you have provided in that variable, and so you will not have to recompile each time you want to change name, no.

How you populate that variable name will be up to you - you could have a list of names stored in your FLASH (persistent memory), or you can receive the new name from a BLE connection, or you can push a button to make it go to a predetermined name.

Best regards,
Karl

RE: Change device name

tony55723 — Tue, 02 Apr 2024 12:18:28 GMT

Hello Ylvisaker ,

But I hope that after changing the name, the advertising will use the new name the next time the power is restarted. Do I have to modify the DEVICE_NAME every time I want to change the name and wait for the 1-minute build time?😭

RE: Change device name

Karl Ylvisaker — Tue, 02 Apr 2024 11:58:27 GMT

Hello,

[quote user="tony55723"]If I use variables, will the name revert back to its original one the next time I power cycle?[/quote]

Yes, unless you store this name in FLASH it will revert back to the initial name upon resetting.

Best regards,
Karl

RE: Change device name

tony55723 — Tue, 02 Apr 2024 11:39:36 GMT

Hello Ylvisaker ,

If I use variables, will the name revert back to its original one the next time I power cycle?

RE: Change device name

Karl Ylvisaker — Tue, 02 Apr 2024 11:34:14 GMT

Hello,

[quote user="tony55723"]Thank you for your reply.[/quote]

No problem at all, I am happy to help!

[quote user="tony55723"]I still don't quite understand how to initialize advertising separately. My previous approach was to modify the DEVICE_NAME, then build, wait for more than 1 minute until the hex file was generated, and then download it to the chip. However, the build time is too long.[/quote]

Yes, please see the gap_params_init function in the example. Here you can change away from using the DEVICE_NAME define to instead use a variable you can change throughout the lifetime if your application.

Best regards,
Karl

RE: Change device name

tony55723 — Tue, 02 Apr 2024 11:18:55 GMT

Hello Ylvisaker ,

Thank you for your reply.

[quote userid="87869" url="~/f/nordic-q-a/109808/change-device-name/476510"]You can re-init the advertising[/quote]

I still don't quite understand how to initialize advertising separately. My previous approach was to modify the DEVICE_NAME, then build, wait for more than 1 minute until the hex file was generated, and then download it to the chip. However, the build time is too long.

Whether it's central or peripheral, it's ble_app_multirole_lesc.

I used this example to establish a mesh network with 1-to-1-to-1 connections, extending continuously. Therefore, all devices include both central and peripheral roles.

RE: Change device name

Karl Ylvisaker — Tue, 02 Apr 2024 10:23:22 GMT

Hello,

[quote user=""]I know that I can modify #define DEVICE_NAME "device001" in sdk_config.h, but it takes a lot of time to compile and flash the program every time. It seems like there should be another way to quickly solve this.[/quote]

You can re-init the advertising and provide a new name as the device name parameter instead of DEVICE_NAME. Please see the section of main.c where DEVICE_NAME is used as the parameter to configure the name of the device in the GAP initialization.

This approach will also let you do so at runtime, so if you first receive the new name over BLE you can then re-init and start advertising with this new name.
Just out of curiosity, which use-case are you targeting where you would need to change the advertising name after you have already established connection with the central device?

Best regards,
Karl