Couldn't change the CONFIG_BT_DEVICE_NAME from Nordic_UART_Service to something else

RE: Couldn't change the CONFIG_BT_DEVICE_NAME from Nordic_UART_Service to something else

Kenneth — Tue, 12 Nov 2024 15:36:31 GMT

You are of course free to do as you want to, but if you haven't already, I suggest to go through:
https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/

Kenneth

RE: Couldn't change the CONFIG_BT_DEVICE_NAME from Nordic_UART_Service to something else

raghuveer — Tue, 12 Nov 2024 15:32:50 GMT

To implement BLE host on the network core, which one is the suggested, nrf/applications/ipc_radio or nrf/samples/bluetooth/rpc_host ?

RE: Couldn't change the CONFIG_BT_DEVICE_NAME from Nordic_UART_Service to something else

raghuveer — Tue, 12 Nov 2024 15:20:26 GMT

I have tried to use HCI_IPC today and faced some configuration issues. So, I would like to continue with RPC as I can at least get it to work with the device name Nordic_UART_Service.

In my case, I could change the CONFIG_BT_DEVICE_NAME value of my application core. For network core, I am using the SB_CONFIG_NETCORE_IPC_RADIO_BT_RPC. It is defaulting to the CONFIG_BT_DEVICE_NAME="Nordic_UART_Service" on the network core.

I am using the `west build -p` option. The error is directly is in the RTT logs so, I think it is not a caching issue on the central.

RE: Couldn't change the CONFIG_BT_DEVICE_NAME from Nordic_UART_Service to something else

Kenneth — Mon, 11 Nov 2024 12:12:53 GMT

Hello,

Dont' use rpc, it's experimental only, and I don't expect it is much used in general.

To change the device name the only thing you need to do is modify CONFIG_BT_DEVICE_NAME in:
\nrf\samples\bluetooth\peripheral_uart\prj.conf (actual path depend on the example you are using)

Make sure to build with --pristine option to ensure the change take effect. Also be aware that if you have connected to a central before, the central may cache the device name, so it may not update the device name until after you re-connect.

Kenneth