Member | Action | Date |
---|---|---|
![]() |
Replied
to
BLE Mesh, problems with dcd file
Hi Ward, You mentioned "After i did those changes and pressed on the generate button, I get some errors in the dcd file after building the code" What are those errors ? are they compiler errors or generation errors ? if yes, please post it here.
|
1 day ago |
![]() |
Updated
to
BLE Mesh, problems with dcd file
Hi Ward, You mentioned "After i did those changes and pressed on the generate button, I get some errors in the dcd file after building the code" What are those errors ? are they compiler errors or generation errors ? in any cases, please post the log info here.
|
1 day ago |
![]() |
Updated
to
BLE Mesh, problems with dcd file
Hi Ward, You mentioned "After i did those changes and pressed on the generate button, I get some errors in the dcd file after building the code" What are those errors ? are they compiler errors or generation errors ? in any cases, please post the log info here.
|
1 day ago |
![]() |
Replied to Bluetooth Knowledge Base Article List Show more |
13 days ago |
![]() |
Posted
KBA_BT_0519: Bluetooth Mesh ADK migration from 2.3.4 to 3.0.x on Bluetooth Wireless Knowledge Base
Bluetooth Mesh Mobile: ADK 2.3.4 -> 3.0.x migration1. IntroductionIn principle, the update of the Bluetooth Mesh Mobile ADK to the current branch does not differ from the previous releases. The changes applied were minor which resulted in preserving the backward compatibility. The main ones were:
Note: All of these updates have been listed in the Bluetooth Mesh Mobile ADK Release Notes document for the 3.0.x versions. 2. Library updateIn this section we will describe the procedure of exchanging the ADK packages in Customer's projects on both platforms. We will refer to the AN1200.1 section 4. Getting started. 2.1 iOSOn the iOS platform you need to follow the steps listed below:
It should be visible in Frameworks, Libraries and Embedded Content section with “Embed & Sign” chosen. Please also make sure that when using XCFrameworks you have disabled the Bitcode in the project by following the steps:
Note: The AN1200.1 in section 4.1 also provides a set of screenshots for better reference. 2.2 AndroidSteps for the Android platform environment can be found below:
Note: The AN1200.1 in section 4.2 also provides a set of screenshots for better reference. 3. Project updates requiredAs stated in the introduction the changes made to the method names and removal of the deprecated items in the ADK 3.0.0 may force the User to also update it's application project. It is necessary to look at the lists of changed items in the sections below and make sure you apply the corrections. 3.1 iOS3.1.1 Deprecated items removedNote:
3.1.2 Naming changes
3.1.3 Other API changes
3.2 Android3.2.1 Deprecated items removedNote:
3.2.2 Naming changes
3.2.3 Other changes
4. ConclusionWith the information listed in the above Document it should be possible for the Users to successfully switch an existing project based on the older ADK versions to the Bluetooth Mesh Mobile ADK 3.0.0. However, in case of any inclarities, please do not hesitate to contact us via a private support case or feel free to comment below. Warning: We would also like to highlight that for the best reliability we always recommend to use the Bluetooth Mesh Mobile ADK and Bluetooth Mesh Embedded SDK in combination from the same release. |
13 days ago |
![]() |
Replied
to
Mesh restart provisioning
Hi Richard, Have you tried to reinit the stack ? I mean by that reinit the mesh classes. Also which SDK are you using ? |
15 days ago |
![]() |
Replied
to
Bluetooth Mesh - After provisioning sl_btmesh_config_client_get_dcd fail
Hi Marco, I think the best at this point would be for you to create a support case and send me your project so I can have a look. One more thing, additionally to making sure the the config client model to your element is present on the provisioner, have you set the provisioning config properly ? Let me know
|
22 days ago |
![]() |
Replied
to
Computer not recognizing Silicon Thunderboard
Hi Omar,
when installing Studio, have you installed the Jlink USB driver ? |
23 days ago |
![]() |
Selected an answer for
Scene client Model api scene_ cmd_ mesh_ scene_ client_ store
please refer https://www.silabs.com/community/wireless/bluetooth/forum.topic.html/_-MHXT summary: it is now hard limit inside out stack, can't change. Scene server iterates through the models to sum up the required space for a single entry, of course the final sum is depending on the DCD. That part should be fine, but the number of scene entries is not configurable via the SDK, unfortunately. |
23 days ago |
![]() |
Replied
to
Bluetooth Mesh - After provisioning sl_btmesh_config_client_get_dcd fail
Hi Marco, I assume the snippet of code that you wrote there work as follow :
Is that correct ? Is this code running on provisioner ? This would be mandatory as a config client model has to be supported. You mentioned "Sometimes the provisioning works" can you elaborate a bit on that versus when it fails ? |
23 days ago |