CC2480 Developer's Guide CC2480 Developer's Guide SWRA176 Pa
|
|
|
Top Searches for this datasheet
CC2480
CC2480 Developer's Guide
CC2480 Developer's Guide SWRA176
Page
Table Contents
ZIGBEE CONCEPTS WHAT ZIGBEE DEVICE TYPES 1.2.1 Coordinator 1.2.2 Router 1.2.3 End-device STACK PROFILE ADDRESSING ADDRESS TYPES. ADDRESSING DEVICES WITH CC2480 USER CONSIDERATIONS
NETWORK COMMISSIONING OVERVIEW. CONFIGURATION OPTIONS 3.2.1 Configuring channel 3.2.2 Controlling which network join USER CONSIDERATIONS
PORTABLE DEVICES. OVERVIEW. CONFIGURATION OPTIONS USER CONSIDERATIONS
END-TO-END ACKNOWLEDGEMENTS OVERVIEW. CONFIGURATION OPTIONS 5.2.1 Number end-to-end retransmissions 5.2.2 Timeout between retransmissions USER CONSIDERATIONS
BINDING. OVERVIEW. USAGE 6.2.1 Creating binding table entries 6.2.2 Using binding table entries. USER CONSIDERATIONS
SECURITY. OVERVIEW. CONFIGURATION OPTIONS 7.2.1 Enabling security 7.2.2 distribution 7.2.3 USER CONSIDERATIONS
APPLICATION PROFILE. INTRODUCTION DEVELOP SIMPLE PRIVATE (MANUFACTURER-SPECIFIC) APPLICATION PROFILE
GENERAL INFORMATION. DOCUMENT HISTORY ADDRESS INFORMATION WORLDWIDE TECHNICAL SUPPORT.
CC2480 Developer's Guide SWRA176
Page
References
CC2480 Interface Specification SWRA175 CC2480 Data Sheet SWRS074
CC2480 Developer's Guide SWRA176
Page
CC2480
ZigBee concepts
What ZigBee
ZigBee open global standard wirelessly networked control monitoring solutions that reliable, cost-effective, low-power. ZigBee utilizes IEEE 802.15.4 compliant radios operating 2.4GHz unlicensed bands. Applications ZigBee include home building automation, industrial controls monitoring, energy management asset tracking. ZigBee network self-configuring, multi-hop wireless network with mains-powered routers battery-powered devices. multi-hop nature network means that devices that wish exchange data ZigBee network have depend other intermediate devices route their packets. Because this cooperative nature network, proper functioning requires that each device perform specific networking functions maintain network infrastructure (ii) configure certain parameters specific values. networking functions that device performs determines role device network called device type. parameters that need configured specific values, along with those values, called stack profile. Device Types
There three logical device types ZigBee network Coordinator (ii) Router (iii) Enddevice. ZigBee network consists single Coordinator node multiple Router Enddevice nodes. Note that device type does restrict type application that particular device.
example network shown diagram above, with ZigBee coordinator black), routers red) devices (white). 1.2.1 Coordinator This device that "starts" ZigBee network. first device network. coordinator node chooses channel network identifier (also called then starts network. coordinator node also used, optionally, assist setting security application-level bindings network. Note that role Coordinator mainly related starting configuring network. Once that accomplished, Coordinator behaves like Router node even away). continued operation network does depend presence Coordinator distributed nature ZigBee network. 1.2.2 Router Router performs networking functions allowing other devices join network (ii) multihop routing (iii) assisting communication child battery-powered devices.
CC2480 Developer's Guide SWRA176 Page
CC2480
Router allows other devices join network. Those devices that have joined network through particular Router referred "child" devices. These "child" devices either Routers End-devices. Router participates mesh networking function serve intermediate forwarding agent packets that routed through Router also performs special function child devices that battery-powered. caches packets destined those devices until child wakes polls data. When child needs transmit message, child sends data parent router. router then takes responsibility delivering packet destination, including performing route discovery functions necessary. This frees child device return sleep. router allowed have application that originator destination network traffic. requirement that routers must constantly ready relay data, they should mainspowered rather then batteries. 1.2.3 End-device end-device specific responsibility maintaining network infrastructure, sleep wake chooses. Therefore devices powered batteries long periods time. Stack Profile
stack parameters that need configured specific values, along with those values, called stack profile. parameters that comprise stack profile their values defined ZigBee Alliance. devices network must conform same stack profile (i.e., devices must have stack profile parameters configured same values). CC2480 based ZigBee compliant platform that conforms ZigBee-2006 specification ZigBee stack profile. such, join network created with devices from other ZigBee vendors that also conform same specification version. also join network created with devices conforming later ZigBee specification versions long only operating end-device. Also, network created CC2480 device will allow other devices join those devices either same specification version later versions only operates end-device. This behaviour according interoperabililty rules ZigBee Alliance.
CC2480 Developer's Guide SWRA176
Page
CC2480
Addressing
Address types
ZigBee devices have types addresses. 64-bit IEEE address (also called address Extended address) 16-bit network address (also called logical address short address). 64-bit address globally unique address that assigned maintained IEEE standards organization. More information these addresses available Each CC2480 device comes pre-programmed with 64-bit IEEE address. 16-bit address assigned automatically device when joins ZigBee network intended while network. only unique within that network. used identifying devices sending data within network. Addressing devices with CC2480
order send data device ZigBee network, application should ZB_SEND_DATA_REQUEST AF_DATA_REQUEST. each these commands, 16-bit short address destination device required. application determine short address extended address itself parent device through ZB_GET_DEVICE_INFO command. extended address network coordinator also available through same interface same extended ZigBee network). ZB_FIND_DEVICE_REQUEST ZDO_NWK_ADDR_REQ commands used discover 16-bit short address device network from 64-bit IEEE address. short address destination device known, application still send data using bindings. chapter more details this feature. possible broadcast data devices network. following 16-bit addresses defined broadcast addresses
Broadcast address 0xFFFC 0xFFFD 0xFFFF Description Group routers coordinator Group devices with radio receiver turned Broadcast group devices network
User considerations
broadcast addressing mode should used only when necessary. Because transmitted whole network, uses more bandwidth than regular unicast packet. network will ratelimit number broadcast packets that transmitted network. possible, special group addresses 0xFFFC 0xFFFD should used place 0xFFFF address.
CC2480 Developer's Guide SWRA176
Page
CC2480
Network commissioning
Overview
Each device configuration parameters (see "Configuration Interface" section CC2480 Interface Specification document) that configured host processor. "network-specific" configuration parameters should same value devices that will part network. "device-specific" configuration parameters different values each device. ZCD_NV_LOGICAL_TYPE must that there exactly device configured coordinator (ii) battery powered devices configured end-devices. Once this done, devices powered-up order. coordinator device will start network other devices will find join Configuration options
3.2.1 Configuring channel This configured ZCD_NV_CHANLIST configuration parameter. Note that this bitmask multiple channels selected simultaneously. coordinator device will scan channels specified ZCD_NV_CHANLIST configuration parameter pick channel that least energy level. more than channel energy level, coordinator will pick channel with least number existing ZigBee networks. routers end-devices will scan channels specified ZCD_NV_CHANLIST configuration parameter. 3.2.2 Controlling which network join scenarios where multiple networks coexist, necessary control network formation joining process. This done ZCD_NV_PANID configuration parameter addition channel parameter). this parameter value between 0x3FFF, coordinator will this value network identifier when starts network. router end-device will only join network that this identifier. turn this feature off, this parameter value 0xFFFF. that case, coordinator will pick arbitrary value network identifier routers end-devices will able join network. User considerations
network topology constrained certain values that specified ZigBee specification. maximum depth network limited depth network number hops that device network from coordinator. Each router device coordinator device) have upto child devices. these, upto other routers while end-devices. Note that end-device "child" multiple router devices portable moves within network.
CC2480 Developer's Guide SWRA176
Page
CC2480
Portable Devices
Overview
devices automatically portable. This means that when device detects that unable communicate with parent device, will rejoin network through another parent device. rejoining process transparent host processor with exception that end-device will receive 16-bit short address when changes parent device. When CC2480 end-device detects that parent device responding, either periodic "poll" packets application data packets, will initiate "rejoin" procedure. will first perform orphan-scan existing parent device. such device found, will scan potential parent device rejoin network. Configuration options
number consecutive communication failures before end-device will initiate rejoin procedure configured ZCD_NV_POLL_FAILURE_RETRIES parameter. Note that communication failures include application data messages well poll packets deivice performing periodic wakeup polling). User considerations
device that changes parent device will receive 16-bit short address. This implications there other devices network that sending messages this device, address changed. Usually, portable devices source messages thus this issue. Router devices also move, even though that typical scenario since they mainspowered devices thus unlikely portable. However, case that router device does move, does rejoin process does change 16-bit short address. However, "child" end-devices, they have perform rejoin since they will lose communication with their parent device. Thus, best router device that expected portable, does allow other devices join (see ZB_PERMIT_JOINING_REQUEST command details this).
CC2480 Developer's Guide SWRA176
Page
CC2480
End-to-end acknowledgements
Overview
non-broadcast messages, there basically types message retry: end-to-end acknowledgement (APS ACK) hop-by-hop acknowledgement (MAC ACK). ACKs always default usually sufficient guarantee high degree reliability network. provide additional reliability, well enable sending device confirmation that packet been delivered destination, ent-to-end acknowledgements used. acknowledgement done layer acknowledgement system from destination device source device. sending device will hold message automatically retry sending message until destination device sends message indicating that received message. This feature enabled disabled each message sent with options field ZB_SEND_DATA_REQUEST AF_DATA_REQUEST commands. Configuration options
following options provided. 5.2.1 Number end-to-end retransmissions This controlled ZCD_NV_APS_FRAME_RETRIES parameter. 5.2.2 Timeout between retransmissions This controlled ZCD_NV_APS_ACK_WAIT_DURATION parameter. This should slightly larger value than expected round-trip time network. Note that destination device end-device, round-trip time will much larger since packet cannot delivered until destination end-device will wake-up poll parent packet. User considerations
end-to-end acknowledgement feature will give much higher level reliability application data packets. However, there significant cost terms network bandwidth, latency power consumption. Because each packet results acknowledgement packet back sender, network throughput reduced. power consumption end-device will increased since only transmit packet wakeup again later receive application-level acknowledgement packet. Thus, encouraged that end-to-end acknowledgement packets used sparingly. most applications, sufficient end-to-end acknowledgements occasionally (say, every transmitted packet) every single packet.
CC2480 Developer's Guide SWRA176
Page
CC2480
Binding
Overview
binding logical link between devices application layer. Bindings allow application send packet without knowing actual destination address. ZigBee stack sending device will determine destination address through lookup from binding table, then forward message destination device multiple devices). Bindings optional feature. possible bindings application knows destination address (the 16-bit short address) each data packets that transmits. However, most applications, that case. logical connections between devices usually known until network setup final deployment. example, lighting network with multiple switches lights, cannot predicted ahead time which switch should control which light. CC2480 device will store binding information non-volatile memory. there unintentional reset, binding information (along with other network configuration) automatically restored without user having setup bindings again. Usage
6.2.1 Creating binding table entries Before device binding feature send data packets, first needs create binding table entries. This usually done right after device joins network extended address destination device known, this command issued source device create binding entry, ZB_BIND_DEVICE function used create binding table entries. extended address known, "push button" strategy employed. this case, destination device first state where will respond match requests issuing ZB_ALLOW_BIND command. Then ZB_BIND_DEVICE command issued source device with null address destination. source device will then broadcast match request packet devices "allow bind" mode will respond. source will then create binding table entry responding device more than devices respond, only first will used addition, bindings also setup external ZigBee commissioning tool issuing appropriate over-the-air commands. These tools available from party vendors. Note that bindings only created between "complementary" devices. That binding will only succeed both devices have registered their application with same profile identifier (ii) same command_id, device command "output" while other device "input". 6.2.2 Using binding table entries When sending data packet, destination address must special value 0xFFFE indicate CC2480 that binding table lookup should perfomed basis command cluster derive actual destination address(es). User considerations
Bindings created source device {command-id, destination address} basis. There multiple bindings created with same command-id different destination addresses. that case, when host processor sends data packet with specified command CC2480 will automatically send copy message each destination addresses listed binding table. example, lighting network, single switch control more than light. Additionally, given destination address destination more than command
CC2480 Developer's Guide SWRA176
Page
CC2480
maximum destination addresses used single CC2480 device. Each destination device destination upto commands id's cluster id's single CC2480 device.
CC2480 Developer's Guide SWRA176
Page
CC2480
Security
Overview
ZigBee provides network-wide security using 128-bit block cipher mode operation underlying security primitive. AES/CCM security algorithms were developed external researchers outside ZigBee Alliance also used widely other communication protocols. security mechanism provided ZigBee provide following functions Privacy application payload encrypted prevent eavesdroppers from reading contents. Message integrity application payload protected with message integrity check prevent modification contents. Access control device must possess network order participate network able send receive data.
CC2480 onboard hardware engine that will automatically apply ZigBee security, enabled. Configuration options
following configuration options available control security. definition parameters available "Network specific configuration parameters" section CC2480 Interface Specification document. 7.2.1 Enabling security enable disable security, ZCD_NV_SECURITY_MODE configuration parameter. 7.2.2 distribution There ways distribute security devices network. security pre-configured same value devices network host processor. Alternately, pre-configured only coordinator device then distributed other devices over-the-air they join network. latter case, there "moment vulnerability" during joining process during which adversary determine listening over-air traffic compromise network security. Hence this option should used unless application developer feels that this option necessary that risk manageable. distribution option selected ZCD_NV_PRECFGKEYS_ENABLE parameter. 7.2.3 actual that will used security configured ZCD_NV_PRECFGKEY parameter. Depending value ZCD_NV_PRECFGKEYS_ENABLE parameter, this parameter should either pre-configured devices network same value pre-configured only coordinator. User considerations
Enabling security following effects network operation Payload overhead Each packet will have additional security header about 18bytes. This will reduce total payload available application same amount. Processing overhead Each packet will take additional processing apply remove security. This reduce network throughput.
CC2480 Developer's Guide SWRA176
Page
CC2480
Application profile
Introduction
application profile common language exchanging application data. consists application devices within that profile (ii) commands exchanged devices application layer (iii) format data that exchanged between devices each command. Application profiles either public private (manufacturer-specific). Public profiles specified ZigBee Alliance should used interoperability with other application vendors necessary. example, manufacturer light switch wishes control light control from another manufacturer, both them should follow same public profile. CC2480 used create public profile applications. necessary that case implement application code host processor that conforms desired public profile specification. More details public profiles obtained from ZigBee Alliance website application-level interoperability required, simple private profile used. Each profile 16-bit identifier called profile public profiles, identifier already defined ZigBee Alliance. private profiles, Alliance will issue identifiers application developer upon request. This necessary that devices with different application profiles same network, profile identifiers will unique. application residing host processor will register with CC2480 before starting joining network (see section CC2480 Interface Specification document). This registration command contains necessary application profile information CC2480 device properly ZigBee network. develop simple private (manufacturer-specific) application profile
first step identify application devices types that will part network. example application shown figure below, this consists temperature sensor, occupancy sensor, thermostat heating/cooling unit.
cmd: temp reading
Temp sensor
cmd: flow control cmd: heat control cmd: cool control cmd: reading
Thermostat
Heating/cooling
Occupancy sensor
Identify devices that need battery powered (e.g. temp sensor sensor devices) those that mains-powered (the thermostat heating/cooling unit devices). battery-powered devices have configured end-device's while mains-powered devices configured routers (one them should coordinator). Identify "commands" that need exchanged between these devices assign unique 16bit command_id each them. Also identify devices that "produce" (output) "consume" (input) each commands. above example, these follows cmd:temp reading "output" temp sensor "input" thermostat
CC2480 Developer's Guide SWRA176 Page
CC2480
cmd:occ reading "output" from occupancy sensor device "input" thermostat cmd:air flow control, cmd:heat control cmd:cool control messages "output" thermostat "input" heating/cooling unit. each "command", define format message being exchanged interpretation. example, temperature value exchanged 8bit value" format where indicates indicates 64°C steps 0.25°C" interpretation This depends actual application requirements. application profile well list commands that each device "produces" "consumes" should registered with CC2480 host processor after each device reset. This done ZB_APP_REGISTER_REQUEST AF_REGISTER commands. This information used CC2480 device when binding feature used bind complementary devices network.
CC2480 Developer's Guide SWRA176
Page
CC2480
General Information
Document History Table Document History
Revision Date 2008-05-27 Description/Changes Version documents R
Address Information
Texas Instruments Norway N-0349 Oslo NORWAY Tel: Fax: site: http://www.ti.com/lpw
Worldwide Technical Support Internet
Semiconductor Product Information Center Home Page: Semiconductor KnowledgeBase Home Page: support.ti.com support.ti.com/sc/knowledgebase
Product Information Centers
Americas Phone: Fax: Internet/Email: +1(972) 644-5580 +1(972) 927-6377
Europe, Middle East Africa Phone: Belgium (English) Finland (English) France Germany Israel (English) Italy Netherlands (English) Russia Spain Sweden (English) United Kingdom Fax: Internet: +358 25173948 8161 0107 4824 8587 1604 8161 2045 support.ti.com/sc/pic/euro.htm
CC2480 Developer's Guide SWRA176
Page
CC2480
Japan Internet/Email International Domestic International Domestic +81-3-3344-5317 0120-81-0036 support.ti.com/sc/pic/japan.htm www.tij.co.jp/pic
Asia Phone International Domestic Australia China Hong India Indonesia Korea Malaysia Zealand Philippines Singapore Taiwan Thailand +886-2-23786800 Toll-Free Number 1-800-999-084 800-820-8682 800-96-5941 +91-80-51381665 (Toll) 001-803-8861-1006 080-551-2804 1-800-80-3973 0800-446-934 1-800-765-7404 800-886-1028 0800-006800 001-800-886-0010 +886-2-2378-6808 tiasia@ti.com ti-china@ti.com support.ti.com/sc/pic/asia.htm
Email Internet
CC2480 Developer's Guide SWRA176
Page
CC2480
IMPORTANT NOTICE
Texas Instruments Incorporated subsidiaries (TI) reserve right make corrections, modifications, enhancements, improvements, other changes products services time discontinue product service without notice. Customers should obtain latest relevant information before placing orders should verify that such information current complete. products sold subject TI's terms conditions sale supplied time order acknowledgment. warrants performance hardware products specifications applicable time sale accordance with TI's standard warranty. Testing other quality control techniques used extent deems necessary support this warranty. Except where mandated government requirements, testing parameters each product necessarily performed. assumes liability applications assistance customer product design. Customers responsible their products applications using components. minimize risks associated with customer products applications, customers should provide adequate design operating safeguards. does warrant represent that license, either express implied, granted under patent right, copyright, mask work right, other intellectual property right relating combination, machine, process which products services used. Information published regarding third-party products services does constitute license from such products services warranty endorsement thereof. such information require license from third party under patents other intellectual property third party, license from under patents other intellectual property Reproduction information data books data sheets permissible only reproduction without alteration accompanied associated warranties, conditions, limitations, notices. Reproduction this information with alteration unfair deceptive business practice. responsible liable such altered documentation. Information third parties subject additional restrictions. Resale products services with statements different from beyond parameters stated that product service voids express implied warranties associated product service unfair deceptive business practice. responsible liable such statements. products authorized safety-critical applications (such life support) where failure product would reasonably expected cause severe personal injury death, unless officers parties have executed agreement specifically governing such use. Buyers represent that they have necessary expertise safety regulatory ramifications their applications, acknowledge agree that they solely responsible legal, regulatory safety-related requirements concerning their products products such safety-critical applications, notwithstanding applications-related information support that provided Further, Buyers must fully indemnify representatives against damages arising products such safetycritical applications. products neither designed intended military/aerospace applications environments unless products specifically designated military-grade "enhanced plastic." Only products designated military-grade meet military specifications. Buyers acknowledge agree that such products which designated military-grade solely Buyer's risk, that they solely responsible compliance with legal regulatory requirements connection with such use. products neither designed intended automotive applications environments unless specific products designated compliant with ISO/TS 16949 requirements. Buyers acknowledge agree that, they non-designated products automotive applications, will responsible failure meet such requirements. Following URLs where obtain information other Texas Instruments products application solutions: Products Amplifiers Data Converters Interface Logic Power Mgmt Microcontrollers amplifier.ti.com dataconverter.ti.com dsp.ti.com interface.ti.com logic.ti.com power.ti.com microcontroller.ti.com Applications Audio Automotive Broadband Digital Control Military Optical Networking Security Telephony Video Imaging Wireless www.ti.com/audio www.ti.com/automotive www.ti.com/broadband www.ti.com/digitalcontrol www.ti.com/military www.ti.com/opticalnetwork www.ti.com/security www.ti.com/telephony www.ti.com/video www.ti.com/wireless
Mailing Address: Texas Instruments, Post Office 655303, Dallas, Texas 75265 Copyright 2008, Texas Instruments Incorporated
CC2480 Developer's Guide SWRA176
Page
Other recent searches
V630ME29 - V630ME29 V630ME29 Datasheet
NTE7109 - NTE7109 NTE7109 Datasheet
MN54ACQ245-X - MN54ACQ245-X MN54ACQ245-X Datasheet
MHW8227 - MHW8227 MHW8227 Datasheet
FRS013-3003-1 - FRS013-3003-1 FRS013-3003-1 Datasheet
ENN8095 - ENN8095 ENN8095 Datasheet
e8715e - e8715e e8715e Datasheet
APD-080M025-1 - APD-080M025-1 APD-080M025-1 Datasheet
Privacy Policy | Disclaimer
© 2012 Datasheet Archive
