• State Not Answered
  • +2 person also asked this people also asked this
  • Replies 5 replies
  • Subscribers 75 subscribers
  • Views 2149 views
  • Users 0 members are here
Attachments (13) Download All
Nordic Case Info
  • Case ID: 253168
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF5340 BLE mesh samples don't work properly

RAlexeev

I tried to launch your example "Bluetooth: Mesh Light" using nRF5340 PDK and I failed. I followed this guide developer.nordicsemi.com/.../README.html. Also I tried to launch an example "Bluetooth: Mesh" (docs.zephyrproject.org/.../README.html) using nRF5340 PDK and I failed. I wrote out all combinations of samples in a table below which I tried to build and run, but all of them didn't work properly. But when I built the sample "Bluetooth: Mesh Light" for nRF52840 DK, then everything worked properly. The problems occurred only in the case of nRF5340 PDK.

Firmwares for application core in rows and firmwares for network core in columns. Network core had firmware from sample /ncs/zephyr/samples/bluetooth/hci_rpmsg without any modification. Network core had firmware from sample /ncs/zephyr/samples/bluetooth/hci_rpmsg with modification according to note from developer.nordicsemi.com/.../README.html, adding two lines to prj.conf:
CONFIG_BT_CTLR_TX_BUFFER_SIZE=74
CONFIG_BT_CTLR_DATA_LENGTH_MAX=74
Application core had firmware from sample /ncs/nrf/samples/bluetooth/mesh/light without any modification. I followed this instruction developer.nordicsemi.com/.../README.html and after the second step I had such messages for some time:
Connecting...
Discovering services...
And a while it came back to a Scanner page. So I couldn't connect to nRF5340 PDK. It's output into UART:
Fullscreen uart_output_1.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
I: No ID address. App must call settings_load()
Bluetooth initialized
Mesh initialized
 I saw the following problem in output into UART:
Fullscreen uart_output_2.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
W: opcode 0x0c33 status 0x12
Bluetooth init failed (err -5)

Certainly, I couldn't even see a node in nRF Mesh Scanner.
Application core had firmware from sample /ncs/nrf/samples/bluetooth/mesh/light with modification according to note from developer.nordicsemi.com/.../README.html, adding two lines to prj.conf:
CONFIG_BT_CTLR_TX_BUFFER_SIZE=74
CONFIG_BT_CTLR_DATA_LENGTH_MAX=74		 I followed this instruction developer.nordicsemi.com/.../README.html and after the second step I had such messages for some time:
Connecting...
Discovering services...
And a while it came back to a Scanner page. So I couldn't connect to nRF5340 PDK. It's output into UART:
Fullscreen uart_output_3.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
I: No ID address. App must call settings_load()
Bluetooth initialized
Mesh initialized
 I saw the following problem in output into UART:
Fullscreen uart_output_10.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
W: opcode 0x0c33 status 0x12
Bluetooth init failed (err -5)

Certainly, I couldn't even see a node in nRF Mesh Scanner.
Application core had firmware from sample /ncs/zephyr/samples/bluetooth/mesh without any modification. I followed this instruction developer.nordicsemi.com/.../README.html and after the second step I had such messages for some time:
Connecting...
Discovering services...
And a while it came back to a Scanner page. So I couldn't connect to nRF5340 PDK. It's output into UART:
Fullscreen uart_output_4.txt Download 
[00:00:00.021,728] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
Bluetooth initialized
Mesh initialized
[00:00:00.021,728] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.3 Build 0
[00:00:00.022,460] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.049,346] <inf> bt_hci_core: Identity: eb:f6:da:7f:da:51 (random)
[00:00:00.049,377] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:00.049,377] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
[00:00:00.050,872] <dbg> bt_mesh_settings.mesh_commit: sub[0].net_idx 0xffff
[00:00:00.050,994] <inf> bt_mesh_prov: Device UUID: 00000000-0000-0000-0000-0000000~
 I saw the following problem in output into UART:
Fullscreen uart_output_5.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
[00:00:00.008,270] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.008,270] <inf> fs_nvs: alloc wra: 0, ff0
[00:00:00.008,270] <inf> fs_nvs: data wra: 0, 8
[00:00:00.019,317] <wrn> bt_hci_core: opcode 0x0c33 status 0x12
Bluetooth init failed (err -5)

