Represent Texas Instrument to design the syllabus and conduct a 3 hours workshop for Republic Polytechnic on ZigBee and MSP430 in Singapore.

1. 1 ZigBee Introduction to TI wireless solution CC2530 ZigBee Network Processor Mini Kit

3. Communication Example

5. ZigBee Alliance “The ZigBee Alliance is an association of companies working together to enable reliable, cost-effective, low-power, wirelessly networked monitoring and control products based on an open global standard” Source: ZigBee Alliance homepage Promoters of the ZigBee alliance are:

6. What are the alternatives to ZigBee? 5

7. Global Frequencies

8. Technologies Summary

9. Why Bluetooth®? Wireless data, audio or voice Replacement of serial cables 10-100m range personal ‘bubble’ (Personal Area Network) Instant, secure, automatic connections Low power consumption (AAA battery power source) Good data rates (~2Mbps throughput) Install base of 3 billion units Why TI Bluetooth? Best in-class RF performance (Transmit and Receive) Dual-mode options with ANT & Bluetooth Available with Wi-Fi Highly integrated, fully certified module available to reduce cost and time to market

10. Why ANT? Ultra low power (ULP) enables coin cell operation for wireless sensors Devices can operate for more than a year without recharging Ideal for sports and fitness sensors, medical and healthcare devices Established ANT+ interoperable ecosystem utilizing 2.4GHz for global deployment Install base of over 13 million devices (Dec’10) Why TI ANT? TI offers single-mode and dual-mode solutions Dual-mode is the first single-chip solution Fully tested ANT ecosystem solution – for both sensor and mobile handheld devices Best in class RF performance Excellent coexistence with other 2.4GHz devices Highly integrated, optimized hardware chipsets or fully certified modules to reduce cost, size and time to market

11. Why Bluetooth Low Energy (BLE)? Ultra-low power communication Fraction of the power of Bluetooth Enables sensor applications to operate on a coin cell for >1 year Consumer medical, sports and wellness applications, mobile accessories Why TI BLE? TI provides both single mode and dual mode Bluetooth low energy solutions Both sides of the link to create a fully tested Bluetooth low energy ecosystem - from smart sensors to smart phones Leading RF performance up to +97dB output power Excellent coexistence with other 2.4GHz devices System on a chip integrated solution and modules available

12. Why Wi-Fi? Connect electronic devices to each other, to the Internet, and to wired networks – quickly and securely Most prominent wireless connectivity technology for computers and internet Real-world performance similar to wired networks High data rates (>20Mbps throughput) Over 2.5B Wi-Fi units deployed in the market today; ~1 billion units/year projected starting in 2011 Why TI Wi-Fi? Wi-Fi + Bluetooth in a single-chip with best-in-class coexistence Bring multi-radios to battery powered applications Highly integrated, fully certified modules available to reduce cost and time to market Platforms offered that integrate system hardware and software

13. Why ZigBee? Self healing (Mesh networks) Operate on battery (many years on AA batteries) Low node cost Easy to deploy (low installation cost) Support Large networks (hundreds of nodes) Intended for monitoring & control applications Standardized protocol (interoperability) Why TI ZigBee? With power amplifying support (cc2591) to boost the signal above 100m One of the major promoter in the ZigBee alliance. One of the early adopters with years of accumulated experience. Wide variety of products compatible with ZigBee.

14. Wireless Technologies Comparison Range Throughput 20 Mbps Zigbee WiFi <2 Mbps ANT BLE/ANT RF4CE Zigbee Sub-1GHz 2.4GHz Bluetooth <250 kbps RF4CE Technology BLE Sub-1GHz Technology Li-Ion Typical Power Source Required WiFi AAA Bluetooth WiFi 2.4GHzProprietary Bluetooth Zigbee RF4CE Coin Cell BLE/ANT Sub-1GHz 2.4GHzProprietary 10,000 100 10 Range (m) RFID Technology

