BLE Mesh Initialization

Can’t get the mesh demo working. We get the following in the debug console:


Mesh FW built at 14:43:29 on May 28 2018

SERVER

Clock = 26Mhz

UUID = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff

Random Address = ff:ff:ff:ff:ff:ff

Security = 1, current node state = 0, friend = 3

 

Generated Device public key (BE)


 

We can see the device in the nRF Connect BLE Android app, but not in the Toshiba mesh app, probably because the address is not initializing properly. We loaded the standalone beacon demo firmware just to make sure the board was ok, and it used the correct Bluetooth address and worked fine.

 

Is the problem that the mesh demo is designed for the Toshiba board pictured?

6replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Is the problem that the mesh demo is designed for the Toshiba board pictured?

    Just to make sure: on which board did you try to run the demo? The PAN1760A USB stick?

    We loaded the standalone beacon demo firmware just to make sure the board was ok, and it used the correct Bluetooth address and worked fine.

    The Bluetooth device address is definitely wrong.

    The Bluetooth Mesh application does not take the address from the pre-programmed flash area, but from the mesh node configuration area instead.

    Can you give more some more details, please?

    Which version of the Bluetooth Mesh SDK are you using?

    Did you follow any steps to configure the mesh node using the HCI tester application?

    Reply Like
  • Hi Michael,

    Kyle posted on my behalf, and I can follow up.

    Just to make sure: on which board did you try to run the demo? The PAN1760A USB stick?

    This is correct.

    Can you give more some more details, please?

    Which version of the Bluetooth Mesh SDK are you using?

    I used the EasyStandalone tool to configure the PAN1760A USB stick for debugging and loaded this file:

    toshiba_bt_mesh_20180528\software\bt_mesh_standalone_application\projects\TC35678_server_application\TC35678_Server_App\Exe\project.hex

    Did you follow any steps to configure the mesh node using the HCI tester application?

    I am not familiar with the HCI tester application. Can you please elaborate?

    Thanks

    Reply Like
  • Please refer to TC35678_BT_Mesh_User_Manual.pdf

    In section 2.2 Preparation in step 2 it says:

    Write firmware and configuration parameters to NVM. See SW development guide.

    You are currently missing this step.

    In TC35678_BT_Mesh_SW_Development_Guide.pdf the procedure is explained in section 3.4.5 Software Setup.

    You can use the pre-written scripts from \toshiba_bt_mesh_20180528\tools\hci_scripts\ as a basis, but you need to adopt them to your configuration.

    The layout of these script files is explained in 5. NVM Mapping and Configuration, the legend on page 23/30 explains where the Bluetooth Device address needs to be put.

    Reply Like
  • Thank you. I figured out how to set up one board as a mesh-client and one as a mesh-server and was able to provision and talk to the server board.

    Is it possible with the server library to make the relay nodes also proxies? I tried modifying the server HCI script to enable the proxy_support bit in the sDevice_features struct, but I wasn't able to see the board directly through the app. My application requires users to be able to connect to a mesh network through any board without having dedicated proxy-server/mesh-client boards.

    Reply Like
  • Thank you for your help, Michael.

    Reply Like
reply to topic
Like Follow
  • Status Answered
  • 2 mths agoLast active
  • 6Replies
  • 101Views
  • 3 Following