• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 500 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.

Linux/CC1310: how to recover normal communication state after the re-power of the co-processor?

Emma Wang
Expert 5200 points
Part Number: CC1310

Tool/software: Linux

The customer is using the node: simplelink_cc13x0_sdk_2_10_00_36\ti154stack\sensor

 

the Linux-SDK:

http://www.ti.com/tool/ti-15.4-stack-gateway-linux-sdk?keyMatch=15.4%20linux&tisearch=Search-EN-Everything

 

 

now they are using the second mode

Question description:

 

When the normal communication is maintained, the power of the Coprocessor device is disconnected. When the node uploads the data packet, the node becomes an orphan state because no response is received, and the node sends a packet of a solo state periodically.

 

After the Co-processor is powered on again, it is found that even though a packet of a solitary state is received, the corresponding short address cannot be found through the address of the broadcast packet in the NV, resulting in unable to generate an acknowledgement to a packet for a solo state. And the node is still in an orphan state. We found it through the Linux application.

The question is: What can do to recover normal communication ?


  • 0
    TI__Genius 12415 points
    Hi,

    Is NV_RESTORE defined in the make file for the project?

    Also if the co-processor is the only one getting powered off you need to make sure that it gets initialized properly again. The co-processor by itself does not hold any configuration given that the NV is stored in the linux host processor and not in the co-processor. when it comes to the linux SDK it might be a problem to power off only the co-processor since when this is done there is a high chance that the co-processor will be assigned a new serial port which the collector application is not aware of and the application will have to be restarted configured to open the new serial port.

    Regards,
    Hector