This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Using CLI to communicate end device from BorderRouter

 <install folder>\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8.zip\examples\thread\cli\ftd\usb\hex   

Need to get confirmation on if I follow the above path and flash the binary in nrf52840 dongle[Other than that I connected with RaspberryPi] and connect it to BorderRouter [Raspbery pi flashed with nordic alpha 4.1.0.1 image + nrf52840 dongle in NCP design]. 

Can I use CLI and communicate  with the end device that is connected in a network?

And also need to know if I flash the above mentioned binary in same dongle with OT stack, will that allow me to open CLI.

If not, need to know the all possible ways to communicate to end device from BorderRouter CLI.

Parents
  • Hi Umamaheswarreddy,

    Need to get confirmation on if I follow the above path and flash the binary in nrf52840 dongle[Other than that I connected with RaspberryPi] and connect it to BorderRouter [Raspbery pi flashed with nordic alpha 4.1.0.1 image + nrf52840 dongle in NCP design]. 

    Can I use CLI and communicate  with the end device that is connected in a network?

     Yes. the device running CLI example itself is an end device that you can set up manually to connect another end device and created or join a Thread network. You can send a command through a serial terminal on Windows, Linux, or Mac. It of course can be your raspberry pi which is used as a BorderRounter, but your BorderRounter must have an NCP device running specific NCP firmware. The NCP device provides an 802,15.4 PHY and MAC layer hardware and OT stack needed by Thread protocol. 

    And also need to know if I flash the above mentioned binary in same dongle with OT stack, will that allow me to open CLI.

     The CLI example already has an OT stack, if you flash the CLI example to the dongle, the former program in the same dongle will be erased or covered.

    If not, need to know the all possible ways to communicate to end device from BorderRouter CLI.

     The first answer has explained the concepts. I also want to remind you that a BorderRouter is used to build the bridge for the internal Thread network and external Internet, it is not necessary if you only want to communicate with an end device in a Thread network.

    Best regard,

    Charlie

     

  • Thanks for the reply Charlie,

     Yes. the device running CLI example itself is an end device that you can set up manually to connect another end device and created or join a Thread network.

    I don't need one more device to be connected as end device but, my main aim is to make BorderRouter up and a device to connect to the network and ensure that there's communication between them.

    For that I have Raspbery pi flashed with nordic alpha 4.1.0.1 image + nrf52840 dongle in NCP design .

    As an end device I have EFR32 MG12 WSTK flashed with OT-CLI-FTD code and connected to the BorderRouter as a child.

    Now I need to communicate to EFR32 from BorderRouter, guess we can communicate using CLI from BorderRouter[raspberry Pi]. But in my case as I have flashed Alpha 4.1.0.1 image for BorderRouter and it doesn't have CLI within it, want to know how to communicate and for communication what all need to be done. 

    I thought of blinking LED with command from BorderRouter, will that work with current setup, If not what do I need and if there's someother way that we can demo it's communication, please let me know.

  • Hi Umamaheswarreddy,

    Let me explain what is CLI. The nordic CLI example is basically OT stack + Command Line Interface(CLI). CLI is only the interface for you to send commands to configure an end device for its OT stack. These supported commands are only for this specific usage.

    When the end devices are connected, you would be able to use TCP/UDP protocol based on this connected IPv6 network. If the EFR32 MG12 WSTK has examples like a CoAP server, you can build a CoAP client on your BorderRouter through some tools,  and send commands to control the CoAPserver. CoAP is an application protocol based on UDP. You can also use bare TCP/UDP to transfer the command to the target device.

    Best regards,

    Charlie

  • It seems all the examples provided requires DK only but I have dongle that is connected to Rasoberry Pi and EFR32 Board.

    Is the demo possible with my current setup?

    If not what do I need in extra and how to demo?

Reply Children
Related