Yes, NCS supports thread, see the Working with Thread article. There are three OpenThread samples, which you can find here. A CLI sample, CoAP Client sample and CoAP Server sample. The source code can be found here.
1) Which SDK is better for thread protocol Connect SDK or Thread SDK ?
There are pros and cons with both. nRF Connect SDK is based on the ROTS Zephyr, so you get all the benefits of this. However, the Thread library in NCS is still under development so there are still few samples and not a lot of resources available to help you. The nRF5 Thread and Zigbee SDK has many more samples, so creating an application will be less work.
Bhavit Rajput said:
2) If I'll use Thread SDK then is it possible to use zephyr rtos with that?
No, I don't think so.
Bhavit Rajput said:
3) I want to implement border router and all other things related to Thread but examples are not available in Connect SDK for that.
Yes, exactly my point. There are more examples available in the nRF5 Thread SDK, while if you go with the NCS Thread Library you will have to write a lot of your application yourself.
1. For questions about the timeline I'll have to direct you to your Regional Sales Manager. Send me a PM with your location and I'll send you their contact info.
2. The Stack/API for OpenThread is the same for both, so in that sense it should be easy to port. But in the nRF5 SDK there are a few examples and functions that aren't available in Zephyr / NCS.
Yes, this is possible, but it's not something we provide.
The border router consists of both a Raspberry Pi and (in your case) an nRF52840 dongle (Thread Border Router). The firmware running on the Raspberry Pi is provided in the Thread SDK, pre-built and ready-to-use as a binary image.
It is possible to replace the Raspberry Pi with a driver on your computer to do the same thing, but you would have to write this yourself, and Nordic wouldn't provide support for it.
