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

CCS/CC1312R: CC13x0 SimpleLink™ TI 15.4-Stack 2.x.x Embedded

Amr Kassab
Prodigy 50 points

Part Number: CC1312R
Other Parts Discussed in Thread: TIDA-010024

Tool/software: Code Composer Studio

I am currently working on intermediate FH non-sleepy nodes using a cc1312 Ti stack. When I try to force the node to enter the sleep mode after a successful packet transmission, I was unable to unicast between the root and the node after waking up. (although the broadcast is still working through keepalive). Could you please explain why this happened? 
In other words, it seems that broadcast Tx keeps synchronized after waking up but the unicast is not, is there any way to resynchronize the unicast Tx? Thanks
  • 0
    TI__Guru* 87831 points

    Hi Arm

    I will assign something to look into this. In the meantime, can you provide information regarding what HW you are running on, what SDK version you are using, and what code examples you are using?

    BR

    Siri

  • 0 in reply to Siri
    Prodigy 50 points

    Hi Sir,

    Thanks a lot for your prompt reply.

    The SDK I am using is: simplelink_cc13x2_26x2_sdk_2_40_00_81

    with cc1312

    Example: 6lowpan mesh TI 15.4 cc1312 Tirtos ccs

  • 0 in reply to Amr Kassab
    TI__Intellectual 1135 points

    Hi Amr,

    Are you using the example given in the TIDA-010024?

    If yes, which mode are you currently running and what changes have you made to the firmware?

    With Regards,

  • 0 in reply to Prasanna Rajagopal97
    Prodigy 50 points

    Hi Prasanna,

    Yes, I am using the TIDA-010024 example. I am working on an intermediate node with FH non-sleepy mode.  My task is to enter the sleep mode then wake up to unicast to and from the root. 

    I have tried several paths like changing MAC association, Rx ON Idle, and others with root poll and node push. The unicast works from node to root but not in the opposite direction. I am not sure if applying poll for both should maintain the unicast communication after waking up or not. 

    Also, How can I interpret sleepy device mode (recommended for leaf node which is not my case). If I applied this mode, will it work for intermediate nodes also and keep the unicast sync possible after waking up?