• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 51 subscribers
  • Views 204 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-EM-CC2745R10-Q1: Zephyr ble mesh shell

Munan Xu
Expert 5770 points

Part Number: LP-EM-CC2745R10-Q1
Other Parts Discussed in Thread: CC2745R10-Q1

Hello,

Has anyone ever tried running the bluetooth mesh shell test in zephyr? I'd like to use this to debug a ble mesh application/ friendship establishment with an existing product since it doesn't require me to rebuild the application every time I want to change a behvior, and it allows for more flexibility in configuration.

 

When I flash and run the test it immediately crashes before getting to any kind of print or terminal.

In the build process for this project it does warn about some configurations that are expected to be enabled but I thought you would at least get to a prompt since the bluetooth stack does not get configured until you bring it up in the shell.

warning: BT_CTLR_DUP_FILTER_LEN (defined at subsys/bluetooth/controller/Kconfig:170) was assigned
the value '0' but got the value ''. Check these unsatisfied dependencies: BT_LL_SW_SPLIT (=n),
BT_CTLR (=n). See docs.zephyrproject.org/.../kconfig.html
and/or look up BT_CTLR_DUP_FILTER_LEN 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: BT_CTLR_ADVANCED_FEATURES (defined at subsys/bluetooth/controller/Kconfig.ll_sw_split:281)
was assigned the value 'y' but got the value 'n'. Check these unsatisfied dependencies:
BT_LL_SW_SPLIT (=n), BT_CTLR (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BT_CTLR_ADVANCED_FEATURES 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.

 

Also I had to add 

CONFIG_BT_LONG_WQ=y
 
to the prj.conf since otherwise the project would not build at all.
 
Originally I tried this on LP_EM_CC2340R53, but had to cut down the stack sizes way down to even get the linker to make everything fit on the device. It also immediately crashes, so I thought maybe it was a stack overflow thing and moved to the LP_EM_CC2745R10-Q1 as a higher memory option but no dice apparently.
 
Munan
  • 0
    TI__Genius 16825 points

    Hello Munan,

    Would you mind specifying what Zephyr version/tag you are using from our repository?: https://github.com/TexasInstruments/simplelink-zephyr

    BR,

    David

  • 0 in reply to David
    TI__Expert 5770 points

    Hi David,

    I'm currently on the previous ea release:

    TexasInstruments/simplelink-zephyr at v3.7.0-ti-9.14.00_ea

    Munan

  • 0 in reply to Munan Xu
    TI__Genius 16825 points

    Hello Munan,

    Thanks. I have reproduced you issue and currently looking into it.

    Let me come back to you asap.

    BR,

    David.

  • 0 in reply to David
    TI__Genius 16825 points

    Hello Munan,

    I am requesting support from the team who worked on this. The standard mesh sample has been tested, but the mesh shell (which is substantially heavier) needs further validation on the CC27xx. For instance, there are no board-specific overlay for CC27xx in the mesh shell sample.

    I am working on creating one and testing.

    Add a board-specific overlay to samples/bluetooth/mesh/boards/lp_em_cc2745r10_q1.conf                                                                                                          
        CONFIG_BT_LONG_WQ=y                                                                                                                                                                       
        CONFIG_BT_LONG_WQ_STACK_SIZE=2048                                                                                                                                                         
        CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096                                                                                                                                                   
        CONFIG_SHELL_STACK_SIZE=4096                                                                                                                                                              
        CONFIG_BT_RX_STACK_SIZE=2048                                                                                                                                                              
        CONFIG_MAIN_STACK_SIZE=2048   

    Best Regards,

    David