15. Typical Decision Parameters Highest Data Rate WLAN (Video) Bluetooth (Audio) Zigbee/802.15.4 Highest Battery Life Zigbee/802.15.4 (Alkaline/Li-Ion) Bluetooth (Alkaline/Li-Ion) WLAN/UWB (Line powered/Li-Ion) Longest Range (Radio Only, not boosted) WLAN Zigbee802.15.4 Bluetooth

16. Commercially deployed ZigBee

17. www.tizigbeedemo.com 16

18. 17

19. 18

20. 19

21. MSP430 20

23. Industry leading code density

24. Flexible clock system

25. Single-cycle register operations

26. 16 GP 16-bit Registers

28. Standby <1 μ A

29. Includes RTC and BOR

30. Active 160 μA/MIPS

31. Fast wake-up <1 μs

32. Internal voltage regulator

33. 4 Programmable voltage levels

35. One programmer for all devices

36. Embedded emulation

37. Trace, single-stepping, in-system debug

38. Intelligent peripherals reduce overhead

39. DTC, DMA, Autoscanning A/D

42. 1.8 - 3.6V single-supply operation

43. Zero-power BOR

44. <50nA pin leakage

45. CPU that minimizes cycles per task

47. 16-bit Orthogonal RISC CPU Efficient, ultra-low power CPU C-compiler friendly RISC architecture 27 core instructions 24 emulated instructions 7 addressing modes Constant generator Single-cycle register operations Memory-to-memoryatomic addressing Bit, byte and word processing 20-bit addressing on MSP430X for Flash >64KB

48. Ultra-Low PowerActivity Profile Extended Ultra-Low Power standby mode Minimum active duty cycle Interrupt driven performance on-demand

50. LCD driver

51. RAM/SFR retainedStand-by DCO off ACLK on 1.0µA Specific values vary by device

52. 10-bit & 12-bit ADCs 200ksps+ Autoscan SingleSequenceRepeat-singleRepeat-sequence Int/ext ref TA SOC triggers Data Transfer Controller(DTC) DMA Enabled Fast Flexible 10- and 12-bit ADCs DirectTransferController DataTransferController

53. 12-bit monotonic 8/12-bit voltage output Programmable settlingtime versus power Int/ext reference Binary or 2’s compliment Self-calibration Group sync load DMA enabled DAC12

54. ~100nA operation (Comp_B) Hysteresis generator (B) Input multiplexer Reference generator Low-pass filter Battery detect Interrupt source Timer_A capture Multiplexer short for sample-and-hold Analog Comparators

56. Bit clock generator

58. 32 CC2530 ZigBee Network Processor

60. Educational tool

61. No ZigBee Profile support

62. Not for ZigBee certfied products

63. Easy portable to other TI platforms

64. Porting guide to Stellaris on Wiki page

65. ZigBee Profile Examples

66. Home Automation

67. Smart Energy

68. ZigBee Certification Ready

69. Includes Operating System Abstraction Layer

71. 35 Wireless Utility Meter 32, 64, 128 or 256KB 32KB 1KB Low cost, Low power, SoC2.4GHz RF Transceiver Low cost, Low powerMixed Signal Microcontroller

72. 36

73. Three paths to ZigBee

74. 38

75. 39 Flexible low-power modes Powerful 5-channel DMA engine Up to 256k of flash IR generation circuitry 102 dBm link budget

76. 40 ZigBee™ – Mesh Network Devices

77. Coordinator 41 Starts a non-beaconed PAN Allows other devices to join it Buffers messages for sleeping End Devices Provides binding and address-table services Routes messages Dynamically repair routing Can have I/O capability Manages security Radio always on

78. Router Does not own or start PAN (Scans to find a network to join) Allows other devices to join it after PAN has been started Routes messages Dynamically repairs routing Buffers messages for sleeping End Devices Support secure messaging Can have I/O capability Radio always on 42

