This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Coexist Mesh SDK 2.1.1 + nrf SDK 15 ble_app_uart ,the GATT open mesh does not work

Nordic Team,

sdk:mesh sdk 2.1.1 + nRF5_SDK_15.0.0

Reference ble_app_uart_coexist example. Coexistence provisioner + ble_app_uart

Initialize:

#define APP_ADV_INTERVAL                800 
int main(void)
{
    bool erase_bonds;
    uart_init();
    log_init();
    timers_init();
    buttons_leds_init(&erase_bonds);
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    services_init();
    advertising_init();
    conn_params_init();

    // Start execution.
    printf("\r\nUART started.\r\n");
    NRF_LOG_INFO("Debug logging for UART over RTT started.");
    mesh_main_init();
    advertising_start();
    mesh_main_start();
}    

the provisioner cannot scan server

<t:         25>, mesh_main.c,  710, ----- BLE Mesh Light Switch Provisioner Demo -----
<t:        570>, mesh_main.c,  639, Initializing and adding models
<t:        588>, mesh_main.c,  692, Setup defaults: Adding keys, addresses, and bindings 
<t:        779>, provisioner_helper.c,  336, netkey_handle: 0
<t:       1223>, mesh_main.c,  739, <start> 
<t:       1227>, mesh_main.c,  726, Starting application ...
<t:       1232>, mesh_main.c,  728, Provisoned Nodes: 0, Configured Nodes: 0 Next Address: 0x0100
<t:       1238>, mesh_main.c,  729, Dev key : 46621EA8155AC9C7280F994AF21A8646
<t:       1243>, mesh_main.c,  730, Net key : 1114817C45766C32A04668DB65382055
<t:       1249>, mesh_main.c,  731, App key : 127CBE674B5E705399A12A8FECF0CCD3
<t:       1254>, mesh_main.c,  732, <t:     144514>, mesh_main.c,  500, Button 1 pressed
<t:     144518>, mesh_main.c,  404, Waiting for Server node to be provisioned ...
<t:     149627>, provisioner_helper.c,  288, Scanning For Unprovisioned Devices

comment out :

//advertising_start();

<t:         24>, mesh_main.c,  710, ----- BLE Mesh Light Switch Provisioner Demo -----
<t:        601>, mesh_main.c,  639, Initializing and adding models
<t:        621>, mesh_main.c,  692, Setup defaults: Adding keys, addresses, and bindings 
<t:        822>, provisioner_helper.c,  336, netkey_handle: 0
<t:        837>, mesh_main.c,  739, <start> 
<t:        841>, mesh_main.c,  726, Starting application ...
<t:        846>, mesh_main.c,  728, Provisoned Nodes: 0, Configured Nodes: 0 Next Address: 0x0100
<t:        852>, mesh_main.c,  729, Dev key : 1086CD369B9057BEE0243469DB9F18B6
<t:        857>, mesh_main.c,  730, Net key : EC20A1D51E999EF6EB2AF4BDABA0D564
<t:        862>, mesh_main.c,  731, App key : 5E2D01FFB1E78BDF8F71FE3109E3C7FE
<t:      61025>, mesh_main.c,  500, Button 1 pressed
<t:      61029>, mesh_main.c,  404, Waiting for Server node to be provisioned ...
<t:      66162>, provisioner_helper.c,  288, Scanning For Unprovisioned Devices
<t:      94880>, provisioner_helper.c,  145, UUID seen: 0059FFFF00000000C0F47E06363D6194
<t:      94886>, provisioner_helper.c,   97, UUID filter matched
<t:      95529>, provisioner_helper.c,  265, Provisioning link established
<t:     108107>, provisioner_helper.c,  260, Static authentication data provided
<t:     120448>, provisioner_helper.c,  192, Provisioning completed received
<t:     120453>, provisioner_helper.c,  197, Adding device address, and device keys
<t:     120460>, provisioner_helper.c,  220, Addr: 0x0100 addr_handle: 1 netkey_handle: 0 devkey_handle: 1
<t:     123955>, provisioner_helper.c,  156, Local provisioning link closed: prov_state: 2  remaining retries: 2
<t:     123962>, mesh_main.c,  313, Provisioning successful
<t:     123966>, provisioner_helper.c,  182, Provisioning complete. Node addr: 0x0100 elements: 1
<t:     123972>, node_setup.c,  713, Configuring Node: 0x0100
<t:     123977>, node_setup.c,  627, Config client setup: devkey_handle:1 addr_handle:1
<t:     123983>, node_setup.c,  383, Getting composition data
<t:     126788>, mesh_main.c,  362, Config client event
<t:     126793>, node_setup.c,  393, Adding appkey
<t:     130487>, mesh_main.c,  362, Config client event
<t:     130492>, node_setup.c,  289, opcode status field: 0 
<t:     130497>, node_setup.c,  404, App key bind: Health server
<t:     131222>, mesh_main.c,  362, Config client event
<t:     131227>, node_setup.c,  289, opcode status field: 0 
<t:     131231>, node_setup.c,  419, App key bind: Simple On/Off server
<t:     132106>, mesh_main.c,  362, Config client event
<t:     132110>, node_setup.c,  289, opcode status field: 0 
<t:     132115>, node_setup.c,  472, Setting publication address for the health server to 0x0001
<t:     135503>, mesh_main.c,  362, Config client event
<t:     135507>, node_setup.c,  289, opcode status field: 0 
<t:     135512>, node_setup.c,  510, Adding subscription
<t:     137102>, mesh_main.c,  362, Config client event
<t:     137107>, node_setup.c,  289, opcode status field: 0 
<t:     137111>, mesh_main.c,  273, Configuration of device 0 successful
<t:     137117>, provisioner_helper.c,  288, Scanning For Unprovisioned Devices

