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

Stack overflow while using indirect messaging

suxint
Prodigy 20 points
Other Parts Discussed in Thread: Z-STACK

Hi,

I'm working on small application which base is SimpleApp from Z-Stack 2.2.0. The communication is between SimpleSensor and SimpleCollector. By default Sensor is bound to Collector and everything works fine. The problem occurs when I bind Collector to Sensor. While using indirect messaging (zb_SendDataRequest with address 0xFFFE) for sending data from Collector to Sensor I've got this warning:

The stack 'xxxxx" is filled to 100% (512 bytes used out of 512). The warning threshold is set to 90%.

First one or two sending works fine, until stack is full, after that there is no communication. When using direct or broadcast messaging there are no problems. While I was debugging i found out that stack is filling after calling zb_SendDataRequest function, or to be precise after invoking APSDE_DataReq function. Any ideas what can cause this problem?

Thanks in advance...

 

  • 0
    Expert 1075 points

    Hi,

    No idea what causes your problem, but while reading your post I had the following two thoughts:

    1) TI released the version 2.2.2 that contains bug fixes; hence, you should step up to the latest version to avoid debugging something that might be fixed already.

    2) Earlier I had an issue where I forgot to free the memory correctly after sending messages, maybe you have the same problem?

    Good luck!

    -LL-

  • 0 in reply to LuckyLuke
    Prodigy 20 points

    LuckyLuke said:

    1) TI released the version 2.2.2 that contains bug fixes; hence, you should step up to the latest version to avoid debugging something that might be fixed already.

    2) Earlier I had an issue where I forgot to free the memory correctly after sending messages, maybe you have the same problem?

    1) I hope that will be last solution, i wrote much code so it would be bad to start from beginning.

    2) I think that is automatically configured by Z-Stack. I watched from the Sensor side whats happening when it sends data and receives confirms, and it is same on Collector side, both use same functions for communication. And also, if that is problem a guess the same problem will occur even when I'm using direct or broadcast sending, not only for indirect.

    Anyway, thanks for advices...