• State Verified Answer
  • Replies 4 replies
  • Subscribers 68 subscribers
  • Views 103 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 335819
Options

Couldn't change the CONFIG_BT_DEVICE_NAME from Nordic_UART_Service to something else

raghuveer

Hello,

I have a custom board with nRF5340 and I am unable to change the BT_DEVICE_NAME on the NET core. I have tried both rpc_host and ipc_radio (RPC) images. they both have the same issue. I am setting the value using a snippet and it is being merged as you can see below.

   *******************************
   * Running CMake for ipc_radio *
   *******************************
......

Parsing /home/workspace/sdk/nrf/applications/ipc_radio/Kconfig
Loaded configuration '/home/workspace/fw/boards/vendor/hid/hid_nrf5340_cpunet_defconfig'
Merged configuration '/home/workspace/sdk/nrf/applications/ipc_radio/prj.conf'
Merged configuration '/home/workspace/fw/snippets/hid-bt-rpc.conf'
Merged configuration '/home/workspace/sdk/nrf/applications/ipc_radio/overlay-bt_rpc.conf'
Merged configuration '/home/workspace/fw/build/ipc_radio/zephyr/.config.sysbuild'
Configuration saved to '/home/workspace/fw/build/ipc_radio/zephyr/.config'
Kconfig header saved to '/home/workspace/fw/build/ipc_radio/zephyr/include/generated/zephyr/autoconf.h'

.....

I am using sysbuild to build the project. The error on RTT log is

<err> BT_RPC: Missmatched CONFIG_BT_DEVICE_NAME: net="Nordic_UART_Ser, app="HID"

Should I use something else other than snippet to change the value in net core image?

Thank you.

Parents
  • +1

    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

  • 0 in reply to Kenneth

    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.

Reply
  • 0 in reply to Kenneth

    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.

Children
Related