79. End Device Does not: Route messages Own or start network Allow other devices to join it Scans to find a PAN to join Polls parent to get messages (can be disabled) Can be mobile Radio/CPU can sleep 43

80. ZigBee Mesh Routing Mesh network routing employs AODV (Ad Hoc On Demand Distance Vector Routing) Ad Hoc (Network is unknown at start-up) On Demand (Determines the route to the destination only when needed) Distance Vector (Only the final destination and the next hop are stored at each node. Relies on a distributed protocol to handle routing) Self healing upon route failure Reliable and robust. Failed router will reinitiate discovery and find an alternative path 44

81. Automatic Rerouting 45

82. ZigBee Device Software Architecture 46

83. IEEE 802.15.4 and TI-MAC 47 Specifies the physical and MAC for low data-rate, wireless personal area networks Intended to allow ultra low power consumption nodes Physical limit of 250kb/s, but much lower in practice Predefined modulation types and frequencies TI 802.15.4 devices operate on 2.4GHz ZigBee is built on top of this standard

84. TI-MAC 48 Available platforms CC2420/CC2 520 (2.4GHz) + MSP430 CC2430/1, CC2530 (2.4Ghz) SoC Low power, low data rate (~100kb/s) Peer to Peer or Star Acknowledgements provided No license, No fees Requires unique IEEE address

85. 49 Z-Stack Low power, Low data rate (~100kb/s) Self forming and repairing mesh networking MAC and APP level acknowledgment Interoperability possible ZigBee.org membership required Compliance testing required Unique IEEE address required

86. Software Stack Considerations ZigBee SimpliciTI Proprietary IEEE 802.15.4 RF4CE Layer Design Freedom Design Freedom Application Design Freedom Design Freedom Design Freedom Higher Layer Protocol Z-Stack + Simple API Design Freedom Remo TI Design Freedom Design Freedom TI MAC Lower Layer Protocol SimpliciTI Design Freedom TI MAC TI MAC CC253x CC243x CC2480 Physical Layer CC111x, CC251x, CC243x, CC253x, CC430, MSP430+CC1101, CC2500 or CC2520 all LPRF devices CC253x CC243x MSP430+CC2520 CC253x CC243x 2.4 GHz RF Frequency 2.4 GHz Sub 1 GHz 2.4 GHz Sub 1 GHz 2.4 GHz 2.4 GHz Solution

87. ZigBee vs. SimpliciTi 51

88. ZigBee Snapshot – Sept 2008 IEEE 802.15.4 – 2003 defines PHY/MAC ZigBee 2006 Products shipping today ZigBee 2007 Two stack profiles: ZigBee and ZigBee PRO 52

89. ZigBee 2006 Extremely well tested by a variety of companies Base of products and networks on market and in use today Many certified stacks and silicon providers available Simpler: Less code and overheard than 2007 or PRO 53

90. ZigBee 2007 and ZigBee PRO ZigBee 2007 Based on proven 2006 feature set plus frequency agility and optional fragmentation Basic features require less memory & resources than PRO ZigBee PRO Enhanced features optimize performance and RAM utilization under select scenarios Feature enhancements based on identified limitations of ZigBee 2006 for specific network deployment Interoperability PRO devices will operate as End Device on a ZigBee 06 or 07 network, and vice cersa ZigBee 06 and 07 network seamlessly 54

91. ZigBee 2007 Summary ZigBee is useful … In most topologies; including peer to peer or sensor reporting ZigBee drawback include: Limited address assignment capabilities in a mobile environment Route establishment takes time and expends energy during route establishment in many source to coordinator scenario 55

92. ZigBee PRO Summary ZigBee PRO is useful in networks with: Large deployments with high ratio of mobile devices Many sensor nodes reporting to Coordinator High Security requirements ZigBee Pro drawbacks include: Additional features increase the code size and complexity Network will suffer reduced throughput due to communication overhead Heavy burden on the Coordinator Required Network Management becomes a point of Failure 56

