Remote Control Application Development with BeeStack Consumer

Transcription

1 August, 2009 Remote Control Application Development with BeeStack Consumer Victor Kwong

2 Introductions and objectives RF4CE Technology Overview IEEE Technology Overview RF4CE Network CERC profile Freescale s Private Profile Freescale s ZigBee RF4CE Supported Devices BeeKit Introduction Hands-on Laboratory Exercise Agenda 2

3 RF4CE Technology Overview 3

4 Home Entertainment Control Today with IR Line of sight transmission Decades-old technology Field of vision limitations Remote needs to be pointed at IR receiver in equipment being controlled Unidirectional unacknowledged transfers Unreliable communication Cannot send information to remote control or between components (DTV, set top box, etc.) Requires manufacturer-specific IR databases Each product has its own control commands Requires larger memory for storing lookup tables Savings from 8 to 32 KB Technology Challenge Plasma TV contains high frequency inverter that obstructs IR signals LCD back lighting saturates DTV IR receiver DTVs field of vision IR diode placed near edge of TV which many times is outside IR field of vision Power consumption Multiple redundant transmissions for each command Higher TX power required to avoid interference created by plasma/lcd screens Typically over 100mA required per IR transmission 4

5 Home Entertainment Control Today with RF No line-of-sight or field of vision limitations Control components behind walls or in cabinets Control over extended ranges Faster more reliable communications Transmit commands until received Many times faster response than IR Enables enhanced user interfaces Touchpad or pointing capability Bi-directional capability More reliable communications Send program guides, playlists stock quotes, etc to remote/components Allows for communications between devices Over-the-air firmware updates possible Remote locator RF consumes 25% of the power used by IR solutions selected for cost and interference avoidance capabilities with benefit of IEEE standard DSSS CSMA-CCA Allows for true interoperability between vendors products 5

6 RF4CE based on Freescale s SynkroRF Protocol Freescale was approached by large CE manufacturer in 2007 for RF control solution to overcome IR problems with DTVs Originally offered ZigBee, but ended up being too complicated and expensive Solution had to be multi-source, based on a public open standard Freescale worked with the CE company and created new protocol called SynkroRF SynkroRF is a IEEE based networking protocol Freescale launched initiative in January 2008 at CES to create standards body with SynkroRF as basis to become de-facto global open RF standard for home entertainment control RF4CE consortium announced in June 2008 with mission of creating a standard for home entertainment control Freescale gave RF4CE consortium SynkroRF protocol 80% of RF4CE protocol is based on Freescale SynkroRF technology RF4CE R1.0 standard ratified in December 2008 Available now from Freescale.com/RF4CE 6

7 Freescale ZigBee RF4CE Leadership ZigBee Alliance Board Of Directors Brett Black, Freescale Wireless Connectivity Operations Manager ZigBee Alliance RF4CE Steering Committee Brett Black, Freescale Wireless Connectivity Operations Manager ZigBee Alliance RF4CE Marketing Chair Ryan Kelly, Freescale Wireless Connectivity Marketing and Applications Manager ZigBee Alliance RF4CE Compliance Chair Victor Berrios, Freescale Wireless Connectivity Platform Manager ZigBee RF4CE Certified Platform Golden Unit BeeStack Consumer (Freescale s RF4CE Implementation) 7

8 Sony Adopts RF Remote Control for New "BRAVIA" SynkroRF Adoption Sony Corp. announced 15 new models of its LCD television "BRAVIA" Aug. 29, Of the 15 models release, 13 were accompanied by an RF remote control. Spring products announced in February 2008 and include RF control in new F, V1 & J1 Bravia LCDs Currently shipping over 40 products with Freescale RF solution including DTVs, Blu-ray DVD recorders, set back boxes, ipod Speaker with RF Remote and HD wireless link module All products use Freescale s MC SynkroRF Platform 8

9 SynkroRF Adoption EchoStar adopts SynkroRF for RF control of next generation DISH Network satellite set top box. VIP922S Set top Box announced at CES State of the art user interface using touchpad technology to reduce the number of buttons and enhance the user experience. CES Awards Best Home Video Product Best Remote Control Best User Interface VIP922S use Freescale s MC SynkroRF Platform Expected to be available to DISH Network subscribers in June

10 RF4CE Adoption Z1's separate input/output module with integrated QAM/ATSC tuner (top) and matching wireless transmitter (bottom) Panasonic Ultra-thin Z1 Series 1080p Plasma HDTV (TC-P54Z1) World s First RF4CE production product Launched in Japan in April. Expected globally in summer. Requires RF remote DTV too thin for tuner electronics Uses Wireless HD (60 GHz) to transmit uncompressed 1080p HD content Uses Freescale MC BeeStack Consumer (ZigBee RF4CE) Platform 10

11 IEEE Technology Overview 11

12 The 802 Wireless Space Where does the standard fit into short range wireless? It addresses the unique needs of monitoring and control: Low Power Long Battery Life Low Duty Cycle Low Data Rate Fast Power on Latency Low Cost WWAN WMAN WLAN WPAN Range IEEE RF4CE Bluetooth IEEE WiMax IEEE WiFi UWB a c Data Rate (Mbps)

