search

ARMmbed / mbed-os

Arm Mbed OS is a platform operating system designed for the internet of things
https://mbed.com
Other
4.67k stars 2.97k forks source link

STM32WB55, mesh API - Zigbee and Thread protocol #13624

Closed pawelm87 closed 2 years ago

pawelm87 commented 4 years ago

Description of defect

My issue is kind of question/problem with the mesh api. Please don't delete it, I have not found place to describe it.

I want implement Mesh network (Zigbee or Thread protocols) based on STM32WB55 because ST gives all stacks. To do it I need mesh api for Thread and ZigBee for test.

Mesh API on the mbed site is not available. The below links redirect to 404 error page: From https://os.mbed.com/docs/mbed-os/v6.3/apis/6LoWPAN-ND-tech.html To connect to the 6LoWPAN-ND network, use the 6LoWPAN-ND interface API. From the information on this page it appears that 6LoWPAN-ND interface is the ZIgBEE protocol.

From page https://os.mbed.com/docs/mbed-os/v6.3/apis/wisun-tech.html To connect to the Wi-SUN network, use the Wi-SUN interface API.

Where can I find API for Thread protocol ? MeshInterface hierarchy refers to 3 mesh interfaces, also to ThreadInterface, but nowhere is not documentation, api, anything. mesh

Target(s) affected by this defect ?

STM32WB55

Toolchain(s) (name and version) displaying this defect ?

Mbed Studio 1.2.1

What version of Mbed-os are you using (tag or sha) ?

mbed-os 5.14.1 and mbed-os 6.2.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

The latest

How is this defect reproduced ?

None

Best

ciarmcom commented 4 years ago

@pawelm87 thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided. Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de or a single valid release tag of the form mbed-os-x.y.z . E.g. '6.2' has not been matched as a valid tag or sha. NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered. Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

pawelm87 commented 4 years ago

@ciarmcom I updated what you asked for.

0xc0170 commented 4 years ago

@artokin would you be able to help?

artokin commented 4 years ago

Mesh API on the mbed site is not available. The below links redirect to 404 error page: From https://os.mbed.com/docs/mbed-os/v6.3/apis/6LoWPAN-ND-tech.htmlpage

There seems to be additional "page" in the URL, the correct URL would be: https://os.mbed.com/docs/mbed-os/v6.3/apis/6LoWPAN-ND-tech.html

TuomoHautamaki commented 4 years ago

I'll clarify the question related to Thread. I'll get back to this..

pawelm87 commented 4 years ago

@artokin my mistake but this is not the issues, on page is link to API to 6LoWPAN-ND protocol and this link redirect to 404 error page

https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed-mesh-api/LoWPANNDInterface.h

https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed-mesh-api/WisunInterface.h

where can I find describe the API for this two protocols ?

artokin commented 4 years ago

I'm sorry, the directory structure has changed in Mbed OS 6 and those links are pointing to the older version of Mbed OS (mbed-os-5.15). Those files are now located in : https://github.com/ARMmbed/mbed-os/tree/master/connectivity/nanostack/mbed-mesh-api/mbed-mesh-api

We will fix the documentation in the near future.

pawelm87 commented 4 years ago

@artokin thank you for help, Will these API work with STM32WB55 which has official ZigBee and Thread stack ?

I found a few example dedicated for mesh network : https://github.com/ARMmbed/mbed-os-example-mesh-minimal https://os.mbed.com/docs/mbed-os/v5.14/apis/mesh-api.html https://github.com/ARMmbed/nanostack-border-router

But in above examples API was usage in different way :(

@TuomoHautamaki can you told about Thread protocol at mbed, may you have examples ?

artokin commented 4 years ago

We have not used STM32WB55 in our development. I'm not sure if Nanostack RF drivers (https://github.com/ARMmbed/mbed-os/tree/master/connectivity/drivers/802.15.4_RF) can directly work with that board.

nanostack-border-router is using nanostack (https://github.com/ARMmbed/mbed-os/tree/master/connectivity/nanostack/sal-stack-nanostack/nanostack) C-API's directly. The purpose of mbed-mesh-api is to hide complexity of Nanostack API's so that applications are easier to build. Therefore mbed-os-example-mesh-minimal is using mbed-mesh-api that is written in C++ and is also documented Mbed OS docs.

pawelm87 commented 4 years ago

unfortunately example-mesh-minimal not work with STM32WB55:

Error: L6218E: Undefined symbol NanostackRfPhy::get_default_instance() (referred from BUILD/NUCLEO_WB55RG/ARMC6/mbed-os/features/nanostack/mbed-mesh-api/source/LoWPANNDInterface.o).

@artokin or @LMESTM whether there are plans to add NanostackRfPhy support for this chip by ST or mbed ?

TuomoHautamaki commented 4 years ago

@pawelm87 my apologies for the slow responses and I still need to pass this further to the right people. @andypowers Pawel is having questions related to mbed OS and Thread connectivity protocols support. Can you check and comment. Thanks

ciarmcom commented 4 years ago

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2146

ciarmcom commented 2 years ago

We closed this issue because it has been inactive for quite some time and we believe it to be low priority. If you think that the priority should be higher, then please reopen with your justification for increasing the priority.