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

How to change ZCL groups for more groups entries (maybe 64) support?

whatcall
Intellectual 305 points
Other Parts Discussed in Thread: Z-STACK, CC2530

Hi, Guys,

Platform: CC2530, Z-stack 2.5.1a.

Project: based on SampleLight

I have a problem when I change the default -DAPS_MAX_GROUPS=16 to -DAPS_MAX_GROUPS=64 in f8wConfig.cfg file for SampleLight project. And then I could manage to add 64 groups for endpoints( 4 endpoints within a module, but we can treat them as one). But after I add one or two scenes for some endpoints, the radio become not responsive to the rest groups or scenes cluster commands . I do a power reset to this radio and then use another CC2530ZNP dongle to scan the group membership of the endpoints running on the first radio, the result indicates only  the first 16 group entries are discovered.  All the other groups entries seem overwritten by scenes information (because I only did write to scenes). I checked the f8w2530.xcl for segment management info and also OSAL_NV.c for the NV read and write operation. I have no idea how the group entry table is located in NV ROM and how the scene entries table could overwrite the groups information.

I will try to change the segment for NV pages to a larger number (also need mod in hal_board_cfg.h I guess).

In case you have met this issue, please help give a hint.

  • 0
    TI__Expert 3050 points

    Hi,

    Did you make sure you clean the content of the NV memory when you moved from APS_MAX_GROUPS=16 to APS_MAX_GROUPS=64? If you change the table size, but use an old NV content, then the NV item size and the actual table size will not match, potentially resulting with a behavior similar to what you describe...

    Whenever changing table sizes, please make sure to erase the NV content. By default, when using IAR to download a new firmware, the NV content is saved. To change this behavior, please select from the main menu: Project-->Options-->Debugger/Texas Instruments-->Erase Flash.

    Please let me know if it solves your issue.

    OD.

  • 0 in reply to OD
    Intellectual 305 points

    Hi,OD,

    We  solved it by erasing all Flash Memory with Flash Programmer tool in SmartRF Studio last week. It should be the problem just as you described.

    Now we are working on the Scene Table NV operation issue. As you know, NV table is read as a whole record item with osal NV APIs in current Z-stack, and this brings page-cross limitation and RAM usage issue if we want to support 64 scene table entry items.