ZIG09115ZCP2855824

Datasheets.org.uk - 100 Million Datasheets from 7500 Manufacturers.

Datasheet Thumbnail

Top Searches for this datasheet

STM32W108hb* - STM32W108hb*
STM32W108 zigbee user manual - STM32W108 zigbee user manual
STM32W108 zigbee - STM32W108 zigbee
STM32W108* - STM32W108*
STM32W* - STM32W*
RF remote control - RF remote control
Electronics Workbench software free download - Electronics Workbench software free download
DVD ID 802 - DVD ID 802
ZIG09115ZCP2855824 - ZIG09115ZCP2855824

UM0909 User manual
STM32W108xx ZigBee® RF4CE library
This document describes RF4CE library develop RF4CE compliant applications STM32W device. document describes initially RF4CE protocol defined ZigBee alliance then describes RF4CE library implements STM32W. document describes also perform some common RF4CE operation well some architecture dependent operation. Finally describes some reference application Target Controller nodes. STRF4CE platform including STM32W associated RF4CE software library been certified ZigBee RF4CE compliance platform December 2009, with Certification number: ZIG09115ZCP2855824. ZigBee RF4CE library designed STM32W108 engineering samples STM32W108xBU63 microcontroller.
Terms definitions
Table List terms
Term CERC HDMI NLDE NLME RF4CE Acknowledgment Application programming interfaces Consumer electronics remote control High-Definition Multimedia Interface Medium Access Control Network layer data entity Network layer management entity volatile memory Personal Area Network Physical layer Remote control device Radio Frequency Consumer Electronics Service Access Point Meaning
February 2010
17097
1/29
www.st.com
Contents
UM0909
Contents
RF4CE protocol description
Overview Network layer
1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 1.2.6 1.2.7 1.2.8 Node types Network topology Frequency agility Discovery Pairing Message transmission reception Security Power-saving
CERC application profile
Using STRF4CE
Programming model
2.1.1 mapping
Initialization
2.2.1 2.2.2 Controller Target
Discovery Pairing Message exchanges Security Timer Power consumption
2.8.1 2.8.2 2.8.3 power down power down standby
2.10
volatile memory management RF4CE Stack configuration
Designing application using RF4CE library
2/29
17097
UM0909
Contents
RF4CE Demo application
Firmware common features Building firmware Programming MB851 firmware RS-232 Remote Control Target applications Virtual
4.5.1 4.5.2 Virtual Virtual
Primer2 Sony Infrared (with RF4CE extender)
Reference documents Revision history
17097
3/29
RF4CE protocol description
UM0909
RF4CE protocol description
Overview
ZigBee® RF4CE standard created consortium companies with objective deliver standardized specification RF-controlled home entertainment products. (radio frequency) remote controls faster, more reliable provide more freedom operate devices from greater distances removing line-of-sight barrier found today's (infrared) remote controls. They also enable advanced features such two-way communication between device remote control, creating richer experience consumers. RF4CE standard defines network layer consumer electronics remote control (CERC) application profile. following section gives more details network layer CERC profile.
Network layer
RF4CE network stack thin, flexible future-proof layer with following features:
Based MAC/PHY IEEE 802.15.4 standard Networking layer thin, flexible future-proof Co-exists with other technologies Support interoperability Support secure communications Powersave mechanisms implemented network layer Simple intuitive pairing mechanism Allow vendor specific applications transactions Support many different applications
Figure shows layered representation RF4CE stack. more details about network layer, please refer [1]. Figure RF4CE stack overview
Application Layer Profiles Application Framework
Power Save Topology Security
Management Channel Agility Pairing
Networking Layer Layer Layer
ZigBee RF4CE Network Profiles
IEEE 802.15.4
Ai15287
4/29
17097
UM0909
RF4CE protocol description
1.2.1
Node types
RF4CE standard defines only node types with different roles:
Target Node with following capabilities: Network Startup Full capability Accepts declines pairing request Makes decision operating channel (frequency agility) Initiates pairing discovery process with Target nodes Implements frequency agility On-demand communication
Controller Node with following capabilities:
1.2.2
Network topology
ZigBee RF4CE PANs essentially point-to-point star topologies with single node acting target device many nodes acting remote controls. routing allowed communication happens between nodes within range. ZigBee RF4CE Network also supports multiple PANs participation multiple networks (Figure Figure RF4CE multi-PAN network
Figure illustrates example ZigBee RF4CE topology which includes three target nodes: player each target node creates PAN. player also have dedicated remote controls which paired each appropriate target node. multi-function remote control, capable controlling three target nodes itself, added network successively pairing desired target nodes. also paired with that external channel selected when played. consequence, this remote control network consists three separate remote control PANs: managed (PAN containing remote control, multi-function
17097
5/29
RF4CE protocol description
UM0909
remote control DVD; second managed player (PAN containing remote control multi-function remote control third managed (PAN3) containing remote control, multi-function remote control
1.2.3
Frequency agility
ZigBee RF4CE Networks operate following IEEE 802.15.4 channels:
Channel 2.425 Channel 2.450 Channel 2.475
Both target controller node types support frequency agility. Target nodes specify base frequency decide switch frequencies adverse channel conditions. detection channel busy condition implementation dependent. Frequency reacquisition achieved through mechanism that allows other nodes trying each frequency once found, channel information stored future communications.
1.2.4
Discovery
discovery procedure builds list devices vicinity". Discovery requests sent originating device (for example, broadcast, multi-channel service multiple devices respond. discovery request also contains originator information allow device respond. When discovery request received, recipient devices normally inform application event. application decides whether respond discovery request. recipient device (for example, television) sends discovery response directly back originator (for example, using unicast service. discovery response contains recipient information. When discovery procedure completed, originator devices inform application discovery information. application then decides whether pair with particular device.
1.2.5
Pairing
Pairing procedure required establish link between devices radio range that wish communicate. Pairing required prior device communications performed only once. Pairing information stored non-volatile memory that retrieved after power cycling. Pairing similar discovery where originator recipient information exchanged application full control whether accept not. Both originator recipient create pairing table entries that contain addressing information security information applicable. application uses these entries reference index.
6/29
17097
UM0909
RF4CE protocol description
1.2.6
Message transmission reception
Message exchange supported between paired devices only transmission options include:
Acknowledged Originator data confirmed recipient Originator data confirmed recipient Originator data sent specific recipient Originator data sent recipients Originator attempts transmission expected channel only Originator attempts transmission using frequency re-acquisition mechanism Unacknowledged Unicast Broadcast Single channel Multiple channel data sent secured unsecured typically acknowledged, unicast multiple channel options Target devices typically unacknowledged, unicast, single channel options
options combined depending application, example:
1.2.7
Security
Security established during pairing process between nodes that both support security their node capabilities. security mechanism following features:
Utilizes AES-128 encryption Security mode: ENC-MIC-32 Data confidentiality (via payload encryption) Data authentication (via Message Integrity Code) Replay protection (via frame counter) Nodes 128-bit link keys Keys generated automatically, security supported Keys stored pairing table
application decide which transmissions require security.
1.2.8
Power-saving
RF4CE specification defines 2-state power-save scheme: Active Standby. normal cases, simply power when buttons being pressed, while target devices must also power-saving techniques when Standby. Targets must also ensure reasonable (human) reaction time exit from Standby. achieve this, power-saving techniques active period during which target wakes duty cycle which device repeats active period shown Figure
17097
7/29
RF4CE protocol description Figure Power saving scheme
UM0909
CERC application profile
CERC application profile first application profile defined RF4CE protocol. aims replacing remote controls that traditional infrared technology. defines very simple push-button pairing process between remote control target device. mechanism works conjunction with existing ZigBee RF4CE discovery pairing mechanisms. Discovery, pairing security (optional) take place single press button. This application profile also defines commands basic device control, such remote control pressed, remote control repeated remote control released. those carry embedded HDMI commands (see [3]). CERC also provides support manufacturer specific commands.
8/29
17097
UM0909
Using STRF4CE
Using STRF4CE
Programming model
STRF4CE library very efficient implementation based MAC/PHY layer specifically tailored RF4CE applications. features simple efficient management store non-volatile data preserve network layer state across power cycling. RF4CE also implements power management functions only radio part compliance with RF4CE specifications. same code base used both target controller node types. defined with close defined specification. designed implemented non-blocking; that network layer operations will give back control application when waiting event. core RF4CE compliant application implemented through never-ending loop where network layer state machine application state machine run. while blocking call application state machine ApplicationTick(); blocking call network layer state machine (void) NWK_Tick();
2.1.1
mapping
provided STRF4CE library defines functions that implement mapping according Table table, term means that implemented function call, term `RF' means that implemented function return value term means that implemented function callback called context NWK_Tick provided user. Each returns following values:
SUCCESS: Operation completed successfully RF4CE_SAP_PENDING: Operation started pending; final result will given matching callback. RF4CE_BUSY: Operation started because network layer still performing some other operation network layer been initialized. other value: Error context specific operation. mapping
Conf
Table
AUTO-DISC COMM-STATUS DISCOVERY GET/SET
17097
9/29
Using STRF4CE Table mapping (continued)
PAIR RESET RX-ENABLE START UNPAIR UPDATE-KEY DATA Conf
UM0909
Initialization
network layer initialized calling NWK_Init API. NWK_Init used initialize network layer according following parameters: nodeCap: node capabilities defined RF4CE specifications. forceColdStart: `True', this Boolean parameter allows network layer perform cold start (for example, first startup outside factory). Otherwise will perform warm start, defined RF4CE specifications.
normal scenarios, should called with defined node capabilities with forceColdStart FALSE. there mismatch between content memory node capabilities, value RF4CE_NVM_DATA_INVALID returned meaning that data contains invalid data; this case, initialization with forced cold start required. This normally requested once when device first used outside factory very special cases, not, example, event power loss (such battery replacement).
2.2.1
Controller
controller initialized immediately status returned accordingly. call successful, value `SUCCESS' returned network layer ready communication. example code controller initialization status NWK_Init(0, FALSE); (status RF4CE_NVM_DATA_INVALID) warm start fails, cold start status NWK_Init(0, TRUE);
2.2.2
Target
Network layer initialized immediately case warm start returning SUCCESS. case cold start, will return RF4CE_SAP_PENDING, meaning that network initialization will completed with call user-defined callback NLME_START_confirm. example code target initialization void NLME_START_confirm (u32 *status)
10/29
17097
UM0909 printf("RF4CE network started\r\n"); networkStarted TRUE; status NWK_Init(1, FALSE); (status RF4CE_NVM_DATA_INVALID) warm start fails, cold start status NWK_Init(1, TRUE); while (networkStarted FALSE) (void) NWK_Tick();
Using STRF4CE
Discovery
device discovery operation started both target controller node with call NLME_DISCOVERY_request with appropriate parameters. case success, returns RF4CE_SAP_PENDING value discovery result communicated through user-defined callback NLME_DISCOVERY_confirm. Only target nodes notified device discoveries user-defined callback NLME_DISCOVERY_indication. target node respond discovery indication using NLME_DISCOVERY_response API. case success, this returns RF4CE_SAP_PENDING value discovery response status communicated through user-defined callback COMM_STATUS_indication. example code device discovery status; NLME_DISCOVERY_REQUEST_Type param; param.DstPANId 0xFFFF; param.DstNwkAddr 0xFFFF; param.OrgAppCapabilities 0x12; param.OrgDevTypeList[0] 0x01; param.OrgProfileIdList[0] 0x01; param.SearchDevType 0xFF; param.DiscProfileIdListSize 0x01; param.DiscProfileIdList {0x01, 00}; param.DiscDuration 0x0016e36; status NLME_DISCOVERY_request (&param);
Pairing
Device pairing required prior starting communication with RF4CE node. Device pairing started both target controller node with call NLME_PAIR_request with appropriate parameters. case success, returns RF4CE_SAP_PENDING pairing operation result communicated through call NLME_PAIR_confirm.
17097
11/29
Using STRF4CE
UM0909
target node respond pair indication using NLME_PAIR_response API. case success, this returns value RF4CE_SAP_PENDING pair response status communicated through user-defined callback COMM_STATUS_indication. example code device pairing status; NLME_PAIR_REQUEST_Type param; IEEEAddr dstLongAddr {0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77}; param.LogicalChannel param.DstPANId 0x1234; memcpy(param.DstIEEEAddr, dstLongAddr, sizeof(IEEEAddr)); param.OrgAppCapabilities 0x13; param.OrgDevTypeList[0] 0x01; param.OrgProfileIdList[0] 0x01; param.KeyExTransferCount status NLME_PAIR_request(&param);
Message exchanges
Messages transmitted through NLDE_DATA_request sent both controller node target node. RF4CE standard states that following types communication possible:
Controller target Target controller Target target
Messages exchanged only between nodes that have previously been paired; that valid pairing entry exists pairing table. case success, returns RF4CE_SAP_PENDING message transmission result communicated through call NLDE_DATA_confirm. other value returned should considered error condition. Message reception indicated user application through user-defined callback NLDE_DATA_indication. example message exchange status; NLDE_DATA_REQUEST_Type param; param.nsduLength param.nsdu[0] 0x11; param.PairingRef param.ProfileId 0x01; //Consumer Electronics Remote control param.VendorId 0xfff1; //Test vendor param.TxOptions 0x4c; Unicast address security multiple channel channel designator vendor specific status NLDE_DATA_request(&param);
12/29
17097
UM0909
Using STRF4CE
Security
Security automatically activated stack when node capabilities paired nodes show that node supports security (see nodeCap parameters Section 2.2). Even security enabled over couple paired nodes, application still ability select between secure non-secure communications when using NLDE_DATA_request API. security enabled, only non-secure communications allowed.
Timer
simple timer used stack handle timeouts delays. timer resolution 1us. Application timer TIME_CurrentTime TIME_ELAPSED.
Power consumption
stack contains built-in mechanism support power saving schemes.
2.8.1
power down
power down part achieved through call NLME_RX_ENABLE_request with RxOnDuration parameters stack confirms power down part when NWK_Tick return value RF4CE_STATE_POWER_DOWN set. Some code show power down show below. NLME_RX_ENABLE_request(0); while ((NWK_Tick() RF4CE_STATE_POWER_DOWN) helper function NWK_PowerDown() provided implement above code recommended. stack brought back normal operation with call NLME_RX_ENABLE_request with RxOnDuration parameters 0xFFFFFF using helper function NWK_PowerUp(FALSE).
2.8.2
power down
real life application, order achieve maximum battery life could useful shutdown entire SOC. this case sequence operation should follow: NWK_PowerDown(); ATOMIC( halPowerDown(); POWERDOWN_SET_GPIO_CFG_REG(); halSleep(SLEEPMODE_POWERDOWN, 0x000004A0); //DeepSleep deep sleep execution will resume from here halPowerUp();
17097
13/29
Using STRF4CE NWK_PowerUp(TRUE); uartInit(115200, PARITY_NONE,
UM0909
2.8.3
standby
RF4CE standard define mechanism achieve power saving through NLME_RX_ENABLE_request with parameter RxOnDuration nwkActivePeriod. simple piece code activate standby shown below. activePeriod; NLME_Get (nwkActivePeriod_ID, &activePeriod);
volatile memory management
RF4CE stack contains module manage storage using Kbyte Flash memory. usage transparent user, some interaction with application required limit Flash wearing. Flash wearing limited using cache data RAM, periodically this cache needs flushed into actual flash, that lost case power failure. following code provides example flash cache: retVal NWK_Tick(); Check whether cache flush required (retVal RF4CE_STATE_NEED_CACHE_FLUSH) NWK_Flush(); Since NWK_Flush operation requires about 40ms complete, application choose when more appropriate call often. NWK_Tick return value gives indication when cache consistent, call NWK_Flush() mandatory delayed necessary.
2.10
RF4CE Stack configuration
RF4CE library allows configuring some stack parameters time, these stack parameters are, according specification, constants implementation dependent. These parameters listed following table:
14/29
17097
UM0909 Table Configurable stack parameters
Name nwkcMaxNodeDescLi stSize nwkcMaxPairingTab leEntries nwkcNodeCapabilit nwkcVendorIdentif Valid range specified specified Default value
Using STRF4CE
Description changeable without recompiling stack changeable without recompiling stack Don't change this, NWK_Init node capabilities Vendor please NWK_Config change Vendor string, please NWK_Config change
specified
value
0xFFF1
nwkcVendorString
characters string
"ST"
complete description parameters, please refer [2]. stack configuration required prior cold starting stack using NWK_Init they stored volatile memory. following code shows configure stack using NWK_Config. void NLME_START_confirm (u32 *status) printf("RF4CE network started\r\n"); networkStarted TRUE; status NWK_Init(0, FALSE); (status RF4CE_NVM_DATA_INVALID) warm start fails, cold start myVendorId 0xabcd; &myVendorId); NWK_Config(nwkcVendorString_ID, "Vendor"); status NWK_Init(1, TRUE); while (networkStarted FALSE) (void) NWK_Tick(); other network parameters changeable using NLME_Set API. Below example setup nwkUserString parameter. This should done only once after cold start. NLME_SET_Type val; val.NIBAttribute nwkUserString_ID; val.NIBAttributeIndex val.NIBAttributeValue "STM32W Target";
17097
15/29
Designing application using RF4CE library
UM0909
Designing application using RF4CE library
code below shows skeleton application implementing RF4CE target device. #include "rf4ce.h" void *param) Your code here void NLME_START_confirm(u32 *status) printf("RF4CE network started\r\n"); networkStarted TRUE; void *param) Your code here void NLME_DISCOVERY_confirm (NLME_DISCOVERY_CONFIRM_Type *param) Your code here void *params) Your code here void *param) Your code here void *param); Your code here void *param) Your code here void NLME_PAIR_indication (NLME_PAIR_INDICATION_Type *params) Your code here void NLME_COMM_STATUS_indication *params) Your code here void NLME_UNPAIR_indication *PairingRef)
16/29
17097
UM0909 Your code here main (void) Init halInit();
Designing application using RF4CE library
init serial uartInit(115200, PARITY_NONE, enable interrupts INTERRUPTS_ON(); status NWK_Init(1, FALSE); (status RF4CE_NVM_DATA_INVALID) warm start fails, cold start myVendorId 0xabcd; &myVendorId); NWK_Config(nwkcVendorString_ID, "Vendor"); status NWK_Init(1, TRUE); while (networkStarted FALSE) (void) NWK_Tick(); while blocking call advance application state machine ApplicationTick(); blocking call advance network layer state machine (void) NWK_Tick();
17097
17/29
RF4CE Demo application
UM0909
RF4CE Demo application
ZigBee RF4CE demo applications target ZigBee RF4CE CERC (Consumer Electronic Remote Control) Profile remote control target devices scenarios listed Table Table ZigBee RF4CE CERC demo applications scenarios
RF4CE remote control RS232 Virtual Primer RF4CE target device RS232 Target Virtual Sony infrared
combinations between Targets supported. These demo scenarios demonstrate simple RF4CE interactions between target device with:
Discovery pairing Secure communications Data transmission Power management
STM32W108 firmware (rf4ce.s37) same both target devices used different scenarios according Section 4.4: RS-232 Remote Control Target applications, Section 4.5: Virtual Section 4.6: Primer2 Sony Infrared (with RF4CE extender). This firmware MB851 board also considered reference application customers want implement CERC profile ZigBee RF4CE stack.
Firmware common features
same firmware (rf4ce.s37) designed STM32W108 MB850 MB851 boards provides user interface, through RS-232 interface, LEDs push-buttons. When loaded MB850 board, firmware controlled Primer2 STM32 microcontroller. When loaded MB851 board, firmware user interactions described Table Table MB851 firmware user interface
Direction Input/Output Output Description Command line interface (see section 5.2) Heartbeat LED, should flashing times, except when Standby.
User interface item RS-232 (Yellow)
18/29
17097
UM0909 Table MB851 firmware user interface (continued)
Direction
RF4CE Demo application
User interface item
Description RF4CE network initialized target. OFF: RF4CE network layer initialized initialized remote control.
(Green)
Output
Blinks every sec: RF4CE network layer cold start progress. Blinks every sec: RF4CE target node waiting pairing from remote control. OFF: Press start node target.
Push-button
Input
Press enable pairing. Press more than seconds bring RF4CE node unconfigured state.
Building firmware
firmware provided prebuilt prebuilt directory software release build from sources Embedded Workbench 5.41 more recent using rf4ce.eww project file.
Programming MB851 firmware
firmware programmed boards using Embedded Workbench prebuilt image using stm32w_flasher utility. information stm32w_flasher utility, refer STM32W-SK STM32W-EXT starter extension kits STM32W108xx user manual (reference: UM0894).
RS-232 Remote Control Target applications
this demo scenario, user interacts with MB851 boards using HyperTerminal user node RF4CE Target RF4CE controller (Figure This demo scenario uses MB851 boards with firmware rf4ce.s37 preloaded even single RS-232 port should according values shown Table Table RS-232 settings
Parameter Baud rate Data bits Parity Stop bits Flow control Setting 115200 None Xon/Xoff
17097
19/29
RF4CE Demo application Figure RS-232 target node
UM0909
demo supports commands (case-sensitive) shown Table over HyperTerminal. (The devices named MB851 MB851 reference STM32W108 boards both loaded with rf4ce.s37 image.) Table Firmware commands
Description Configure node Target Configure node Controller Discovery Pair procedure Discovery Pair procedure from Target Dump Pairing Table Device software reset Clear Pairing Table Erase storage Enable power save Disable power save Print Help menu Send Command (Pressed): Volume Send Command (Pressed): Volume Down Send Command (Pressed): Channel Send Command (Pressed): Channel Down Send Command (Pressed): Channel Enter string command mode
Command
demo applications, type following commands sequence: MB851 devices configured, prompt "Unconfig>". Otherwise type cancel previous configuration. MB851 Type command configure Target. Wait approximately seconds RF4CE network initialization. initialization correct, prompt will Target(-1)> indicates that device paired). MB851 Type command configure Controller (remote control). initialization correct, prompt Controller(-1)> indicates that device paired). MB851 Type command wait confirm messages both boards.
20/29
17097
UM0909
RF4CE Demo application Below example discovery pair messages with status CONTROLLER: Controller(-1)>D <CERC_DSC_PAIR> Status 00000100 <CERC_DSC_PAIR_END> Status 00000000 PairingRef VendorId FFF2 VendorString Vendor AppCapabilities UserString STM32W Target DevTypeList <CERC_PAIR_CONFIRM_END> Controller(0)> TARGET: Target(-1)>D <CERC_DSC_PAIR> Status 00000100 <CERC_DSC_PAIR_END> Status 00000000 PairingRef VendorId FFF1 VendorString AppCapabilities UserString STM32W DevTypeList PANId FFFF Address 0080E1020000026C <CERC_PAIR_INDICATION_END> Status 00000000 PairingRef PANId FFFF Address 0080E1020000026C Target(0)> Furthermore verify that pairing operation successful checking pairing table contents. MB851 Type command verify that devices paired. find below example device paired. particular status must 0x02 otherwise discovery pair procedure failed some reason.
Controller(0)>p <CERC_PAIRING_TABLE> status sNWK dstIEEEAddr A645 0080E10200000261 FFFF FFFFFFFFFFFFFFFF FFFF FFFFFFFFFFFFFFFF
dPAN 72FA FFFF FFFF
dNWK E596 FFFF FFFF
frmcnt 00000409 FFFFFFFF FFFFFFFF
linkKey
17097
21/29
RF4CE Demo application
FFFF FFFFFFFFFFFFFFFF FFFF FFFF FFFFFFFF FFFF FFFFFFFFFFFFFFFF FFFF FFFF FFFFFFFF
UM0909
press keys Controller check that they correctly received Target. MB851 (Remote Control): Type commands: Change channel Keys Volume Volume down Channel Channel down with payload 0x01 (KEY_PRESSED) containing number 0x## according following list: KEY_PRESSED plus 0x20 "Channel -0x29 "Channel 0x41 "VolUp" 0x42 "VolDown" 0x30 "ChannelUp" 0x31 "ChannelDown" with payload 0x03 (KEY_RELEASED) keep pressed, CERC profile sends packet with payload 0x02 indicate that being repeated. Note: each received, infrared Target emits Sony compatible sequence. This useful driving Sony with infrared remote control.
MB851 (Target): each pressed released, receives packets:
Virtual
This demo scenario uses MB851 boards applets emulate RF4CE remote control RF4CE (see Figure Virtual applet implementing remote control driven through GUI. Virtual applet implementing driven through GUI. start demo, please make sure have MB851 boards connected through port perform following steps: Virtual Virtual applications from Programs STMicroelectronics ZigBee RF4CE 1.0.0 STM32W108 Demos. Virtual application, select serial port from drop-down menu. firmware present board, will automatically downloaded application.) Wait initialization procedure complete ("ST RF4CE Ready" message displayed). Virtual application, select serial port from drop-down menu. firmware present board, will automatically downloaded application.) Wait initialization procedure complete ("ST RF4CE Ready" message displayed). Virtual application, select start pairing procedure.
22/29
17097
UM0909 Note: Virtual application, select
RF4CE Demo application start pairing procedure.
everything message "Paired" displayed confirmation message with technical details displayed after seconds. demo operational presses virtual will perform requested action virtual specified Table
again demo with same boards devices already paired Steps necessary. Figure RF4CE Virtual
4.5.1
Virtual
Virtual application that emulates RF4CE supports commands listed Table Table Button functions Virtual
CERC code 0x43 0x41 Infrared code 0x14 0x12 Mute button Volume button Description
label
0x42
0x13
Volume down button
0x40
0x15
Standby button
0x30
0x10
Channel button
0x31
0x11
Channel down button
0x44
0x1A
Play button
0x46
0x19
Pause button
0x69
0x25 0x09, 0x010x08
button
0x20-0x29
Digit button
17097
23/29
RF4CE Demo application Table Button functions Virtual (continued)
CERC code 0x35 Infrared code 0x3A Info button Description
UM0909
label
0x09
0x60
Menu button
0x01
0x74
button
0x02
0x75
Down button
0x04
0x33
Right button
0x03
0x34
Left button
0x00
0x65
Select/OK button
Cancel paired devices
Show list paired devices
Search pair RF4CE Target
24/29
17097
UM0909 Figure shows snapshot Virtual application. Figure Virtual
RF4CE Demo application
17097
25/29
RF4CE Demo application
UM0909
4.5.2
Virtual
Virtual application that emulates RF4CE supports following features:
channels, playing video from files Volume control Mute Channel change Play/Pause Pair button Erase pairing table button Paired devices information Virtual screenshot
Figure
26/29
17097
UM0909
RF4CE Demo application
Primer2 Sony Infrared (with RF4CE extender)
This demo scenario targets standalone demo with battery operated infrared support Sony's codes (see Figure Primer2 touch sensing remote control connected STM32W108 MB850 board. order start RF4CE Remote control application Primer2, select "RF4CE entry from Primer2 application menu. Primer2 supports commands listed Table with following differences: Table Additional Primer2 commands
present. Joystick up/down Joystick left/right Joystick held left more than seconds Joystick held right more than seconds Scrolls between button's pages. Shows pairing list. Erases pairing table. Forces firmware upload STM32W108.
RF4CE extender STM32W108 MB851 board which acts RF4CE-Infrared bridge between Primer2 RF4CE Sony Please note that:
rf4ce.s37 firmware requested loaded STM32W108 MB851 board Jumper should fitted
Sony infrared normal supporting Sony's codes listed Table with MB851 board placed close infrared receiver. Figure Primer2 Sony infrared
Primer RF4CE remote control
RF4CE extender
Sony
Primer2 RF4CE supports following commands:
Certain standard buttons Volume control Mute Channel change Pair button Paired device information
17097
27/29
Reference documents RF4CE extender supports following features:
UM0909
Network layer cold start pressing button when off. Pairing mode when pressing button Erase pairing table bring unconfigured state when pressing button more than seconds.
Note:
This demo also using Virtual applet Sony compatible available) shown Figure Figure Primer2 Virtual
Primer RF4CE remote control
Reference documents
ZigBee RF4CE Specification, ZigBee Alliance document 094945r00ZB, Version 1.00, March 17th, 2009. ZigBee RF4CE: CERC Profile Specification, ZigBee Alliance document 094946r00ZB, March 17th, 2009. High-Definition Multimedia Interface Specification, HDMI Licensing, LLC, Version 1.3a, November 2006. STMicroelectronics, STM32W108HB datasheet, 16252 December 2009 RF4CE Reference Guide, HTML document
Revision history
Table
Date 19-Feb-2010
Document revision history
Revision Initial release. Changes
28/29
17097
UM0909
Please Read Carefully:
Information this document provided solely connection with products. STMicroelectronics subsidiaries ("ST") reserve right make changes, corrections, modifications improvements, this document, products services described herein time, without notice. products sold pursuant ST's terms conditions sale. Purchasers solely responsible choice, selection products services described herein, assumes liability whatsoever relating choice, selection products services described herein. license, express implied, estoppel otherwise, intellectual property rights granted under this document. part this document refers third party products services shall deemed license grant such third party products services, intellectual property contained therein considered warranty covering manner whatsoever such third party products services intellectual property contained therein.
UNLESS OTHERWISE FORTH ST'S TERMS CONDITIONS SALE DISCLAIMS EXPRESS IMPLIED WARRANTY WITH RESPECT AND/OR SALE PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES MERCHANTABILITY, FITNESS PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER LAWS JURISDICTION), INFRINGEMENT PATENT, COPYRIGHT OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS EXPRESSLY APPROVED WRITING AUTHORIZED REPRESENTATIVE, PRODUCTS RECOMMENDED, AUTHORIZED WARRANTED MILITARY, CRAFT, SPACE, LIFE SAVING, LIFE SUSTAINING APPLICATIONS, PRODUCTS SYSTEMS WHERE FAILURE MALFUNCTION RESULT PERSONAL INJURY, DEATH, SEVERE PROPERTY ENVIRONMENTAL DAMAGE. PRODUCTS WHICH SPECIFIED "AUTOMOTIVE GRADE" ONLY USED AUTOMOTIVE APPLICATIONS USER'S RISK.
Resale products with provisions different from statements and/or technical features forth this document shall immediately void warranty granted product service described herein shall create extend manner whatsoever, liability
logo trademarks registered trademarks various countries. Information this document supersedes replaces information previously supplied. logo registered trademark STMicroelectronics. other names property their respective owners.
2010 STMicroelectronics rights reserved STMicroelectronics group companies Australia Belgium Brazil Canada China Czech Republic Finland France Germany Hong Kong India Israel Italy Japan Malaysia Malta Morocco Philippines Singapore Spain Sweden Switzerland United Kingdom United States America www.st.com
17097
29/29

ZIG09115ZCP2855824

Top Searches for this datasheet

Other recent searches