Certainly, I couldn't even see a node in nRF Mesh Scanner.
Application core had firmware from sample /ncs/zephyr/samples/bluetooth/mesh with modification according to an answer from devzone.nordicsemi.com/.../254172, adding two lines to prj.conf:
CONFIG_BT_TINYCRYPT_ECC=y
CONFIG_BT_L2CAP_RX_MTU=69		 I followed this instruction developer.nordicsemi.com/.../README.html and after the second step I had such messages for some time:
Connecting...
Discovering services...
And a while it came back to a Scanner page. So I couldn't connect to nRF5340 PDK. It's output into UART:
Fullscreen uart_output_7.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
[00:00:00.008,270] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.008,270] <inf> fs_nvs: alloc wra: 0, fd0
[00:00:00.008,270] <inf> fs_nvs: data wra: 0, 2c
[00:00:00.021,484] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
Bluetooth initialized
Mesh initialized
[00:00:00.021,484] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.021,514] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.3 Build 0
[00:00:00.022,216] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.042,907] <inf> bt_hci_core: Identity: eb:f6:da:7f:da:51 (random)
[00:00:00.042,907] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:00.042,907] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
[00:00:00.044,403] <dbg> bt_mesh_settings.mesh_commit: sub[0].net_idx 0xffff
[00:00:00.044,494] <inf> bt_mesh_prov: Device UUID: 00000000-0000-0000-0000-0000000~
 I saw the following problem in output into UART:
Fullscreen uart_output_6.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
[00:00:00.008,270] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.008,270] <inf> fs_nvs: alloc wra: 0, ff0
[00:00:00.008,270] <inf> fs_nvs: data wra: 0, 8
[00:00:00.019,317] <wrn> bt_hci_core: opcode 0x0c33 status 0x12
Bluetooth init failed (err -5)

Certainly, I couldn't even see a node in nRF Mesh Scanner.
Application core had firmware from sample /ncs/zephyr/samples/bluetooth/mesh with modification according to note from developer.nordicsemi.com/.../README.html, adding two lines to prj.conf:
CONFIG_BT_CTLR_TX_BUFFER_SIZE=74
CONFIG_BT_CTLR_DATA_LENGTH_MAX=74		 I followed this instruction developer.nordicsemi.com/.../README.html and after the second step I had such messages for some time:
Connecting...
Discovering services...
And a while it came back to a Scanner page. So I couldn't connect to nRF5340 PDK. It's output into UART:
Fullscreen uart_output_8.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
[00:00:00.008,239] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.008,270] <inf> fs_nvs: alloc wra: 0, f90
[00:00:00.008,270] <inf> fs_nvs: data wra: 0, f4
[00:00:00.021,820] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
Bluetooth initialized
Mesh initialized
[00:00:00.021,820] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.021,820] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.3 Build 0
[00:00:00.022,552] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.038,055] <inf> bt_hci_core: Identity: eb:f6:da:7f:da:51 (random)
[00:00:00.038,085] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
[00:00:00.038,085] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff
[00:00:00.039,581] <dbg> bt_mesh_settings.mesh_commit: sub[0].net_idx 0xffff
[00:00:00.039,703] <inf> bt_mesh_prov: Device UUID: 00000000-0000-0000-0000-0000000~

I saw the following problem in output into UART:

Fullscreen uart_output_9.txt Download 
*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Initializing...
[00:00:00.008,270] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.008,270] <inf> fs_nvs: alloc wra: 0, ff0
[00:00:00.008,270] <inf> fs_nvs: data wra: 0, 0
[00:00:00.019,470] <wrn> bt_hci_core: opcode 0x0c33 status 0x12
Bluetooth init failed (err -5)

Certainly, I couldn't even see a node in nRF Mesh Scanner.

I used nRF Connect v3.4.1 Programmer to firmware a network core.

Explain to me, please, how to launch any sample of BLE mesh for nRF5340 PDK? Does the working sample exist at least?

Parents
  • 0

    Hi Roman, 

    We are working on your case and will reply later. 

    Please note that we are moving into the summer vacation period here in Norway, so it might take a bit longer to get to the bottom of this than expected, as staff during the month of July will be reduced. I'm sorry about the inconvenience, but please be patient. And I'll get back to you as soon as I hear something from the devs.

    -Amanda H.

Reply
  • 0

    Hi Roman, 

    We are working on your case and will reply later. 

    Please note that we are moving into the summer vacation period here in Norway, so it might take a bit longer to get to the bottom of this than expected, as staff during the month of July will be reduced. I'm sorry about the inconvenience, but please be patient. And I'll get back to you as soon as I hear something from the devs.

    -Amanda H.

Children
No Data
Related
Terms of service