• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 56 subscribers
  • Views 298 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.

CC2652PSIP: Thread communication using CC2652PSIP

MTX tvm
Prodigy 30 points
Part Number: CC2652PSIP

Hi,

We are designing an IOT products using thread network. The chip using is CC2652PSIP. I checked the example projects like Cli_FTD, Doorlock, Shade etc and is working fine. I have some doubts and requirements and is listed below:

1) I wants to exchange data between two nodes. For example If I press a switch , data must be transferred from one node to another. Does data transfer  is only possible using CoAP functionality ???. Is there any other methods for transferring data

2) In CLI_FTD example the uplink up,thread, CoAp etc are started by entering commands in the terminal. In my application, when I turn ON FTD node , he said services must be started without entering the command in the terminal. What are the procedures,steps and API's for starting the services.

3) In MTD node, I tried different print functions to output text messages on the terminal.But none of them are printing . What are the API's used for printing messages in the terminal.

Thanks

  • 0
    TI__Guru**** 217507 points

    Hi MTX,

    1) You can use the ping command, see the Thread CLI Project Zero for more information.

    2) The purpose of the CLI examples is to provide a Command Line Interface and not make assumptions about the thread network startup operation.  You can consider the RCP combined with the Linux Border Router to automate the process.

    3) How are you trying to print functions and which MTD project are you using?  Application examples already implement a Common User Interface (CUI) and the CLI UART is dedicated towards command line execution.  Are you enabling a second UART2 peripheral and using it towards debug printing?  This would have to use a secondary UART connection other than the backchannel XDS110.

    Regards,
    Ryan

  • 0
    TI__Mastermind 35030 points

    Hi MTX,

    Agreed with Ryan here.

    Additionally, please note that Thread is analogous to IP (it implements IPv6 over 802.15.4).

    It is up to application interpretation of the bytes.

    CoAP is one such application layer.

    Thanks,
    Toby