In mesh sdk1.0.1 +sdk 14.2 no such problem.How do I change it?

Parents
  • Did you take a look at the readme located here: nrf5_SDK_for_Mesh_v2.1.1_src\examples\sdk_coexist\ble_app_uart_coexist? I noticed a few bugs in the sdk_coexist uart example that were reported internally. 

    How are you currently testing this example? Are you using the regular provisioner, the client ble_app_uart coexist example & a regular mesh light switch server example?

  • Hi Bjorn,

    thank you for your reply!

    provisioner example:“nrf5_SDK_for_Mesh_v2.1.1_src\examples\light_switch\provisioner”

    server example:“nrf5_SDK_for_Mesh_v2.1.1_src\examples\light_switch\server”

    ble_app_uart_coexist example: "nrf5_SDK_for_Mesh_v2.1.1_src\examples\sdk_coexist\ble_app_uart_coexist"

    Refer to the README.md file, the ble_app_uart_coexist example works fine

    Then refer to ble_app_uart_coexist example

    I want coexist the provisioner exapmle and ble_app_uart example in the nRF5_SDK_15.0.0

    start advertising, mesh can not scan to the server

    but stop advertising working fine

    GATT and MESH can't work together

    What other bugs have been discovered? I am going to develop products on this sdk.

     

Reply
  • Hi Bjorn,

    thank you for your reply!

    provisioner example:“nrf5_SDK_for_Mesh_v2.1.1_src\examples\light_switch\provisioner”

    server example:“nrf5_SDK_for_Mesh_v2.1.1_src\examples\light_switch\server”

    ble_app_uart_coexist example: "nrf5_SDK_for_Mesh_v2.1.1_src\examples\sdk_coexist\ble_app_uart_coexist"

    Refer to the README.md file, the ble_app_uart_coexist example works fine

    Then refer to ble_app_uart_coexist example

    I want coexist the provisioner exapmle and ble_app_uart example in the nRF5_SDK_15.0.0

    start advertising, mesh can not scan to the server

    but stop advertising working fine

    GATT and MESH can't work together

    What other bugs have been discovered? I am going to develop products on this sdk.

     

Children
Related