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

CC2538: The coordinator cannot receive data

Cherry Zhou
Mastermind 22235 points
Part Number: CC2538
Other Parts Discussed in Thread: CC2592, Z-STACK

Hi team,

Here's an issue from the customer may need your help:

Board: CC2538+CC2592

After entering PM3 mode, the data is sent by waking up with a key, but the data is not received by the coordinator. The same program, without POWER_SAVING, everything works. Confirm that the data has indeed been sent. Z-Stack 3.0.2 is used.

Compile Options:

BDB_REPORTING
ewarm
CC2538_USE_ALTERNATE_INTERRUPT_MAP=1
FEATURE_RESET_MACRO
SECURE=1
TC_LINKKEY_JOIN
NV_INIT
NV_RESTORE
POWER_SAVING
NWK_AUTO_POLL
xZTOOL_P1
xMT_TASK
xMT_APP_FUNC
xMT_SYS_FUNC
xMT_ZDO_FUNC
xMT_APP_CNF_FUNC
xLCD_SUPPORTED=DEBUG
MULTICAST_ENABLED=FALSE
ZCL_READ
ZCL_DISCOVER
ZCL_WRITE
ZCL_BASIC
ZCL_IDENTIFY
ZCL_ON_OFF
ZCL_GROUPS

Configuration:

-DRFD_RCVC_ALWAYS_ON=FALSE

-DPOLL_RATE=0

-DQUEUED_POLL_RATE=0

-DRESPONSE_POLL_RATE=0

The customer would like to know if using the power-save mode for the terminal, what modifications does the coordinator need to make?  How to configure the code?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    Guru 735455 points

    I would suggest you to setup sniffer to check this. You need to provide sniffer log here to check what exactly happened.

  • 0
    TI__Guru**** 202096 points

    Hi Cherry,

    A sleepy ZED should be entering PM2 for Z-Stack power saving mode, as the sleep timer is required for operation. Are they doing anything inside the Z-Stack application to change this intended behavior?  Otherwise, a default example project is expected to wake and send messages without any difficulty.  The QUEUED_POLL_RATE and RESPONSE_POLL_RATE should remain at their default values (100) as they determine how quickly to poll for further queued or other response messages from the parent node.  The customer will need to provide more debug if they continue to experience difficulty.

    Regards,
    Ryan