• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 57 subscribers
  • Views 2568 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.

When will we see some docs for using OpenThread + CC26xx / CC13xx

mike snyder
Intellectual 945 points

Other Parts Discussed in Thread: CC2538

Hi e2e. I know this is a fairly new announcement about openthread.

TI - do you have an approximate time frame for openthread integration? Will this be used with TI RTOS? 

I have about 20 more questions, but I will start with those 2. 

Thanks!

  • 0
    Guru 735695 points
    To know about Thread status or road map from TI, I suggest you to contact TI local representative.
  • 0
    Prodigy 30 points

    Hi All,

    It's great to hear that TI is supporting openthread. I Have just compiled thread cli app for CC2538Dk, it is working fine as stated in openthread Wiki. I want to implement CoAP on cc2538dk by using opnethread, can any one help me in this regards

    1. by sharing how to documents or giving any idea how to achieve it.

    2. How openthread border router can be implemented, is there any document to do so, Let me Know?

    Thanks in Advance for your help or Ideas.

    Cheers,

    Praveen K

  • 0 in reply to PRAVEEN KAMMA
    Guru 735695 points
    As I know, there's no such document available. However, openthread API can do UDP send and receive so you can use it to implement COAP by yourself.
  • 0 in reply to PRAVEEN KAMMA
    TI__Prodigy 220 points

    Hey Praveen,

    Currently the CoAP server object in OpenThread only implements the subset of the protocol that is necessary for Thread Commissioning. You will have to open up a new port with a new CoAP server object to service the requests you are sending to the embedded device. If the functionality for the command is not present in the current CoAP implementation you may need to extend the *.cpp files in `src/core/coap` . You may want to take a look at the joiner and commissioner code in `src/core/meshcop/` to see how they are extending the Commissioning CoAP server to service certain requests.


    A border router can be created with a cc2538 running the ncp example and a linux machine running wpantund. A startup guide from Nest can be found here: https://github.com/openthread/wpantund/blob/master/INSTALL.md#wpantund-installation-guide

  • 0 in reply to Seth Rickard
    Prodigy 30 points

    Thanks Sickard, I have tried by running ncp on cc2538dk and wpantund on ubuntu pc. i am unable to creat it as border router, please share me the guide to implement border router. I think i may be missing any configurations in openthread code for border router.

    Thanks for your well guided response.

    with regards,

    Praveen Kumar Kamma.

  • 0 in reply to PRAVEEN KAMMA
    TI__Prodigy 220 points

    Hey Praveen,

    We do not currently have any collateral for creating a Border Router. The Thread Group is still debating on what the best practices are for Border Router behavior.

    If you can bring the Network CoProcessor up with wpantund you should be able to configure it with wpanctl. If you can get the NCP on a Thread network you should be able to see an interface with a name like `wpan0` when you run ifconfig in the Linux terminal.

    Once you have the interface you can ping on the network by specifying the iface for ping, like

    ping6 -I wpan0 ff02::1

    which will send an ICMPv6 packet on the interface `wpan0` to the link local all routers multicast address.

    From there you can use wpanctl to make sure the NCP is a router and add a default global prefix for the nodes on the network.

    You will then need to configure the Linux net subsystem to forward traffic from one iface to another, and probably generate router advertisements. I found this page helpful: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/

    This would offer you an IPv6 bridge onto the Thread network from another IPv6 network. You can then send datagrams to endpoints on the Thread network from endpoints another IPv6 network, and vice versa.

    What constitutes a Border Router is still up in the air, questions about mDNS vs CoAP for discovery and 6to4 translation have yet to be settled.