STM32W108xx STM32W-SK STM32W-EXT

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

STM32W108xx STM32W-SK STM32W-EXT

Datasheet Thumbnail

Top Searches for this datasheet

Zigbee-pro Library - Zigbee-pro Library
STM32W108 zigbee - STM32W108 zigbee
STM32W108 datasheet - STM32W108 datasheet
STM32W108* - STM32W108*
STM32w eeprom - STM32w eeprom
ga 32 arm - ga 32 arm
STM32W108xx - STM32W108xx
STM32W-SK - STM32W-SK
STM32W-EXT - STM32W-EXT

RN0034 Release notes
STM32W108xx starter extension kits EmberZNet4.0.2
About these release notes
This release notes STM32W108xx starter extension kits (order code: STM32W-SK STM32W-EXT, respectively) related EmberZNet4.0.2 ZigBee® stack. This release these kits contains following:
Hardware Abstraction Layer (HAL) software provided source code STM32W108 ZigBee Networking stack Sample applications provided source code EmberZNet Command Line Utilities required STM32W108 Hardware Reference Designs Datasheet STM32W108 Application Serial-only Bootloaders
These release notes updated periodically order keep abreast software updates problems limitations found this release. Check Internet website www.st.com/mcu latest version these release notes (STM32W section).
What's
EmberZNet4.0.2 stack designed STM32W108 engineering samples STM32W108xBU61 microcontroller. This release addresses following issues: [Security] security frame counters were being initialized when stack reset. This could have caused dropped messages frame counter confusion when using security. [MAC] rare occurrences, Frame Pending when should have been. [MAC] Smart Energy InterPAN Bootloader messages (MAC passthrough messages) triggered packet-buffer assert emberGetLinkedBuffersPointer. [AppFramework] zcl-utils (app/ha/zcl-util.c) should immediately drop messages that properly encrypted. [Routing] Stack handles oversized source routes more gracefully. ZigBee limitations, largest source route that safely utilized network hops relays destination). Prior this fix, EmberZNet's source routing utilities library (app/util/source-route.c) didn't prevent oversized source routes (more than relays) from being used. This lead creation outgoing frames that were large stack handle, which turn lead assert mac.c:441) zigbee-pro-stack library. [ZDO] Stack used deprecated status 0x87 EMBER_ZDP_TABLE_FULL employing correct value 0x8C. (The TABLE_FULL error specified with 0x87 0x8C.) [ZDO] BINDING TABLE RESPONSE TotalEntries field incorrectly number entries present response instead total number active (used) entries responder's binding table.
February 2010 16225 1/13
www.st.com
Contents
RN0034
Contents
Read first
Host system requirements Installation Support Software versions Supported hardware platforms Formal ZigBee certified platform status Accessing documentation File layout
Installation
Installing EmberZNet stack Installing Embedded Workbench ARM, version 5.41 Command line utilities Installing FTDI driver
Known issues/limitations
Networking stack software Embedded Workbench STM32W108 Intended behavior
Additional information
General information Important project file options Note security routing Note forming, joining leaving
Revision history
2/13
16225
RN0034
Read first
Read first
This chapter provides important information about this release.
Note:
Host system requirements
compatibles running Windows operating systems. install (Integrated Development Environment) used building EmberZNet ZigBee stack, users must have administrator privileges.
Installation
Refer STM32W-SK STM32W-EXT starter extension kits STM32W108xx user manual (reference: UM0894) included your EmberZNet installation folder detailed step-by-step instructions about setting your first time. Section Installation detailed instructions installing this release.
Support
STM32W108 customers eligible technical support. STMicroelectronics site www.st.com/mcu (STM32W section) obtain information about STM32W108 products services, well sign product support.
Software versions
Stack software version build version number defined SOFTWARE_VERSION source code stack/config/config.h file.
This stack software release intended used with following versions other components:
Programming utilities em3xx_load (Version 1.0b27.1264522950), em3xx_convert (Version 1.0b25.1261162476) stm32w_flasher (Version 1.0.1b1-20100203) Embedded Workbench 5.41 library (from Certicom) released
Supported hardware platforms
This release supported STM32W108 platforms only.
Formal ZigBee certified platform status
According ZigBee policy, STMicroelectronics must certify this release order remain compliant. STMicroelectronics scheduled certify this release coming weeks. STMicroelectronics high confidence that this certification process should proceed without further changes stack, there always risk change.
16225
3/13
Read first
RN0034
Accessing documentation
view full documentation, open: Start Programs STMicroelectronics EmberZNet Stack 4.0.2 STM32W108 Documentation open documentation/index.htm file from root directory installed EmberZNet stack. documentation includes HTML pages describing EmberZNet Stack API, along with user manuals, application developer's guide, STM32W108 datasheet, various application notes. view documentation Embedded Workbench, open: Start Programs Systems Embedded Workbench Release Notes view information sample applications, open: Start Programs STMicroelectronics EmberZNet Stack 4.0.2 STM32W108 Samples open app/sampleApps.html file from root directory installed EmberZNet stack. This includes explanations sample applications work, what commands supported, notes, limitations. also includes shortcut links open project files. Embedded Workbench 5.41 must installed before these project links will work properly.
File layout
Installing EmberZNet stack software creates following directories: app: Contains sample application utilities source code. Note that sample application project files included directory under project directory (for instance, app/sensor/ewb). Project workspaces have extension. app/nodetest: Contains pre-built image nodetest image. app/prebuilt: Contains pre-built images many sample applications including: ZigBee Smart Energy (SE), ZigBee Home Automation (HA) Sensor example applications (sink, sensor, sleepy-sensor, mobile-sensor). hal: Contains STM32W108 source code. stack: Contains header files necessary build EmberZNet applications. build: Contains pre-built stack libraries. Note that when sample applications built, their corresponding files stored subdirectory this directory. documentation: Contains documentation files. Open documentation/index.htm list documentation files. tool/certificates: Contains sample security certificates install codes. tool/bootloader: Contains bootloader project files building bootloaders with custom modifications. tool/em3xx: Contains em3xx utilities.
4/13
16225
RN0034
Installation
Installation
Refer STM32W-SK STM32W-EXT starter extension kits STM32W108xx user manual (reference: UM0894) detailed step-by-step instructions about setting your first time. release made several components that work together provide complete functionality. With exception Embedded Workbench, most recent versions these installers downloaded from website (www.st.com/mcu, STM32W section).
Installing EmberZNet stack
stack installer should installed first, performs following actions:
Installs files needed develop applications EmberZNet Stack into directory specified user. (The default location C:\Program version}\ STM32W108). Adds shortcut Start Menu into folder specified user (default directory .\STMicrolectronics\{release version}\STM32W108). Adds entry "Add/remove programs" panel (accessed from Windows Control Panel) stack uninstalled. Does affect environment variables.
Installing Embedded Workbench ARM, version 5.41
CD-ROM with Embedded Workbench included your STM32W108 kit. This 30-day evaluation version. Insert CD-ROM into Drive your follow instructions displayed screen installer. Installer does automatically start, browse your Drive, click autorun.exe. Refer "Quick start installation information" section installer additional information about installation process configure your license.
Command line utilities
following command line utilities provided tools\em3xx folder installation path:
em3xx_load.exe (Refer Section 4.1: General information details) em3xx_convert.exe used convert files into format stm32w_flasher
following utility provided tools folder installation path:
Note:
Refer STM32W-SK STM32W-EXT starter extension kits STM32W108xx user manual (reference: UM0894) information about using this utility.
16225
5/13
Installation
RN0034
Installing FTDI driver
order interface STM32W108 boards, driver FTDI USBSerial converter must installed. This driver acquired from FTDI
6/13
16225
RN0034
Known issues/limitations
Known issues/limitations
Networking stack software
em3xx_load properly leave chip state where Deep Sleep fully achieved. testing Deep Sleep function, power-cycle chip after loading image. command outputs nodetest application fully updated easily parseable response formatting. These commands have their output changed future releases. recently published Cortex Microcontroller Software Interface Standard (CMSIS). CMSIS could used future releases. Therefore, possible register definitions, exception interrupt definitions, other APIs source code change future releases comply with CMSIS Standard. ARM's TPIU TracePort functionality gracefully shutdown when entering Deep Sleep. This could cause some irrelevant data seen Debug channel output sleepy devices. driver should considered preliminary, does provide functionality aspects STM32W108 ADC's hardware features. This driver also implemented assuming that EmberZNet Stack will share with application. This longer true, application full control generalpurpose STM32W108. Future releases include changes driver expose additional features, remove sharing. halAdcSetRange() function within should used. Only default voltage range should used. STM32W108 Errata sheet details. [Security] Persistent security state after Join failure cause spurious failures subsequent Join attempts. [Stack] devices transmit Leave Announcements.
Embedded Workbench
linker displays usage statistics about amount different types memory that used. usage statistics (readwrite data memory) incorrectly count Simulated EEPROM RAM. Please instead refer output generated em3xx_convert which provides more complete breakdown usage. While linker prints stdout basic information regarding code data usage, this information confusing misleading. em3xx_convert, which triggered project files post build step, prints stdout more detailed information usage, Flash memory usage, usage summary. Errors memory usage information generated em3xx_convert visible build output window Workbench. view these errors, select Options from Tools menu, then select Messages category. Under Show build messages option, select All. When starting debug session, incorrectly display warning about stack "CSTACK" being filled 100% while threshold 90%. EWARM release notes additional information.
16225
7/13
Known issues/limitations
RN0034
STM32W108
STM32W108 Errata documentation included with stack documentation more information.
Intended behavior
This section describes certain intended behaviors that have caused confusion: Broadcasts with empty payload heard through loopback sending node. Problem: When sending broadcast with payload, sending node does emberIncomingMessageHandler() call broadcast loopback. Other devices network will receive broadcast expected. Workaround: 1-byte payload broadcast that sender expects hear through broadcast loopback. Problem: ZigBee requires devices send Leave message when they leaving network. ensure that this message sent, devices wait seconds. Workaround: None.
takes least seconds node leave network.
When node "hears" messages, lastHopLqi lastHopRssi parameters should have invalid values. Problem: last read values RSSI used when device hears message from itself. Workaround: device should RSSI values when source address itself.
Parent could allow device rejoining with in-use cause node network change Problem: child attempts rejoin using shortID that already assigned another device, parent does allow rejoin sends conflict message causing joined device using same change it's Workaround: None, intended behavior.
route discovery initiated source routed unicast sent with option. Problem: source route option takes precedence over route discovery option. This could setup return error, designed behavior allow source route option (the route being used many-to-one route) take precedence over route discovery option. Workaround: None, intended behavior.
8/13
16225
RN0034
Additional information
Additional information
General information
STM32W10 chips little endian. majority included sample applications configured bootloader (NULL_BTL). bootloader sample applications themselves only ones preconfigured their respective bootloader. em3xx_load will generate warning detects bootloader/application mismatch when loading image. default, STM32W108 uses Simulated EEPROM that consumes Kbytes Flash memory. Building application using define EMBER_SIM_EEPROM_4KB causes Simulated EEPROM consume only Kbytes Flash memory. 4Kbyte SimEE discouraged since this affects write cycle counts tokens could reduce life device. Refer application note Using Simulated EEPROM detailed discussion Simulated EEPROM write cycles. applications, regardless chip SimEE size, limited total Kbytes token data.
Note:
possible switch between Kbytes Kbytes sizes dynamically. Installing application onto device that different size Simulated EEPROM than previously installed application will cause tokens reset their default values.
Manufacturing tokens stored Customer Information Block best modified using manipulation commands em3xx_load.exe. These commands, -cibtokenspatch, -cibtokensprint, -cibtokensdump abstract token locations patching simplify interface. token manipulation commands designed operate byte arrays, endian integers, strings. Therefore, data being passed into token manipulation shown more natural, human readable format. STM32W108 platform supports improved reset information available application that provides greater detail when necessary, while still keeping simplistic interface when only general information required. addition existing APIs halGetResetInfo() halGetResetString(), there APIs halGetExtendedResetInfo() halGetExtendedResetString(). STM32W108 platform also supports enhanced crash diagnostics. Portions that maintained EmberZNet intended modified included part Library. Library includes functions such Simulated EEPROM, Flash memory manipulation, system timer management, chip calibrations. STM32W108 platform, possible customize behavior bootloaders change things such menus displayed, which peripherals used, baud rates, replace external EEPROM drivers, many other behaviors. These portions bootloaders provided source code, linked against bootloader library which handles xmodem transactions, processing files, writing images Main Flash Block. STM32W108 platform, external Flash/EEPROM drivers used application bootloader only need included application bootloader itself. application does need built specific Flash/EEPROM component, application will call directly driver that built application bootloader. These means there longer separate app-bootloader-demo sample applications Flash/EEPROMs, there separate application bootloaders.
16225
9/13
Additional information
RN0034
Important project file options
following list describes important project file options needed build EmberZNet applications STM32W108 with IAR's Embedded Workbench. These premade generated workspaces provide good example settings, extended your applications. list given here does provide every project setting option includes major settings.
Core: STM32W108 FPU: None Endian Mode: Little Library: Normal Language conformance: Allow extensions Plain 'char' Unsigned Optimizations: Level: High (Size) Optimizations: Enabled transformations: Compiler Preprocessor/Assembler Preprocessor: Additional include directories: $FILE_DIR$\ $PROJ_DIR$\.\.\.\ $PROJ_DIR$\.\.\.\STACK\ $PROJ_DIR$\.\.\.\HAL\ MB850 board: MB851 board: CORTEXM3 CORTEXM3_STM32W108 PHY_EM3XX MB850 board: BOARD_MB850 MB851 board: BOARD_MB851 following, depending bootloader choice: SERIAL_UART_BTL APP_BTL NULL_BTL
Compiler Preprocessor/Assembler Preprocessor: Defined symbols:
Output Converter: Generate Additional output: Output format: Motorola Build Actions: Post-build command line: "$TARGET_BPATH$.s37" "$TARGET_BPATH$.ebl"
Linker: Config: Override default:
10/13
16225
RN0034
Additional information Linker: Config: Configuration file symbol definitions: following, must match bootloader choice also used above: SERIAL_UART_BTL=1 APP_BTL=1 NULL_BTL=1
Linker: Library: Automatic runtime library selection Linker: Library: Override default program entry: Entry Symbol: halEntryPoint Debugger: Setup: J-Link/J-Trace Debugger: Setup: Device description file: Override default: Debugger: Download: Verify download Debugger: Download: Flash Loader(s) Debugger: Extra Options: command line options (ensure this appears single line): -jlink_exec_command "SetSysPowerDownOnIdle SetDbgPowerDownOnClose
J-Link/J-Trace: Setup: JTAG/SWD speed: Auto: Initial J-Link/J-Trace: Connection: TCP/IP desired J-Link/J-Trace: Connection: Interface:
Note security routing
Security requires using many-to-one routing trust center ensure that exchanges occur correctly. Many-to-one routing ensures that parent joining device route trust center that parents send route records behalf their joining children which means trust center will have source route back joining device. network does many-to-one routing devices that more than hops from trust center, joining will unreliable. LOW_RAM_CONCENTRATOR mode, route records sent before each message that sent trust center. This expected.
Note forming, joining leaving
Once ZigBee device joined network, there state kept other devices network about device resets, still considered part network should call emberNetworkInit return network previously part device should reset call emberJoinNetwork emberFormNetwork return network previously part device wants move another network should either call emberLeaveNetwork, wait indication from emberStackStatusHandler that network down, then call emberJoinNetwork emberFormNetwork join start another network. During development useful clear this state (when reloading test version application, instance) without going through leave/form process. Since this state stored tokens Simulated EEPROM, simplest mechanism clearing state erase chip's main Flash memory which will erase tokens. While programming application into Flash memory using em3xx_load, option -erase added program operation erase Flash memory while programming application. desire erase Flash memory separate
16225
11/13
Revision history
RN0034
step, -erase used itself command -masserase, which faster operation, used. Note that -erase -masserase will erase main Flash memory, including bootloader requiring bootloader reinstalled with application.
Revision history
Table
Date 16-Nov-2009 16-Feb-2010
Document revision history
Revision Initial release. Added support EmberZNet4.0.2 stack. What's page list modifications. Changes
12/13
16225
RN0034
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
16225
13/13

STM32W108xx STM32W-SK STM32W-EXT

Top Searches for this datasheet

Other recent searches