• State Not Answered
  • Replies 16 replies
  • Subscribers 72 subscribers
  • Views 645 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 339255
Options

Bluetooth Mesh - No cdb entry for subnet 0x000

susenka

Hi,
I recently purchased a nRF52840 dongle with the intention of creating a Bluetooth mesh provisioner with it. The first thing I tried was flashing the mesh_shell example. The flash was successful, but once I started the provisioning process described in https://docs.zephyrproject.org/latest/connectivity/bluetooth/api/mesh/shell.html, the application threw some errors that I do not seem to understand. Has anyone faced the same problem? Thanks.

*** Booting Zephyr OS build v4.0.0-2778-g1b70bfa14e28 ***
Initializing...
[00:00:00.326,110] <inf> fs_nvs: 4 Sectors of 4096 bytes
[00:00:00.326,110] <inf> fs_nvs: alloc wra: 0, e70
[00:00:00.326,141] <inf> fs_nvs: data wra: 0, 2d8
[00:00:00.330,902] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,024] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,146] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,268] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,390] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,481] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,604] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,726] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,848] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.331,970] <wrn> net_buf: Timeout discarded. No blocking in syswq
[00:00:00.332,061] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.332,092] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.332,122] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 4.0 Build 99
uart:~$ > mesh init
mesh init
Mesh shell initialized
uart:~$ > mesh prov local 0 0x0001
mesh prov local 0 0x0001
No cdb entry for subnet 0x000

  • 0

    Hi,

    It seems to be coming from https://docs.nordicsemi.com/bundle/zephyr-apis-latest/page/group_net_buf.html#ga534366f3b5c7f41a28372c12149ca005. Could you verify the following:

    1. Which version of nRF Connect SDK are you using? 
      1. If you're running it from the Zephyr RTOS, do you see the same thing when using nRF Connect SDK? 
    2. If you have one available, do you see the same behavior on a nRF52840DK as well (no worries if you don't have one available, I will use that board to see if I can recreate it)
    3. Is the result you're describing coming from an unmodified shell sample from the SDK?

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi

    AHaug said:
    Which version of nRF Connect SDK are you using? 

    I don't think, this question is applicable to my problem since I'm using the stock Zephyr RTOS sample, but correct me if I'm wrong. I cannot seem to find a sample that does the same thing in the nRF Connect SDK. From what I understand, nRF Connect sdk does not include a sample application of mesh provisioner. Most of the samples are provisioned by the mobile application.

    AHaug said:
    If you have one available, do you see the same behavior on a nRF52840DK as well (no worries if you don't have one available, I will use that board to see if I can recreate it)

    Unfortunately I have only one dongle development kit by me.

    AHaug said:
    Is the result you're describing coming from an unmodified shell sample from the SDK?

    Yes, I haven't modified any of sample code. Also to add to this, I also tried to flash a mesh provisioner sample from the Zephyr RTOS repository, but ended up getting the same error messages - 

    [00:00:00.330,902] <wrn> net_buf: Timeout discarded. No blocking in syswq

    Thanks for your assistance,

    Viktor

  • 0 in reply to susenka
    susenka said:

    I don't think, this question is applicable to my problem since I'm using the stock Zephyr RTOS sample, but correct me if I'm wrong. I cannot seem to find a sample that does the same thing in the nRF Connect SDK. From what I understand, nRF Connect sdk does not include a sample application of mesh provisioner. Most of the samples are provisioned by the mobile application.

    To angle it the other way: Is there a difference if you follow the steps in the downstream version of Zephyr that is present within nRF Connect SDK or if you use the upstream Zephyr RTOS version

    susenka said:
    Unfortunately I have only one dongle development kit by me.

    No worries

    susenka said:
    Yes, I haven't modified any of sample code. Also to add to this, I also tried to flash a mesh provisioner sample from the Zephyr RTOS repository, but ended up getting the same error messages - 

    Thank you for verifying. I'll try to set the shell sample (from NCS, i.e zephyr downstream) and provision some devices to see if I see the same thing

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hello,

    First of all I would like to thank you for your help so far. I installed the nRF connect sdk on a clean windows installation and tried flashing the dongle using the sample program. Unfortunately the whole process failed, the device will not communicate via the built in UART and just becomes unresponsive. This also happens with the default mesh_provisioner sample. Just to note, the blinky sample works as intended without any problems. Have you tried flashing it to find the problem?

    Regards,

    Viktor

  • 0 in reply to susenka

    Hi,

    mesh init
Mesh shell initialized
uart:~$ > mesh prov local 0 0x0001
mesh prov local 0 0x0001
No cdb entry for subnet 0x000

    I believe I've found the reason. The reason for why you don't get any cdb entry for subnet 0x000 is because you haven't created a CDB yet. Use 'mesh cdb create <NetKey>' to create one.

    Let me know if you're able to provision the device after creating the CDB (worked for me at least)

    Kind regards,
    Andreas

Related
Terms of service