13 IEEE Basics Simple packet data protocol for lightweight wireless networks Released in 2003, update in 2006 O-QPSK Modulation (2.4GHz) DSSS Energy Spreading Scheme Three bands, 27 channels specified 2.4 GHz: 16 channels, 250 kbps MHz : 1 channel, 20 kbps MHz: 10 channels, 40 kbps AES 128 Encryption and Authentication Communication Features Simple Frame Structure Reliable Data Delivery CSMA-CA Message Acknowledgement Association/Disassociation Network Support Employs 64-bit IEEE & 16-bit short addresses Supports Mesh, Star and Point-to-Point Non-Beaconed Beaconed Optional super frame structure with beacons Supports Guaranteed Time Slots (GTS) Frequency Band MHz MHz License Required? Region Data Rate No Europe 20kbps 1 Channels No Americas 40kbps MHz No Worldwide 250kbps 16 13

14 2.4 GHz Channel Occupancy b Channel Channel b Channel b Channel (end of ISM Band) b Channel (North America) b Spectrum Occupancy (Typical) Channel 14

15 The ZigBee Protocol Stack Mesh Networking on MAC/PHY RF4CE Technology Provides network services, frequency agility, security management, applications profiles, interoperability and certification testing IEEE STD Designed to supply the radio and protocol, allowing the designer to concentrate on the application and their customers needs APPLICATION PROFILES NETWORK LAYER MAC LAYER PHY LAYER Application RF4CE Stack Silicon OEM ZigBee RF4CE IEEE 15

16 IEEE Device Types Full function device (FFD) Talks to several devices Normally mains powered (always on) Can route messages Reduced Function Device (RFD) Carries limited functionality to control cost and complexity Talks to parent Requires less memory Can be a sleeping device General usage will be in network edge devices 16

17 IEEE Data Frame Format max. 102 Bytes max. 133 Bytes = 1064 bits = kbps min. 16 Bytes = 128 bits = kbps Provides up to 102 Byte data payload capacity Data sequence numbering to ensure that packets are tracked Robust structure improves reception in difficult conditions Frame Check Sequence (FCS) validates error-free data 17

18 Robustness in the 2.4 GHz Band Designed from ground up with co-existence in mind Direct Sequence Spread Spectrum Energy spread so signal looks like noise to other systems Symbol rate is 62.5 khz so a symbol only last 16 μs Provides 16 channels to help avoid interference Channel spacing provides slots in the non-overlapping bands Designed to minimize jamming susceptibility Adjacent and alternate channel rejection reduce likelihood of interference CSMA listens before transmitting and does a random back off in case of collision Message acknowledgement provides delivery status 18

19 Freescale Multi-Offering Approach with SMAC SynkroRF ZigBee RF4CE ZigBee / ZigBee PRO Customer Defined & Developed Customer Defined & Developed Customer Defined & Developed SynkroRF Customer Developed RF4CE Profiles ZigBee RF4CE Customer Developed ZigBee Profiles ZigBee/ ZigBee PRO S-MAC MAC MAC MAC MAC PHY Layer PHY PHY PHY PHY Hardware Hardware Hardware Hardware Hardware 19

20 RF4CE Network 20

21 ZigBee RF4CE from Freescale Semiconductor ZigBee RF4CE is a platform solution for wireless monitoring, control and complete automation for home consumer products. Enhanced RF Technology Two Way Communications Easy Device Configuration Improved consumer electronics experience with product differentiation in a cost sensitive market. Send information to remote control and eliminate extensive IR device databases. Simple device pairing for direct communication between any two devices. Resolves plasma TV high frequency inverter and LCD back light interference issues by offering a robust RF, message-acknowledged solution. Offers capability to download information to remote control such as program guides, stock information, news/alerts, push services etc. with reliable bi-directional communications. Provides simple device pairing through discovery process between two devices: a Controller and a Target device. Enhances battery life by up to 4X with fewer repeat messages and no need for line of site visibility. Control devices from anywhere! Allows manufacturers to provide an end product with value added RF features at a cost effective price point. Automates the user experience without needing to send serial messages to every device. Eliminates need to carry IR databases for thousands of devices in memory by learning capabilities of each device over the air. Support for Target to Target communications. Supports an extensive list of devices including DTVs, DVDs, set top boxes, remote controls, media centers, game consoles, satellite radios and many more! 21

22 ZigBee RF4CE Overview ZigBee RF4CE Features: Based on 2.4 GHz MAC/PHY IEEE standard Networking layer is thin, flexible and futureproof Co-exists with other 2.4 GHz technologies Support for interoperability Support for secure communications Power save mechanisms implemented in network layer Simple and intuitive pairing mechanism POWER SAVE TOPOLOGY APPLICATION PROFILES APPLICATION FRAMEWORK SECURITY NETWORKING LAYER CHANNEL AGILITY MAC LAYER PHY LAYER MANAGEMENT PAIRING OEM ZigBee RF4CE Network & Profiles IEEE Allow for vendor specific applications and transactions Support for many different applications Application ZigBee RF4CE Network & Profiles Silicon 22

23 Define pairing and discovery procedures Standardizes commands Ensures interoperability between devices ZigBee RF4CE Application Profiles First Applications Profile - Consumer Electronics Remote Control (CERC) Defines push button pairing process between controller and target Defines commands for basic CE device control User control pressed command carries HDMI CEC commands Support for manufacturer specific commands 23 23

