RE: How to use a public address for advertising (nRF54LM20A)？

Leo Mo — Fri, 09 Jan 2026 02:56:54 GMT

Hi Terje,

Thank you very much!

It seems to be caused by CONFIG_BT_PRIVACY=y. Even though I later set it to n, the chip was not erased.

Best Regards,

Leo

RE: How to use a public address for advertising (nRF54LM20A)？

tesc — Tue, 06 Jan 2026 14:02:00 GMT

Hi,

I have tested this, using nRF Connect for Android, an nRF54LM20A DK v0.3.4 and nRF Connect SDK v3.2.1, with the peripheral_lbs sample with the following lines added to main.c:

Among the includes:

#include <zephyr/bluetooth/controller.h>

Right before the call in main() to bt_enable:

uint8_t addr[6] = {0x06, 0x05, 0x04, 0x03, 0x02, 0x01};
bt_ctlr_set_public_addr(addr);

I consistently see the device advertise with the address 01:02:03:04:05:06.

I know there was issues with bt_ctlr_set_public_addr() in nRF Connect SDK v2.2.0, which was memory related, but that issue was fixed for v2.3.0, and as far as I can tell the nRF54LM20A didn't even exist back then.

Regardless:

What version are you using of the nRF54LM20A and DK?
Are you able to reproduce the issue with the above additions to the otherwise unmodified peripheral LBS sample from nRF Connect SDK v3.2.1?

Regards,
Terje

RE: How to use a public address for advertising (nRF54LM20A)？

Leo Mo — Mon, 05 Jan 2026 09:41:18 GMT

The same project does not have this problem on the nRF52840.