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.

question on Z-Stack

Other Parts Discussed in Thread: Z-STACK, CC2430, CC2420, CC2520

Hi,

This is my first post in this forum.

My question is about TI's Z-stack.

1. Does CC2480 support Z-stack? Why in the download page only shows the Z-stack file for cc2430, cc2420 and cc2520?

2. what's the relationship between Z-stack and ZASA, are these two in the network layer? It seems like to me that they are not in the same layer.

Thank you in advance

-Jim

 

 

 

 

 

  • 1. CC2480 has its own internal processor which runs the ZigBee stack, so there is not need to have an external MCU running Z-Stack.  This allows you to develop ZigBee applications much quicker and to use a MCU with significantly less memory (and cost) to run the end-device application.  If you are developing for ZigBee, I would highly recommend the CC2480.  If you don't use CC2480, you will have to use a MCU running the Z-stack software to implement ZigBee.

    2.  Z-stack IS the ZigBee Network Stack.  ZASA is source code for an implementation of application layer (the only portion of the ZigBee stack that is NOT run by the CC2480 processor to allow you to configure for your own sensors/controls and application requirements (sampling rates, sleep times, etc.)

  • Hi RFCE

    Thank you so much for your answers.

    I still have some doubts on the item 1.

    following your answer, I guess one difference between CC2480 and (CC2420, CC2430, CC2520) is that CC2480 does not need MSP430 MCU to run Z-stack and CC2480's Z-stack is already in its flash memory?

    also if I am using CC2430 now, I have to download the Z-stack for the MSP430 MCU? I am confused here.

    Thank you

    -Jim

     

     

     

     

      

     

     

  • Hi,

    CC2480 is a ZigBee processor, it runs a TI Zstack compliant ZigBee 2006. You don't have to programm the chip. As CC2480 is

    only in charge of Nwk part. You need an external MCU to develop your own application. ZASA is an exemple of application for

    a MSP430.

     

    For the others components:

    CC2420 and CC2520 are some RF transceivers, they need an external MCU to run Zstack.You have a Zstack different for each

    one running on MSP430 solution.

    CC2430 is a chip with a 8051 MCU and a RF transceiver in the same component. It exists also a Zstack especialy for

    CC2430. Zstack 1.4.3

    Launix.

     

     

  • Correct, if you use the CC2480, you will not need the MSP430 MCU to run Z-stack.  The ZigBee Network Stack is run on the CC2480 INTERNAL processor.  There is a defined set of commands to send data to the ZigBee stack across a SPI serial bus (or UART).

    If you are using CC2430 AND want to run a ZigBee network, you will need to download Z-stack for the MSP430 MCU.

  • RFCE, the Zstack for CC2430 is not about a MSP430 architecture. This stack is for the 8051 core of CC2430.

  • launix,  you are correct.  I've gotten so used to thinking MSP430 that I forgot that the CC2430/2431 are 8051-based.  Can't wait for the CC430 to be released.

  • Thanks to RFCE and Launix

    Let me confirm one more thing:

    TI's Z-Stack open source only for CC2420, 2430 and 2520, but not for CC2480, right? since the Z-Stack will be somehow different for different chips, do you think the inter-operatability will be affected? The inter-operatability is only limited to TI's ZigBee products, right? for example, an existing mesh network with CC2430 +MSP430 radio nodes, a CC2480 radio node wants to join.

    Thank you

    -Jim

     

     

     

  • You are right, because for CC2480, the stack is "in hard" on the flash. Even if the Zstack is different, the inter-operability must be right between products

    compliant to the same ZigBee specification. The inter-operability is right between differents manufacturer too.

    For your last question, if the Zstack on the different chip is compliant to the same specification, the inter-operability is right.