24 ZigBee RF4CE Network Topology & Initialization Two Device Types Target: Start their own/individual PAN Controller: Join Target PAN as required Target device starts network Target responds with Discovery & Pair Responses Controller performs Discovery & Pair Requests Target Device Controller device 24

25 Co-existing star network topology Each Target device forms its own star network. ZigBee RF4CE Network Topology Target Device Allowed, but pairing method not defined in specification Controller device Pairing method defined in specification 25

26 ZigBee RF4CE - Possible Configurations TV RC TV RC PAN 1 TV DVD PAN 3 DVD RC PAN 1 TV Multifunction RC DVD PAN 3 DVD RC TV Multifunction RC DVD PAN 3 CD PAN 2 CD PAN 2 CD CD RC CD RC Independent-Coexisting Devices with Dedicated Remotes Independent-Coexisting Devices with Dedicated Remotes + Multifunction Remote Independent-Coexisting Devices with Single, Multifunction Remote Target node Controller node 26

27 ZigBee RF4CE Network Topology PAN 3 TV RC DVD DVD RC PAN 1 TV CD Target node Controller node CD RC PAN

28 ZigBee RF4CE Network Topology PAN 3 TV RC DVD DVD RC PAN 1 Multifunction RC TV CD Target node Controller node CD RC PAN

29 ZigBee RF4CE Network Topology PAN 3 TV RC DVD DVD RC PAN 1 Multi-function RC TV CD Target node Controller node CD RC PAN

30 ZigBee RF4CE Channel Agility b/g Channel b/g Channel b/g Channel GHz GHz Channel Agility b/g Channel b/g Spectrum Occupancy (Typical) Channel ZigBee RF4CE Channel All nodes support frequency agility Target specifies PAN base frequency Target can switch frequency on adverse channel conditions Other nodes know where the target was when attempting TX If target not found, nodes re-acquire by trying each frequency 30

31 RF4CE Device types 31

32 RF4CE Profile and vendor IDs Profile IDs Vendor IDs 32

33 ZigBee RF4CE Device Discovery The discovery process is responsible for finding target devices in the radio vicinity of the controller node that meet certain criteria. The discovery criteria could be a given device type, a given application profile, or simply any device that is within reach of the controller. DTV DTV Discovery Response RC Discovery Request (Multi-channel; Broadcast Transmission) RC Discovery Response (Single-channel; Unicast Transmissions) STB STB Target nodes matching the discovery criteria respond to discovery request as instructed by the application layer 33

34 ZigBee RF4CE Device Pairing The pairing process handles the association between two nodes of a ZigBee RF4CE network: a Controller node to a Target node. As future data exchange between the two nodes will be performed using the same PAN id and Short Source & Destination Addresses, the purpose of this process is for the Controller node to obtain a PAN id and a Short Address from the Target node. DTV DTV Pair Request RC Device List DTV STB RC A Target device is selected from the list of devices which responded to the Controller during discovery request. The selected Target device is sent a Pairing Request. STB A Pair Request is sent via unicast to the intended Target device. The device address information was obtained during the discovery process. STB 34

35 ZigBee RF4CE Security Utilizes the AES-128 core Security mode: ENC-MIC-32 Data confidentiality (via payload encryption) Data authentication (via Message Integrity Code) Replay protection (via frame counter) Nodes use 128-bit link keys Keys are generated automatically, if security is supported Keys are stored in the pairing table Application can decide which transmissions require security 35

36 ZigBee RF4CE Un-pairing An un-pair request can be originated by either the Target or Controller device in a pairing link. The requester will always succeed in removing the node from its pairing table. The recipient, will wait for the application before removing the requesting node from its pairing table. DTV RC Un-pair Request 36

37 ZigBee RF4CE Device Communications Communications can be originated by either the Target or Controller device and are asynchronous. Transmissions options available: Acknowledged Unicast Unsecured Single Channel Un-acknowledged Broadcast Secured Multi-Channel DTV RC Options can be combined depending on application RC would typically use acknowledged, unicast and multiple channel Pointing device would typically use unacknowledged, unicast, single channel 37

38 ZigBee RF4CE Power Save Two states for Power Save: Active & Standby Used in Target devices (controllers can simply turn off when no buttons are being pressed) Specification is 1 ma average current consumption while in standby mode Can be enabled and disabled by the application When Power Save is enabled: The node will have a duty cycle of no more than 1 second During the standby period (duty cycle - active period), the transceiver is off During the active period (minimum length of 16.8 msec), the target node's receiver will listen for incoming packets A data frame received during the active period must be fully processed before the target node can enter standby A network frame (discovery, pairing, etc.) will be ignored if received during the active period. Power save must be disabled to process network packets The application can always control the transceiver directly Power saving mechanism is aligned with Channel Agility nwkdutycycle (no more than 1 sec) Rx on nwkactiveperiod (min. of 16.8 msec) Rx off 38

39 Consumer Electronics Remote Control (CERC) Application Profile 39

40 Defines Stack and Application attributes nwkdiscoveryrepetitioninterval nwkmaxdiscoveryrepetitions nwkmaxreportednodedescriptors aplkeyrepeatinterval aplkeyrepeatwaittime ZigBee RF4CE - CERC Defines push-button pairing protocol Works in conjunction with existing network discovery & pairing services Discovery, pairing and key establishment (as required) all take place as defined in protocol Defines commands for basic CE device control User control pressed (carrying HDMI CEC commands) User control repeated User control released Defines command discovery command and response messages 40

