wifi interface to nRF52840 SoCs for thread border router

[vinay Hasyagar]

Hi,

I am using nRF52840 SoC as a thread device in my application. I want to push data from sensors to cloud. So I need to configure one of my thread devices as border router. I went through the SDK document where it is mentioned that, nRF52840 SoC should be configured as NCP and it should be connected to a host processor (in your case its raspberry PI). 

   My problem is, in my application Raspberry Pi is not feasible. 

   Can I take any WiFi chip (EX: ESP32) and interface it to nRF52840 SoC via UART or SPI and make it work as Thread Border router?

   Is the Host Processor should be capable of running OS (Ex Linux)? 

  Also in the document you have mentioned that it is necessary to use wpantund which is a Linux Driver/Daemon. What does it do? If we don't use it then, does it affect the function of border router?

Please help me with this.

Thanks

[Jørgen Holmefjord]

Hi,

The border router is specified in the Thread specifications (see chapter 9 in Thread specifications v1.1.1). As long as you follow the specifications, there is nothing preventing you from implementing a border router with another device than the solution we provide. 

In addition to the Thread specifications, I would recommend you to have a look at the following resources from the Thread Group:

• Thread Border Routers Overview
• Thread Border Routers Best Practices

wpantund is a user-space network interface driver/daemon that provides a native IPv6 network interface to an NCP. It was written and developed by Nest Labs to better support Thread connectivity on Unix-like operating systems. It uses Spinel to communicate with an NCP.

Spinel is a general management protocol for enabling a host device to communicate with and manage an NCP. Initially designed to support Thread-based NCPs, Spinel has been designed with a layered approach that allows it to be easily adapted to other network technologies in the future.

If you want to create a border router in a non-unix system, you need to implement some alternative to wpantund, to interface the network interface to the Spinel communication of the NCP.

Best regards,
Jørgen