93. 57 Q&A regarding to CC2530 (ZigBee)…

94. 58 IAR Embedded Workbench for MSP430 Subhead text here

95. 59 Debug using IAR Launch IAR Embedded Workbench Open ‘Hardware Interface Example.eww’ C:exas InstrumentsC2530ZNP Mini KitNP ExamplesARardware Interface Examples.eww Set Button Blink – Debug to Active Project > Download and Debug Once enter debug mod, Click F5 or Debug > Go

96. Useful Information about IAR 60 In IAR, right click on the function and choose ‘Go to definition of xxx’ can find out the origin of the function.

97. Useful Information about IAR 61 If devices got disconnected while still in use, make sure you choose ‘clean’ before debug to avoid unnecessary problem.

98. 62 Understanding CC2530 ZNP Mini Kit demo code Subhead text here

99. 63 Introduction The examples provided are designed to be small, easy to use building blocks of code which can be easily incorporated into your application. The examples in this document are written for ease of use first, performance second. There is most likely a faster way to do everything, but we want to ensure that the examples are easy to understand. The examples are grouped into three categories, organized for simple to complex: Hardware Interface Example: exercising the basic hardware on the board; light sensor, accelerometer, UART, etc. Communication Examples: sending/receiving packets between two CC2530ZNPs Simple Applications Examples: simple examples of how to use the CC2530ZNP in an application

100. 64 Button Blink This is a simple example that just toggles the state of the LED when the button is pressed, and is a good first program to compile and load to ensure that you have configured the development environment correctly.

101. 65

102. 66 Hello World The MSP430 hardware creates a virtual COM port to attach to the target board. This is useful for outputting debug information to see what is happening. On the CC2530ZNP target board, the hardware UART is used as a debug console. For this example you’ll need a HyperTerminal. The first step is to determine which COM port the target board is using. On windows XP, Click Start and then Run. Type in, ‘devmgmt.msc’.

103. 67 View under Ports (COM & LPT) to see which COM port is used for the msp430. It will be labeled something similar to “MSP430 Application UART (COM9)”. Now open the HyperTerminal. Select COM port from above (COM9) and configure the serial port as: Port: COM9 Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow Control: none Once the Hello World example is debugged and downloaded, it should output to this console. You should now see the LED blink and the text ‘Hello World’ output to the console.

104. 68 Communication Examples In this example, it demonstrates how to establish communication between two devices. There must be one coordinator in the network. The basic coordinator startup process Reset ZNP Set Startup Option = CLEAR_STATE and CLEAR_CONFIG – this will restore the ZNP to “factory” configuration. Reset ZNP Set ZigBee Device type to COORDINATOR Reset ZNP Note: if you want to set a custom PANID or channel list, do that here and then reset ZNP Register Application (Configure the ZNP for our application) Start App Wait for Start Confirm

105. Change Channel 69 As mention previously, each network can only have one coordinator. Therefore, each group must use different channel to avoid conflict.

106. 70

107. 71 Basic Communication Flowchart Coordinator Init. network & display info Listen for incoming data or join request Join request Date received Full Display incoming messages Check if network full Denial Connection Not Full Accept Connection

108. 72 Basic Communication Flowchart End-Device Init. network & display info Search for Coordinator or Router Timer Interrupt Triggers Send message to coordinator

109. 73 Simple Application Example

110. 74 CC2530 ZNP Sample Code Flowchart Coordinator Init. network & display info Format and Broadcast Listen for hardware interrupt Button Pressed Listen for incoming data or join request Join request Date received Parse and Display Messages Full Check if network full Denial Connection Not Full Accept Connection Unknown Message Status Report

111. 75 CC2530 ZNP Sample Code Flowchart End-Deivce Timer Triggered Init. network & display info Format and Broadcast Listen for hardware interrupt Button Pressed Listen for incoming data Accelerometer Triggered Date received Display Messages