41 Freescale s ZigBee RF4CE Private Application Profile 41

42 Fragmentation Bulk data transfer support Over the Air Menus Enhanced user interface options for devices Polling Freescale ZigBee RF4CE Private Profile Support for asynchronous Target to (sleeping) controller communications Remote Pairing Allows for Target devices to directly communicate 42

43 Freescale s ZigBee RF4CE Supported Devices 43

44 MC1321x Overview MCU Features 40 MHz HCS08 low-voltage, low-power core Flash and memory dependent on part Multiple 16-bit timers Up to 38 GPIO 8-bit port keyboard interrupt (KBI) 8-channel 10-bit analog-to-digital converter (ADC) SCI interface supporting up to kbaud I2C with 100 kbps maximum bus loading Low-voltage detection In-circuit debug and Flash programming Common on-chip processor (COP) watchdog timer RF Features compliant 2.4 GHz RF transceiver 250 kbps O-PQSK modulation 16 selectable channels Auto-trim feature for crystal accuracy Eliminate need for external variable capacitors Allows for automated production frequency calibration Programmable from -27 dbm to +3 dbm RX sensitivity of -92 dbm Integrated Transmit/Receive switch Supports single-ended or full differential operation Features -40 to +85 degrees C operating temperature 2V to 3.4V Low external component count Requires a single 16 MHz crystal Programmable frequency clock output for MCU 9x9x1 mm 71-pin LGA package RoHS compliant Availability Shipping in volume since September 2006 Tx/Rx Switch Analog Receiver Frequency Generator Analog Transmitter IRQ Arbiter Power Management Digital Transceiver Buffer RAM RFIC Timers Digital Control Logic RAM Arbiter Voltage Regulators HCS08 CPU FLASH Memory RAM Low Voltage Interrupt Keyboard Interrupt Internal Clock Gen Background Debug Module 8-ch 10-bit ADC 2 x SCI IIC 16-bit Timers COP Features MC13211 MC13212 MC13213 Protocol Stack SMAC SMAC IEEE Memory 16 KB Flash 1KB RAM 32 KB Flash 2 KB RAM K SRP $3.10 $3.38 $3.71 Up to 39 GPIO SMAC SynkroRF IEEE ZigBee RF4CE ZigBee 60 KB Flash 4KB RAM 44

45 Features Integrated 2.4 GHz transceiver with 32-bit CPU Compliant transceiver ARM7TDMI up to 26Mhz Lowest power Significant power reduction 21 ma Rx & 29 ma Tx with radio and MCU <1uA hibernate current Large Memory 128KB Serial Flash, 96KB RAM 80KB ROM containing MAC, device drivers and boot code Improved RF performance -96 dbm sensitivity (DCD mode) -100 dbm (NCD mode, +2-3 ma current) +5 dbm power output Hardware accelerator reduces MCU overhead MAC accelerator AES 128-bit hardware encryption/decryption Best in class peripherals UART, SPI, KBI, 8 channel 12-bit ADC, 4x16-bit timer, I 2 C, SSI (I2S), 64 GPIO Unique platform in a package RF matching in package Requires power, crystal and 50 Ohm antenna 9.5 mm x 9.5 mm 99-pin LGA MC1322x Platform in a Package (PiP) Balun TX/RX Switch Analog TX Analog RX 24 MHz (Typical) KHz (Optional) Digital Modem TX Modem RX Modem MAC Accelerator (MACA) IEEE Transceiver MC1322X Block Diagram Buck Converter Analog Power Management & Voltage Regulation RF Oscillator/PLL & Clock Generation Advanced Security Module (ASM) SPI FLASH Module (SPIF) 128 KB Serial FLASH Features Protocol Stack Memory Clock & Reset Module (CRM) CPU Complex ARM7 TDMI-S 32-bit CPU Bus Interface & Memory Arbitrator ARM Interrupt Controller (AITC) 96 KB RAM 80 KB ROM Battery Monitor K SRP $4.74 Data & Address Buses MC13224V SMAC SynkroRF IEEE ZigBee RF4CE (Q209) ZigBee ZigBee Pro 128 KB Serial Flash 96 KB RAM 80 KB ROM Timer Module SCI/UART Module SCI/UART Module SSI/I 2 S Module I 2 C Module Keyboard Interface SPI Interface GPIO Control 12-bit ADC 12-bit ADC JTAG & Nexus Up to 64 GPIO 45

46 MC1321x Development Hardware 2nd generation development kit Based on Freescale s MC compliant 2.4GHz SiP LEDs and switches for demonstration monitoring and control Flash reprogramming and in-circuit hardware debugging USB multilink programmer/debugger Includes CodeWarrior Range approximately 400m line-of-sight 1321xCSK-BDM One (1) 1321x-SRB (sensor reference boards) One (1) 1321x-NCB (network control board) LCD for demonstration messaging SMA connector for external antenna connection ZigBee RF4CE Out-of-Box Remote Control Application 1321x-SRB 1321x-NCB 46

