• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 229 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2652P: Z-Stack stops responding after some time on any SDKs later than 7.10.00.98

Lorenz Brun
Prodigy 10 points
Part Number: CC2652P
Other Parts Discussed in Thread: Z-STACK, SYSCONFIG

Tool/software:

I have a custom ZigBee device based on the CC2652P2. It keeps processing messages with Z-Stack 7.10.00.98, but not with any later SDKs (7.40, 7.41). It takes between a few minutes and hours to stop working.

Attaching a debugger doesn't show anything out of the ordinary, all non-Zigbee functionality (like pressing buttons, driving indicator LEDs) keeps working as normal, TI-RTOS timers also keep working.

The coordinator complains that it doesn't even get an MAC ack to the packets it sends, so it looks like the 802.15.4 stack already has a problem.

This is being tested in a relatively large network (~30 devices) with high interference in the 2.4GHz band but other devices and the old SDK cope fine. The code is derived from the genericapp Z-Stack sample with TI-RTOS 7. Coordinator is also running TI Z-Stack.

Any ideas on how to debug this further? I want to upgrade to 7.41 due to some routing stability issues on 7.10.

  • 0
    TI__Guru**** 208997 points

    Hi Lorenz,

    Is your device a ZR or ZED role?  What Network Configurations (SysConfig or Z-Stack files) have you modified?  Is it possible to recreate the issue with default examples?  Does anything specifically occur within the network at the time of device crash (provide sniffer logs if possible)?  Did you try SIMPLELINK-LOWPOWER-F2-SDK v7.10.01.24 and v7.10.02.23 as well?  The TI R&D Test Team continue to verify large network operation per release and have not cited any issues recently.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 10 points

    Hi Ryan,

    This is a ZR. No SDK files were modified. The following syscfg settings were modified:

    * Channel list was set to enable all channels.

    * TX power is set to 15dBm. 

    It happens quite randomly but I think it's correlated with network activity (more activity fails quicker). I can try running a sniffer in the background but it'll be hard to correlate when exactly the failure occurred in the sniffer logs.

    I tried 7.10.02.23 and it has the same issue. These are all clean builds, so there should be nothing left from other SDKs.

    The hardware is not suitable for any unmodified examples, so it's going to be hard to try these as-is.

    Regards,

    Lorenz

  • 0 in reply to Lorenz Brun
    TI__Guru**** 208997 points

    Hi Lorenz,

    Thank you for the additional information, which confirms that it is very similar (if not identical) to another issue that was recently resolved in the F2 SDK.  Unfortunately the fix requires changes to the pre-built libraries which are not accessible in the release SDK.  However, there should be a release of the F2 SDK v8.30 sometime later this week or early next week, and I recommend that you evaluate this new SDK as soon as it goes live.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 10 points

    Is the v8.30 SDK available in a different place than the existing v7.41 SDK or did it get delayed?

  • 0 in reply to Lorenz Brun
    TI__Guru**** 208997 points

    Thanks for checking in.  I apologize for the unfortunate news, but the F2 8.30 SDK has recently been gated due to internal issues.  The latest tentative date (as of 12/2) for release is now 1/31/25.

    Regards,
    Ryan