Bsim for central_hr example

RE: Bsim for central_hr example

Einar Thorsrud — Wed, 19 Mar 2025 09:34:43 GMT

Hi,

I have not been able to test today, but I see the UARTE peripheral should be emulated by the nrf52_bsim board, so I would expect it should be possible to get it to work with the proiper configuration. I suggest you refer to the nrf52_bsim board files for reference. I should add though that this is added by the Zephyr community and not supported by Nordic (that may change, though).

Also, please note that bsim has its clear uses for instance in reproducing bugs that can take a long time to reproduce, etc as you can simulate much faster than in real life. But the models are far from perfect, so you riskm issing real issues, and also getting false positives. So it is not a test tool I would recommend for most projects. (There is also a limitation in that currently you have to use Zephyr LL and not the SoftDegvice Controller which is what you should use in the real procuct, adding even more to the difference between the simulated device and the real product.)

RE: Bsim for central_hr example

Artnia — Wed, 19 Mar 2025 07:16:58 GMT

Hi, thank you, it looks good:

~/nordic/central_hr$ d_00: @00:00:00.000000  *** Booting nRF Connect SDK v2.8.0-a2386bfc8401 ***
d_00: @00:00:00.000000  *** Using Zephyr OS v3.7.99-0bc3393fb112 ***
d_00: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
d_00: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
d_00: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 3.7 Build 99
d_00: @00:00:00.000000  [00:00:00.000,000] <wrn> bt_id: No static addresses stored in controller
d_00: @00:00:00.002648  [00:00:00.002,624] <inf> bt_hci_core: Identity: FD:9E:B2:48:47:39 (random)
d_00: @00:00:00.002648  [00:00:00.002,624] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x0000, manufacturer 0x0059
d_00: @00:00:00.002648  [00:00:00.002,624] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0xffff
d_00: @00:00:00.002648  Bluetooth initialized
d_00: @00:00:00.003368  Scanning successfully started

Now I would like to do the same for my actual application instead of central_hr. My app is based on the NUS example and uses UART. I run into following error:

d_00: @00:00:00.000000  *** Booting My Application v2.7.0-7937ab1b0b19 ***
d_00: @00:00:00.000000  *** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
d_00: @00:00:00.000000  *** Using Zephyr OS v3.7.99-0bc3393fb112 ***
d_00: @00:00:00.000000  [00:00:00.000,000] <err> UART_DRIVER: Cannot initialize UART callback
d_00: @00:00:00.000000  [00:00:00.000,000] <err> BLE: Uart init failed (err -88)

which comes from here:

    /* Register UART Callback */
    err = uart_callback_set(uart, uart_cb, NULL);
    if (err) {
        k_free(rx);
        LOG_ERR("Cannot initialize UART callback");
        return err;
    }

while -88 is

#define ENOSYS 88		/* Function not implemented */

and zephyr.dts:

devzone.nordicsemi.com/.../8508.zephyr.dts

Probably also something with the device tree. Do you have an idea?

RE: Bsim for central_hr example

Einar Thorsrud — Tue, 18 Mar 2025 12:38:54 GMT

Hi,

The way to change Bluetooth controller implementation has changed, and that is now done in the devicetree instaed of using Kconfig. See this post for details.