47 Feature 1321x Developer s Starter Kit MC1321x Development Tools Summary 1321x Consumer Starter Kit 1321x Network Starters Kit SRB NCB N/A 1 1 CodeWarrior IDE Special Edition Special Edition Special Edition BeeKit with BeeStack ZigBee Protocol Stack (Available Dec 06) ZigBee Packet Analyzer Hardware BeeKit with 90-day evaluation of Bee-Stack 1321x /ZigBee Development Kit 4 No No No Yes Protocol Analyzer No No No Out-of Box Application RF4CE Remote Control RoHS Compliant Yes Yes Yes Yes Price BeeKit with 90-day evaluation of Bee-Stack Accelerometer Demo $ XDSK $ XDSK- BDM $ XCSK-BDM Recommended for RF4CE Development Available Now BeeKit with 90-day evaluation of Bee-Stack Wireless UART $ XNSK $ XNSK-BDM 3 Special Edition, Standard Edition (1321XEVK-SFTW only) BeeKit with 90-day evaluation of BeeStack, Full Node Lock Version (1321XEVK-SFTW only) Daintree Standard Edition ZigBee Environment Demonstration (ZeD) $ XEVK $ XEVK- SFTW 47

48 MC1322x Development Hardware Based on Freescale s 3 rd Generation GHz PiP 1322x-SRB MMA7260Q 3-axis Acceleration Sensor, MPXV5010G Pressure Sensor and Temperature Sensor 2.5 mm Headset/Audio In jack Speaker Joystick, buttons & LEDs 1322x-SRB 1322x-NCB Graphic LCD display 2.5 mm Headset/Audio In jack Speaker Joystick, buttons & LEDs SMA connector Nexus debug interface 1322x-USB 1322x-NCB 1322x-LPB Supports on-chip buck converter Lowest power board for current measurements 1322x-USB USB dongle and /ZigBee packet sniffer 1322x-LPB 48

49 Feature 1322x USB Kit MC1322x Development Tools Summary 1322x Developer Starter Kit 1322x Network Starter Kit 1322x /ZigBee EVK End Node Coordinator Low Power Node USB Node J-Link JTAG Debugger N/A N/A N/A 1 No 1 1 N/A N/A Yes Yes Yes IAR 32K Edition IAR IDE IAR 32K Edition IAR 32K Edition IAR 32K Edition (256K Edition- 1322xEVK-SFTW only) BeeKit with BeeStack ZigBee Protocol Stack BeeKit with 90- day evaluation of BeeStack Protocol Analyzer No No No Out-of Box Application None BeeKit with 90-day evaluation of BeeStack Weather Station Sensor Demo BeeKit with 90-day evaluation of BeeStack Network Demo BeeKit with 90-day evaluation of BeeStack (Full Node Locked Version XEVK-SFTW only) Daintree Basic Edition ZigBee environment Demonstration (ZeD) RoHS Compliant Yes Yes Yes Yes $ xEVK Price $ xUSB $ xDSK-DBG $ xNSK-DBG $ xEVK-SFTW Recommended for SynkroRF/RF4CE Development 49

50 Reference Designs Development Board Reference Design Based on development boards and include I/O, headers and additional functionality FCC and CE certified Provide Schematic in OrCAD Layout in Gerber BOM Direct support in BeeKit Form Factor Reference Designs Form factor design with minimal I/O and headers Focus is on RF design Single Port Design Chip or F Antenna Basic Interfaces UART, I2C Provide Reference Manual Schematic in OrCAD Layout in Gerber and Allegro BOM BeeKit Platform Editor Configuration File Dev Board Reference Design 1319xEVB 1320x-QE128DSK 1320xRFC 1321xNCB 1321xSRB 1322xLPB 1322xNCB 1322xSRB 1322xUSB Form Factor Reference Design 1320xQE128-IPB 1321x-ICB 1321x-IPB 1321x-UCB 1322x-IPB/ICB (Pending) 1322x-ERB (Pending) 50

51 ZigBee RF4CE USB Dongle Application USB 2.0 FS USBDP USBDM BDM LDO 3.3V USB to Serial FT232RQ T M MC13213 Balun 50:200 RF4CE Dongle MC GHz RF4CE compatible RF Interface Black-Box SW for MC13213 (available through BeeKit) - to assist in systems where the RF is to be used as a "dongle" or extension to a main CPU FTDI Virtual Com Port / USB to Serial bridge USB 2.0 Full Speed Compatible Minimum BOM requirements Small size: 60x20x10 mm inc USB connector Key Advantages Simple add-on to enable any USB enabled device to provide development environment / demonstrations Easily retrofit RF4CE to an existing system (e.g. STB or Media PC) without needing to modify the main board Multiple OS supported FSL provides full design information 51

52 Freescale RF4CE USB Dongle ZigBee RF4CE USB Dongle Application Simplifies the addition of RF4CE to an existing USB enabled system Complimentary Multiple OS Support from FTDI FTDI Drivers available at: Vendor ID - VIP / PID are also available OS Support: Windows Vista (32/64 Bit) XP (32/64 Bit) 2000 / 98 / ME Mac OS X / OS 9 / OS 8 Linux Windows CE 52

53 BeeKit 53

54 BeeKit Overview A New Approach to Wireless Applications Development: Graphical user interface (GUI) to create, and validate network configuration Codebases deliver libraries, templates and applications Exports directly to IDE for development and debug 54

