• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 495 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.

LAUNCHXL-CC26X2R1: What is right way to change MAX_BINDING_CLUSTER_IDS (using IAR IDE)?

Yakov Treister
Prodigy 40 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: Z-STACK

Hi,

I get Bind response: table full because coordinator in my network bind more than 4 clusters on same entry.

(Just for note I defined Binding Table Size to be 10.)

Now from debug I sow that MAX_BINDING_CLUSTER_IDS made the problem and when I changed it indeed issue resolved.

BUT in Stack\nwk\binding_table.h there is comment:

// this value is built into the libraries, so it is not
// configurable in the release projects

So, what is right way to change MAX_BINDING_CLUSTER_IDS (I use IAR IDE)?

Thank you,

Yakov

  • 0
    TI__Guru**** 218427 points

    Hi Yakov,

    I am asking the Software Development Team to further clarify the source code dependency.  I found that the Legacy Z-Stack 3.0.2 solution's comment is slightly different: "Note that any value other than the default value may cause a compilation warning but Device Binding will function correctly."  Would it be possible for you to register multiple endpoints which split the cluster ID assignments and thus create separate binding entries to work around this issue?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 40 points

    Hi Ryan,

    Thank you so much for prompt response.

    I'll try to talk to guys implementing specific ZC i use, because now I see it causes similar problem to other our product.

    But to have general solution for my ZED project I prefere to allocate some spare in MAX_BINDING_CLUSTER_IDS.

    Best regards,

    Yakov

  • 0 in reply to Yakov Treister
    TI__Guru**** 218427 points

    Here is the feedback I received:

    That value is used in library functions and unfortunately cannot be changed by a non-source project.  Changing it in the release project will only change the files compiled outside of libraries, which means the struct will be sized differently in different places in the project which can lead to undefined behavior.
    We can speak offline if you require the source code to proceed.
    Regards,
    Ryan