• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 560 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.

CC2530: Node is not joining the network

Ashwin Natarajan
Intellectual 405 points

Part Number: CC2530
Other Parts Discussed in Thread: CC2531, Z-STACK,

Hi,

We faced an issue while joining a node to a network.

Setup: One coordinator (running at max TX power) and zero routers

Sniffing setup: CC2531. Packet info is sent from TiWsPc to Wireshark using socket mode and is decrypted in Wireshark

ZStack version: 2.6.2

Issue:

  1. When the node is programmed with the FW, we can see Beacon request from the node and Beacon from the coordinator
  2. We can see the association request from the node and the association response from the coordinator (association status: successful)
  3. There is no device announce after this process and the node cannot be reached at all. The node goes back to scanning channels for potential networks to join.

NOTE: We are facing this issue only when the firmware is run on a specific node (i.e.) if the same FW is programmed onto another device, the node joins the network successfully and makes a device announce.

Network key: 00:01:02:03:04:05:06:07:08:09:0A:0B:0C:0D:0E:0F

failure case_filtered.zip

  • 0
    Guru 735695 points

    ZStack version: 2.6.2 is obsolete. I would suggest you to use latest Z-Stack 3.0.2 or use Z-Stack Home 1.2.2a (Z-Stack core Version 2.6.3a) at least.

  • 0
    TI__Guru**** 223557 points

    Please mass erase and then re-program the device in question.  If it still fails then this indicates a hardware issue, in which case you can try an A-B-A test (swap CC2530 devices between boards) to see if it is a MCU or passive component issue.  Your faulty node may have been damaged by an ESD event or other system malfunction.

    Regards,
    Ryan