55 BeeKit Overview Provides a development environment where wireless link and protocol configurations can be managed in a straightforward, uncomplicated approach. Complementary tool to traditional IDEs. Not just a tool for generation of static starter code, but rather an extension to embedded application environments. Supports Simple MAC (SMAC), IEEE MAC, SynkroRF, ZigBee-RF4CE and ZigBee application development on HCS08 and MC13224 Processors Freescale ZigBee-RF4CE Stack (BeeStack Consumer) interface reuses Freescale s MAC messaging interface for a common user experience. Experience gained with one helps understand the other. Applications are decoupled from the stack implementation. Allows for easy code updates and promotes code reuse. 55

56 BeeKit Definitions A codebase contains all the information that is required for BeeKit to interact with the user and create a project for a specific communication stack. Freescale provides a codebase in the form of: A database containing the embedded software component source files (platform components, applications, etc.) and pre-compiled libraries (SMAC, MAC, etc.) Configuration files that hold information about the organization of the embedded software components, their configurable parameters and features, and the BeeKit GUI information Freescale provides each codebase. The user does not modify it, but uses BeeKit to generate stack-based directory structures external to the codebase. A solution contains one or more BeeKit projects drawn from a single codebase. A project in BeeKit is a complete collection of attributes that define a stack and application configuration for a particular target platform. A project exported from BeeKit consists of assembled codebase components (source files, libraries) and an XML file (CW) or EWP file (EWARM) that describes the project. 56

57 BeeKit Development Flow Start BeeKit Create project Customize & validate Project Export Project Import into IDE 57

58 Hands-on Lab 58

59 Laboratory Exercise GOAL: Creation, deployment and modification of a 2-node RF4CE system One controller One target (TV) Procedure Creation of controller and target projects using BeeKit Exporting projects from BeeKit into CodeWarrior IDE Project compilation and loading into development hardware Exercising of RF4CE functionality Modification of target (TV) device functionality Re-building and re-loading of images to development hardware Exercising of RF4CE Functionality 59

60 MC13213-NCB Buzzer GPIO Connectors RF Connector Debug USB Connector Serial (DB9) Connector MC13213 IC F - Antenna LCD Display DC Supply Reset Button Power Switch Buttons (SW1-SW4) 60

61 MC13213-SRB Buzzer 3-Axis Acceleration Sensor GPIO Connector Debug USB Connector DC Supply F - Antenna MC13213 IC Power Switch Reset Switch Buttons (SW1-SW4) 61

62 2-Node RF4CE System SimpleTV NCB simulates and RF4CE TV LCD displays device status & messages received from controller Buttons provide typical TV functionality Virtual Remote Control PC application serves as GUI SRB provides the RF4CE network PC application talks to SRB using BlackBox protocol 62

63 BlackBox vs. ZTC Application ZTC is a Freescale proprietary application that allows for monitoring and exercising of the various protocol layers which comprise the various IEEE based protocols Allows a host to monitor/inject inter-layer messages Intended for use during protocol evaluation and prototype building BlackBox is a ZTC-based application with defined functionality Think about a modem with an AT-command set Intended to be used as a dongle to a main application processor APPLICATION PROFILES APPLICATION FRAMEWORK POWER SAVE SECURITY NETWORKING LAYER MANAGEMENT TOPOLOGY CHANNEL AGILITY PAIRING MAC LAYER PHY LAYER 63

64 ZTC Application Requirements for Virtual Remote BeeStack Consumer CodeBase includes a BlackBox application template for a controller node. It includes support for accessing all the network features and the following profile services: CERC Profile: Controller-side Push Button Pair CERC Profile: Sending and receiving commands FSL Private Profile: Fragmented data reception FSL Private Profile: Poll-originator side Virtual Remote PC application requires a BlackBox which supports all network features and the following profile services: CERC Profile: Controller-side Push Button Pair FSL Private Profile: Over the Air Menu Browser FSL Private Profile: Over the Air Menu Displayer We need to build our own BlackBox application!!! 64

65 BeeKit: Project Creation and Export 65

66 Run BeeKit Start->Programs->Freescale BeeKit->Freescale BeeKit Select Codebase in BeeKit File> Select Codebase Select HCS08 BeeStack Consumer Codebase Press Set Active Step 1: Select Codebase 66

67 Step 2: Start New Project by Selecting Template Start New Project File> New Project Select RF4CE Demo Apps Select ZTC Node App If the message The File My Solution already exist. Would you like to replace the file? press Yes 67

68 Step 3: Configure Template The Configuration Wizard will guide you through the configuration of key parameters Press Next to continue 68

69 Step 4: Select Target HW for Application Select the HW to be used when running the application Select MC1321x-SRB and press Next 69

70 Select platform modules to be used Leave default options unchanged Press Next Step 5 Configure Platform Modules 70

71 Step 6 Configure Communication Options Select communication port to be used Leave default option for SCI(UART) unchanged Press Next 71

72 Step 7 Configure SCI Parameters Select physical UART to be used and communication speed Leave default option for Enable UART on USB unchanged Select as the baud rate and press Next 72

73 Step 8 Configure Profile Functionality Select profile functionality to be included Match the CERC functionality as shown Match the FSL private profile functionality as shown and press Next 73

74 Select discovery options Leave default functionality unchanged Press Finish Step 9 Configure Discovery Options 74

