ERROR RUNNING MESH CHAT EXAMPLE ON NRF7002DK

[Kha Tran]

I've been trying to run the example Mesh/Chat on NRF7002DK, and the terminal print <err> bt_mesh_pb_adv: Failed enabling advertiser and <err> bt_mesh_pb_gatt: Failed enabling advertiser. I've seen the issue nRF5340-DK và trò chuyện lưới Bluetooth cũample. - Hỏi & Đáp Bắc Âu - Nordic DevZone - Nordic DevZone --- nRF5340-DK and Bluetooth mesh chat example. - Nordic Q&A - Nordic DevZone - Nordic DevZone but it dont work either. Can any one know  how to fix this? Pls help me cuz I'm currently working on my seminar final project 

[Kha Tran]

*********************************
* Running CMake for chat_7002dk *
*********************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/nordic/myApps/chat_7002dk
-- CMake version: 3.21.0
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/ncs/v2.8.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf7002dk, qualifiers: nrf5340/cpuapp
-- Found host-tools: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/2d382dcd92/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.8.0/zephyr/boards/nordic/nrf7002dk/nrf7002dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/nordic/myApps/chat_7002dk/build/chat_7002dk/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/nordic/myApps/chat_7002dk/build/chat_7002dk/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/nordic/myApps/chat_7002dk/build/chat_7002dk/zephyr/dts.cmake

warning: The choice symbol BT_LL_SW_SPLIT (defined at subsys/bluetooth\controller/Kconfig:139) was
selected (set =y), but no symbol ended up as the choice selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_BT_LL_SW_SPLIT and/or look up
BT_LL_SW_SPLIT in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: Deprecated symbol BOARD_ENABLE_CPUNET is enabled.

[Vidar Berg]

Hello,

BT_LL_SW_SPLIT selects the Zephyr Bluetooth controller instead of the Softdevice controller which the mesh samples are testet with. Instead of trying enable use this controller, please copy the sysbuild folder here: https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/mesh/light_ctrl/sysbuild to your project root directory and do a pristine build. This folder contains mesh specific configuration settings for the Softdevice controller.

Best regards,

Vidar 

[Vidar Berg]

Hi,

Build target needs to be nrf7002dk/nrf5340/cpuapp. Please try that and let me know if you still experience problems. 

[Kha Tran]

Hi Vidar, your tutorials worked!! But unfortunatedly I ran into new trouble After i flash the program to board nrf7002dk, I use my phone to provision it and it disconected after I press the Provision button 

[Vidar Berg]

Hi, good to hear that this resolved the build issues. As you know, this particular project has not been configured or tested with the nRF5340, and it apparently requires some additional configuration changes to work. Please try to increase the CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE in your project configuration and see if that helps. 

You can add the line below to your prj.conf and see if you still get the assertion afterward.

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

[Kha Tran]

Hi Vidar, I've tried your solution and it seems not work for me, can you have a look at it? (I also tried CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=8192)

[Vidar Berg]

Hi, have you made any modifications to the original sample project besides adding the 'sysbuild' directory as I suggested? A coworker of mine tested with both v2.8 and v2.9.1 using nRF7002DK rev. 1.0.3 but was unable to reproduce this assertion.

Either way, please try the same with SDK v2.9.1 and see if that works for you.