75 Step 10: Inspect Project You can inspect and edit the properties in Solution Explorer Help screen provides more info 75

76 Step 11: Create Additional Projects: SimpleTV Add a SimpleTV application to the solution by following the steps below: 1. Right-click on the Solution Explorer window 2. Select Add Project Select RF4CE Demo Apps 4. Select Simple TV App 5. Press OK 6. Follow Configuration Wizard Accept all defaults on the Hardware, Platform Modules, and Parameters screens On the Set Device Identifiers screen, modify the default values as follows: Enter a name of your choosing (max: 14 characters) for identification string Enter the Extended Address found in the sticker on bottom side of MC13213 NCB Enter a device vendor name of your choosing (max: 6 characters) Accept defaults on the Set Discovery Options Screen 76

77 Step 12: Export Solution and Open in CodeWarrior Export and Open Solution in CodeWarrior Select Solution -> Export and Open Solution in CodeWarrior Select all projects Press OK 77

78 Step 13: Explore the Source Code Explore the Source Code Do not make any changes 78

79 CodeWarrior: Project Build and Download 79

80 Step 14: Explore the Source Code Explore the Source Code Do not make any changes 80

81 P&E Micro Multilink USB cable goes here LED indicates that Target device is powered Connector to target BDM interface LED indicates that Multilink is powered Pin 1 (Red) 81

82 Step 15: Prepare SRB for Programming Set the power switch on SRB to the OFF position Connect a USB cable between the SRB and the host computer Connect the Multilink to a computer USB port Make sure multilink is powered (power LED is ON) Connect the Multilink BDM connector to the BDM connector on the Sensor Node board (SRB) Ensure pin one on the Multilink cable (red wire) is lined up with pin one on the SRB Pin 1 Power ON the Board. 82

83 Step 16: Configure ZTC Node App Project Select ZTC Node App Project in CodeWarrior Press the Settings button 83

84 Step 17: Configure Compiler Settings (1) Select Compiler for HC08 from the Target Settings list 84

85 Step 18: Configure Compiler Settings (2) Compiler for HC08 from the Target Settings Panel Place cursor at end of the Command Line Arguments input box 85

86 Step 19: Configure Compiler Settings (3) Using the back arrow key Traverse the command line arguments until you find -DgBlackBoxDevice_d=0 86

87 Change the command line argument to read: -DgBlackBoxDevice_d=1 Step 20: Configure Compiler Settings (4) This indicates that you plan to use the ZTC application as a BlackBox 87

88 Step 21: Configure Compiler Settings (5) Press on Apply Press on OK 88

89 Select ZTC Node App Project in CodeWarrior Press the Debug button Step 22: Build ZTC Node App Project 89

90 Step 23: Download ZTC Node App Project to SRB Pressing the Debug button (previous step) initiated a project build & download to the target hardware The True-Time Debugger will automatically launch When the PEMICRO Connection Manager appears, press Connect Programmer window will appear automatically and provide statistics on the download process When downloading is complete, you will see the message Postload command file correctly executed Device is now programmed Disconnect Multilink from SRB Close (File>Exit) the True-Time Debugger window Turn power switch on SRB to the OFF position 90

91 Step 24: Prepare NCB for Programming Set the power switch on NCB to the OFF position Ensure that batteries are properly loaded into the board Connect the Multilink to a computer USB port Make sure multilink is powered (power LED is ON) Connect the Multilink BDM connector to the BDM connector on the NCB Ensure pin one on the Multilink cable (red wire) is lined up with pin one on the NCB Pin 1 Power ON the Board 91

92 Select Simple TV App Project in CodeWarrior Press the Debug button Step 25: Build SimpleTV Project 92

93 Step 26: Download SimpleTV Project to NCB Pressing the Debug button (previous step) initiated a project build & download to the target hardware The True-Time Debugger will automatically launch When the PEMICRO Connection Manager appears, press Connect Programmer window will appear automatically and provide statistics on the download process When downloading is complete, you will see the message Postload command file correctly executed Device is now programmed Disconnect Multilink from NCB Close (File>Exit) the True-Time Debugger window Turn power switch on NCB to the OFF position 93

94 Exercising RF4CE Functionality 94

95 Step 27: Starting the SimpleTV Turn power switch on NCB to the ON position Press the Reset button on the NCB The SimpleTV device will automatically start TV off Network initializing TV off Network initialized TV off The LCD will present messages on the status of the device: Network initializing Network Initialized TV off At this state, the SimpleTV has successfully started and is ready for operation (NOTE: the LEDS will flash in sequence while the SimpleTV is OFF) 95

96 Step 28: Starting the Virtual Remote Make sure the SRB is connected to the PC via USB cable Turn power switch on SRB to the ON position Run the VirtualRemote PC application Double click on the Virtual Remote shortcut on the desktop OR Start->Programs->Freescale BeeKit->Virtual Remote->Virtual Remote The Virtual Remote application will present messages on its status: Auto-detecting the BlackBox device (SRB) Initializing the BlackBox connection Application started 96

97 Step 29: Pairing the Virtual Remote with the SimpleTV Devices must be paired to one another before they can communicate Applications implement the CERC profile Use Push Button Pairing mechanism Press any of the softkeys in the Virtual Remote to initiate the pairing process Soft Keys Soft Keys TV off SW4 Long press (hold down for 2+ seconds) SW4 on the SimpleTV (NCB) to initiate the paring process 97

98 Was pairing successful? Or did you observe pairing failures? Was Pairing Successful? Per CERC specification, the controller expects only ONE device to respond to Discovery Requests while in Push Button Pairing mode Per CERC specification, the target expects only one controller to be doing the discovery/pairing while on Push Button Pairing mode We have multiple controllers and targets trying to pair at the same time. By specification, this will fail. PLEASE FOLLOW INSTRUCTOR S INSTRUCTIONS TO FACILITATE THE ORDERLY PAIRING OF ALL SETUPS IN THE CLASS 98

99 Successful Pairing TV off Push Button Pair Each device will provide status messages Virtual Remote Pairing with TV : The discovery/pairing process is enagaged TV OFF : Pairing process complete. Showing status of pairied device Paired with FSL Remote SimpleTV Push Button Pairing : The discovery/pairing process is engaged Paired with FSL Remote : Pairing process complete TV OFF : The device has returned its display to status mode TV off 99

100 Step 30: Using the Virtual Remote & SimpleTV The user interface in the devices can be used to send messages between them NOTE: All local changes in the SimpleTV (e.g. Vol +/-) are reported to the Virtual Remote Volume : 13 Channel : 58 When TV is ON, Long button press on SW1 turns it OFF Vol - CH - Vol + CH + When TV is OFF, Any button turns it ON 100

101 Modifying Target Device Functionality 101

102 The Task at Hand SimpleTV volume control is accomplished by two methods Volume control commands from Virtual Remote Volume control buttons on SimpleTV device What we will do Identify common function that alters volume status Modify application to control device volume in steps of two instead of one 102

103 Close the project titled ZTC Node App.mcp Click on the x in the project window Step 31: Return to CodeWarrior 103

104 Step 32: Navigate SimpleTV Source Code Extend the project view to show the application source files Click on + next to NwkApps to extend file view 104

105 Step 33: Open Source File for Modification Open NwkApp.c source file Double-click on NwkApps.c filename to open file 105

106 Step 34: Locate Function to be Modified Navigate to function App_SetTvVolume in NwkApp.c source file Click on the {.} icon on the editor s toolbar From the list of functions displayed, select App_SetTvVolume 106

107 Step 35: Modify Volume Up Functionality Update function to alter TV volume in steps of 2 In the switch(settype) statement, locate case for gsetoneup_c Update line appvolatileparams.tvvolume++; to increase volume by two instead of one. 107

108 Step 36: Modify Volume Down Functionality Update function to alter TV volume in steps of 2 In the switch(settype) statement, locate case for gsetonedown_c Update line appvolatileparams.tvvolume--; to decrease volume by two instead of one. 108

109 Save changes made to NwkApp.c Click the Save icon on the toolbar Step 37: Save Source Code Changes 109

110 Step 38: Prepare NCB for Programming Set the power switch on NCB to the OFF position Ensure that batteries are properly loaded into the board Connect the Multilink to a computer USB port Make sure multilink is powered (power LED is ON) Connect the Multilink BDM connector to the BDM connector on the NCB Ensure pin one on the Multilink cable (red wire) is lined up with pin one on the NCB Pin 1 Power ON the Board 110

111 Select Simple TV App Project in CodeWarrior Press the Debug button Step 39: Build SimpleTV Project 111

112 Step 40: Download SimpleTV Project to NCB Pressing the Debug button (previous step) initiated a project build & download to the target hardware The True-Time Debugger will automatically launch When the PEMICRO Connection Manager appears, press Connect Programmer window will appear automatically and provide statistics on the download process When downloading is complete, you will see the message Postload command file correctly executed Device is now programmed Disconnect Multilink from NCB Close (File>Exit) the True-Time Debugger window Turn power switch on NCB to the OFF position 112

113 Exercising RF4CE Functionality 113

114 Step 41: Starting the SimpleTV Turn power switch on NCB to the ON position Press the Reset button on the NCB The SimpleTV device will automatically start TV off Network initializing TV off Network initialized TV off The LCD will present messages on the status of the device: Network initializing Network Initialized TV off At this state, the SimpleTV has successfully started and is ready for operation (NOTE: the LEDS will flash in sequence while the SimpleTV is OFF) 114

115 Step 42: Reset the Virtual Remote Press the Clear button on the Virtual Remote to remote the SimpleTV from the remote s pairing table The Virtual Remote will return to its initial status, allowing the pairing process to be re-started Press to remove SimpleTV from Pairing Table 115

116 Step 43: Pairing the Virtual Remote with the SimpleTV Devices must be paired to one another before they can communicate Applications implement the CERC profile Use Push Button Pairing mechanism Press any of the softkeys in the Virtual Remote to initiate the pairing process Soft Keys Soft Keys TV off SW4 Long press (hold down for 2+ seconds) SW4 on the SimpleTV (NCB) to initiate the paring process 116

117 Step 44: Using the Virtual Remote & SimpleTV The user interface in the devices can be used to send messages between them Verify that volume operations (up/down) now alter device operation by a factor of 2 Volume : 13 Channel : 58 When TV is ON, Long button press on SW1 turns it OFF Vol - CH - Vol + CH + When TV is OFF, Any button turns it ON 117

118