UM0389 User manual
ZigBee REva kit library package
Introduction
This document describes the ZigBee REva Kit library package, which consists of two software libraries:
EZSP library for driving the SN260 (by STMicroelectronics) or EM260 (by Ember) ZigBee devices. HAL library for addressing some of the REva platform devices and capabilities (buttons, buzzer, LEDs, memory, microcontroller, SPI protocol, system timer, UART). The HAL APIs can be matched with specific application purposes.
The EZSP APIs enable an ST microcontroller (hosted on the REva platform through a daughter board) to communicate with the SN260 ZigBee network processor. This library is built on top of the HAL library, since each EZSP frame is sent serially to the SN260 silicon through the SPI interface (driven with the specific HAL APIs). The Raisonance REva board, with a daughter board supporting the selected ST microcontroller, and a radio communication module with the SN260 silicon are used as reference platforms. This user guide is intended to provide an overall description of the software and hardware requirements for the ZigBee REva Kit library package, instructions for setting up the hardware and building the software library package as well as describing known limitations and issues at release time. Due to the total compatibility between the SN260 and EM260, and the partnership between the two companies, some documents have been graciously supplied by Ember.
List of key words
HAL: Hardware Abstraction Layer. EZSP: Ember ZigBee Serial Protocol. EmberZNet: ZigBee stack running over the SN260 silicon. RIDE: Raisonance Integrated Development Environment. RCM: Radio Communication Module.
December 2007
Rev 8
1/30
www.st.com
Contents
UM0389
Contents
1 2 Release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Quick start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 2.2 Required hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.1 External equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.1 2.2.2 2.2.3 2.2.4 Host development platform (Ride7 toolset) . . . . . . . . . . . . . . . . . . . . . . . 8 Host development platform (RIDE toolset) . . . . . . . . . . . . . . . . . . . . . . . 9 Cosmic C toolchain for ST7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Host development platform (IAR toolset) . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3
Hardware setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 Module/cable connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 REva board jumper settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 REva Power area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Daughter board jumper settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Raisonance RLink jumper settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4
Building the library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3
Application examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1 3.2 Setup the application serial communication channel . . . . . . . . . . . . . . . . 17 Version application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.1 3.2.2 3.2.3 To run the version application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Load and run a version pre-built image . . . . . . . . . . . . . . . . . . . . . . . . . 20 Building/running steps for STM32F103x and STR71x-STR91x microcontrollers using IAR toolset 20
3.3
Sensor and sink applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3.1 3.3.2 3.3.3 To run the sensor application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Load and run two sink and sensor pre-built images . . . . . . . . . . . . . . . 22 Building/running steps for STM32F103x and STR71x-STR91x microcontrollers using IAR toolset 23
3.4
Light and switch applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.4.1 3.4.2 To run the light application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Load and run two light and switch pre-built images . . . . . . . . . . . . . . . . 26
2/30
UM0389 3.4.3 Building/running steps for STM32F103x and STR71x-STR91x microcontrollers using IAR toolset 27
Contents
4 5 6
SPI bootloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Limitations and support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3/30
Release notes
UM0389
1
Release notes
The current release supports the STM32F103x, STR71xF, STR75xF, ST7LITE39 and STR91xF microcontrollers.
4/30
UM0389
Quick start
2
Quick start
Figure 1 describes the ZigBee REva Kit library package layout. Figure 1. ezsp ZigBee REva Kit library package layout
include src libs ezsp header files ezsp sources files (EZSP APIs) ezsp_hal.r prj Ride7 project for building the ezsp_hal.lib library image (used for STM32F103x and STR7x-9x microcontrollers) ezsp_hal_ST7.prj RIDE project for building the ezsp_hal_ST7.lib library image (used for ST7LITE39 microcontrollers) board/ST microcontroller dependencies header files HAL header files HAL sources files (HAL APIs) Header files (specific types, required by the EZSP APIs and potentially available for developing applications) (access point to all available documents) (User Guide, EZSP, HAL APIs ...)
hal
config include src
include
header files
docs
index.html other docs
bin
ezsp_hal.lib ezsp_hal_ST7.lib version.hex version_st7.hex sensor.hex, sink.hex light.hex, switch.hex light_st7.hex, switch_st7.hex em260-spi.hex em2xx_load em260-rangetest.hex spi_bootloader a pre-built library image (for STM32F103x) a pre-built library image (for ST7LITE39) pre-built image of a simple ZigBee application (for STM32F103x) pre-built image of a simple ZigBee application (for ST7LITE39) pre-built images of the sensor and sink applications (for STM32F103x) pre-built images of the light and switch applications (for STM32F103x) pre-built images of the light and switch applications (for ST7LITE39) EmberZNet stack image files It contains the application loader files (which enable loading the EmberZNstack image em260-spi.hex into the SN260 silicon) SN260 range test (RF quality statistics) image files It contains the STM32F103x utility for uploading the stack image via the SPI vir tual COM through USB serial communication support suppor t for STM32F103x and STR71x-91x USB devices
serialUSB
vir t ualcom usblib
Note:
The EmberZNet 2.5.x stack version is delivered in XPV and XDV format (same for the related range test application).
5/30
Quick start
UM0389 If using the Ember ZNet 3.x stack, a new util directory is provided. It includes functions for handling the ZigBee source routing and security. Figure 2 describes the util directory layout. Figure 2. util
include header file for source routing functions source routing functions
util directory layout
table
src
include
header files for ZigBee security functions
security
src ZigBee security functions
In addition, a directory app is provided for hosting applications built over the library. Some applications are provided for showing the library package functions: a simple application which enables basic ZigBee operations to be performed, two simple applications (light and switch) for controlling a light and two more complex applications (sink, sensor) which enable the configuration of a distributed sensors network. Figure 3 describes the app directory layout. Figure 3. app
app
app directory layout
Ride7 projects for the sink, sensor applications: sink.rprj, sensor.rprj (for STM32F103x and STR7x-9x) application header file application sources files
sink_sensor
include src
app
version
src
Raisonance toolset (RIDE & Ride7) projects for the version application (version.rprj for STM32F103x and STR7x-9x and version _ST7.prj for ST7LITE39) application source files Raisonance toolset (RIDE & Ride7) projects for the light, switch applications (light.rprj, switch.rprj for STM32F103x and STR7x-9x, light_ST7.prj, switch_ST7.prj for ST7LITE39)
app
light
include src application header file application source files
Fur thermore, for each application, the corresponding IAR workspace is provided to enable the user to directly build the application using the IAR toolset.
6/30
UM0389 Note: 1 2 3 The ezsp_hal library does not provide an IAR workspace.
Quick start
This version of the ZigBee REva Kit package provides the IAR workspaces only for STM32F103x, STR71x and STR91x microcontrollers. The STM32F103x microcontrollers are only supported by the new Raisonance Ride7 environment, which still provides support for STR7x-91x microcontrollers. The RkitST7 for the Ride7 has some limitations/issues (it does not support the Cosmic toolchain and its library manager does not build a library). A RIDE project is still provided for the ezsp_hal library version for the ST7LITE39 microcontroller (and related applications). Consequently, two different Ride7 and RIDE projects are provided to target the library/applications based on the microcontroller family being used. The _ST7 suffix identifies the microcontroller family and the rprj (Ride7) or prj (RIDE) suffixes identify the Raisonance environments to be used. (For example, use the version.rprj Ride7 project for STM32F103x, STR7x-91x microcontrollers and the version_ST7.prj RIDE project for ST7LITE39 microcontrollers.) The sensor and sink applications are not supported by the ST7LITE39 microcontroller due to its smaller Flash memory (only 8 Kbytes) and RAM (only 384 bytes). The available pre-built images of version.hex, light.hex, switch.hex, sensor.hex, sink.hex, ezsp_hal.lib are provided only for STM32F103x microcontrollers (not the STR7x or STR91x). The available built images version_st7.hex, light_st7.hex, switch_st7.hex, ezsp_hal_ST7.lib are created for ST7LITE39 microcontrollers.
2.1
Required hardware
The target hardware is described below.
REva ZigBee Starter Kit for ST Microcontrollers which includes: Raisonance REva board v2.12 RLink v.2.10 REva daughter board (with the ST microcontroller) EM260 RCM module with the EM260 or SN260 silicon REva USB cable for programming the ST microcontroller with the RIDE toolset (and also to power the overall board) Cabling: Serial cable (for connecting the REva board serial SER1 to a PC RS232 port) USB mini cable (for connecting the STR71x-9x USB mini-B connector to a PC USB port)
Note:
At the time of manufacture, the REva board is provided in the "Attached mode": REva and RLink boards are connected, no connection cable is required and power is supplied by the USB connection. This is the standard configuration used for the library, applications building and running. Refer to the REva documentation for information corresponding to the REva + RLink + ST daughter boards. The new REva ZigBee Starter Kit for ST microcontrollers includes the STM32F103RBT6 and the ST7LITE39 microcontrollers and not the STR711FR2, STR750FV2 or STR912FW44. The EM260 device (Ember vendor) and the SN260 (STMicroelectronics vendor) are totally compatible.
7/30
Quick start
UM0389
2.1.1
External equipment
To show the library functions, the minimum external equipment required is a PC (Windows XP or 2000) with the Raisonance RIDE or Ride7 toolset (see software section for more information). When using the IAR toolset, the following equipment is required for programming (and/or debugging):
IAR J-Link JTAG emulator hardware for programming/debugging External power supply (9 V) for powering the REva board
2.2
Required software
The library is distributed through a specific link on the STMicroelectronics web site.
2.2.1
Host development platform (Ride7 toolset)
The Raisonance Ride7 toolset (Ride7 IDE version 7.01.0002 and RKit ARM for Ride7 version 1.03.0003) is used for building libraries and applications running with STM32F103x and STR7x-91x ARM microcontroller families. Ride7 is the new integrated development environment designed for the development of STMicrocontroller projects. This tool automatically manages file dependencies so that no makefile is necessary. The toolset is available from http://www.stm32circle.com/resources/tools.php. Select "Download the latest CD-ROM image".
Note:
The Ride7 toolset has the following known limitations:
The Ride7 RKit for ST7 microcontrollers does not support the Cosmic toolchain. Raisonance does not plan to add the Cosmic toolchain support to the Ride7 environment. The solution is to use the RIDE toolset (version 06.10.22) or the Raisonance toolchain provided inside the Ride7, RKitST7 for the ST7LITE39 microcontrollers. The current library manager of the Ride7 RKitST7 Raisonance toolchain cannot be used to build a library. Raisonance support is currently working on this issue. For ST7LITE39 microcontrollers, the RIDE (version 06.10.22) toolset with the Cosmic toolchain is used.
8/30
UM0389
Quick start
2.2.2
Host development platform (RIDE toolset)
The Raisonance RIDE toolset (version 06.10.22) is used for building libraries and applications running with ST7LITE39 microcontrollers. RIDE is an integrated development environment designed for the development of STMicrocontroller projects. This tool automatically manages file dependencies so that no makefile is necessary. The toolset is available from the Raisonance web site. Download (for free, after a simple account request) the RKit-ST7+STRx+PSD package (following the reported instructions if some other patches are required) and install it. This installation comes with documentation about the RIDE tool and Raisonance development boards (including ST microcontroller daughter boards).
Note:
1
The current RIDE toolset has the following known limitation: The RIDE default library manager incorrectly builds the *.lib file format (when used for the ST7LITE39 microcontroller). It does not use the clib utility even if the RIDE has been configured for using the Cosmic toolchain (see Section 2.2.3 below). Raisonance support recommends the following solution: Use a script (make_library.wsc) for running the clib utility and building the library image. The ezsp_hal_st7.prj project is already configured for using this make_library.wsc script, so the user is required to double-click on this script after the "Project Build all" command has been performed.
2
RIDE projects are no longer provided for building libraries and applications running with STM32F103x and STR7x-91x ARM microcontroller families.
2.2.3
Cosmic C toolchain for ST7
RIDE-ST7 can be used together with a number of third party tools such as the Cosmic C toolchain. The Cosmic C toolchain for ST7 is composed of a C compiler, an assembler and linker and can be used without leaving RIDE's graphical user interface (GUI).
Configuring RIDE and the COSMIC C toolchain to work together
In order to use RIDE together with the Cosmic C toolchain, the Cosmic software package must be installed. The Cosmic tools are not included in the distribution of RIDE-ST7. The free ST7 compiler 16K evaluation version is available for download at the Cosmic software web site after completing a request form. To use the Cosmic C toolchain it is also required to register with Cosmic Software: the installation procedure will send a message to Cosmic Software. Once the two packages have been properly installed and registered, it is necessary to inform RIDE where the Cosmic tools are located. By default, RIDE looks for the Cosmic tools under c:\cosmic\cxst7, which is the default directory proposed by the Cosmic installation program. If this directory is changed during the Cosmic tools installation, this must be indicated to RIDE. To do this: 1. 2. From the Options, Target, ST7 family menu, open Properties, Tools and select Cosmic Tools. From the Options, Target, ST7 family menu, open Properties, Settings and select the Cosmic installation path.
9/30
Quick start
UM0389
2.2.4
Host development platform (IAR toolset)
The IAR Embedded Workbench IDE for ARM toolset (version 4.42A supports the ARM CortexTM) is also used for building and running applications. The IAR Embedded Workbench IDE for ARM is a very powerful integrated Development Environment designed for developing and managing complete embedded applications projects.
Note:
1
For programming (and/or debugging) using the IAR toolset, an IAR J-Link JTAG emulator is required. The IAR J-Link is a JTAG emulator designed for ARM cores. It connects via USB to a PC running Windows 2000 or XP. It has a built-in 20-pin JTAG connector, which is compatible with the standard 20-pin connector defined by ARM. Using the IAR J-Link, an external power supply is required for powering the REva board. The 9V power supply should output 9V DC and have a 2.1 x 5 mm jack with the ground signal on the outside. The first time the IAR J-link is plugged in the PC USB port, the user is requested to provide the corresponding J-Link driver, browsing to the IAR installation directory and selecting the folder ARM, drivers, Jlink. When disconnecting the IAR J-Link from the PC USB port, also unplug the IAR 20-pin JTAG connector from the REva on-board 20-pin JTAG ISD connector. The IAR toolset and the IAR J-Link are not provided with the kit. For detailed information about the IAR products refers to the www.iar.com web site.
2
3 4
2.3
2.3.1
Hardware setup
Module/cable connections
Please ensure that the target hardware is connected as described below: 1. Plug the EM260 RCM module on the REva Raisonance two 6-pins, single row, and 0.1inch pitch sockets present in the wrapping zone (they enable direct connection of the RCM module to the REva ZigBee platform). Plug the ST microcontroller daughter board into the specific REva socket. Set the REva power jumper according to the settings described in Section 2.3.3 on page 12 and plug the REva USB cable into the PC USB port and the RLink port. Set the REva power jumper according to the settings described in Section 2.3.3 on page 12 and plug an external power supply connector into the REva 9V DC input jack. Plug the IAR J-Link 20-pin JTAG connector to the REva on-board 20-pins ISD connector and the J-Link USB cable to a PC USB port.
2. 3.
When using the Ride7 or RIDE toolset:
When using the IAR toolset: 4. 5.
If the application requires displaying debugging messages and/or interaction with the user, the following serial communication channels are supported:
Serial COM through RS232 (for all microcontrollers): Connect a serial cable between the PC serial port and the REva SER1 port. Connect the USB-Mini cable to the STR71x-9x USB mini-B connector and to a PC USB port. Vir tual COM through USB (only for STR71x-91x microcontrollers):
10/30
UM0389 Caution:
Quick start When unplugging the USB cable from the mini-B connector of the STR71x-9x daughter board, always hold the daughter board with one hand while removing the cable with the other. Otherwise, the daughter board could be torn off from the SO-DIMM connector.
2.3.2
REva board jumper settings
Table 1 lists the jumper settings for REva board functional areas (inputs, outputs, analog, com with the STM32F103x, STR71x, STR75x and STR91x daughter boards). Table 1. Settings for STM32F103x, STR71x, STR75x and STR91x daughter boards
Setting Fitted Fitted Fitted Unfitted Unfitted Fitted Unfitted Unfitted Fitted Fitted Fitted as |_| for STM32F103x and STR91x. Fitted as _| |_ for STR71x, STR75x Fitted Fitted Fitted Purpose Enable LED D7 (available for application use). Enable LED D6 (available for application use). Enable LED D5 (available for application use). Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Enable LED D2 (available for application use). Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Enable the BT5 button (available for application use). Enable the BT6 button (available for application use). Note that the POL jumper also has to be fitted to _| |_ position.
Jumper D7 D6 D5 D4 D3 D2 D1 D0 BT5 BT6
POL
Enable the BT6 button usage.
BUZZ TX RX
Enable buzzer (available for application use). Enable serial transmission (available for application use). Enable serial reception (available for application use).
11/30
Quick start
UM0389 Table 2 lists the jumper settings for REva board functional areas (inputs, outputs, analog, com with the ST7LITE39 daughter boards). Table 2. Settings for ST7LITE39 daughter boards
Setting Unfitted Unfitted Unfitted Unfitted Unfitted Fitted Unfitted Unfitted Fitted Fitted Fitted as |_| Fitted Fitted Purpose Exclusively used for the driver handling communication over the UART. Exclusively used for internal driver purposes. Exclusively used for internal driver purposes. Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Enable led D2 (available for application use). Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Exclusively used for the SN260 to the ST microcontroller serial communication over the SPI interface. Enable the BT5 button (available for application use). Enable the BT6 button (available for application use). Note that the POL jumper also has to be fitted to |_| position. Enable the BT6 button usage. Enable serial transmission (available for application use). Enable serial reception (available for application use).
Jumper D7 D6 D5 D4 D3 D2 D1 D0 BT5 BT6 POL TX RX
2.3.3
REva Power area
Ride7 and RIDE environments
When using the REva power jumper settings in a Ride7 or RIDE environment, keep the default configuration (USB power supply) as shown in Figure 4. Figure 4. REva power area (USB power supply)
Regulated voltage supplied from USB (configured by the daughter board) USB (5V) 2 REG Jack VDD 1
12/30
UM0389
Quick start
IAR environment (IAR J-Link JTAG emulator and external power supply)
When using the REva power jumper settings in an IAR environment, set the jumper for an external power supply as shown in Figure 5. Figure 5. REva power area (external power supply)
Regulated voltage supplied from jack (configured by the daughter board) USB (5V) 2 REG Jack VDD 1
2.3.4
Daughter board jumper settings
REva STM32F103x daughter board
For the REva STM32F103x daughter board, Table 3 and Figure 6 show the default settings. Table 3. REva STM32F103x daughter board
Setting Fitted Unfitted Flash boot mode RAM boot mode (the Flash boot mode is used) Purpose
Jumper FLASH RAM
Figure 6.
Boot mode setting for STM32F103x daughter board
13/30
Quick start
UM0389
REva STR71x daughter board
For the REva STR71x daughter board, Table 4 and Figure 7 show the default settings. Table 4. REva STR71x daughter board
Setting Fitted Unfitted Flash boot mode RAM boot mode (the Flash boot mode is used) Purpose
Jumper FLASH RAM
Figure 7.
Boot mode setting for STR71x daughter board
REva STR75x daughter board
For the REva STR75x daughter board, Table 5 shows the default settings. Table 5. REva STR75x daughter board
Setting Fitted Unfitted Fitted Unfitted Flash boot mode Flash boot mode Flash boot mode Flash boot mode Purpose
Jumper Boot0 = 0 Boot0 = 1 Boot1 = 0 Boot1 = 1
REva ST7LITE39 daughter board
For the REva ST7LITE39 daughter board, Table 6 and Figure 8 show the default settings. Table 6. REva ST7LITE39 daughter board
Setting Unfitted Fitted 5V power supply 3.3V power supply Purpose
Jumper 5V 3.3V
14/30
UM0389 Figure 8. Power area for REva ST7LITE39 daughter board
Quick start
Note:
The STR91x cannot boot from RAM. As a consequence, no specific boot jumpers are present on the STR91x daughter board.
2.3.5
Raisonance RLink jumper settings
When using STM32F103x, STR71x, STR75x and STR91x daughter boards, just keep the default jumper settings as shown in Figure 9. Figure 9. Power area for Raisonance RLink (STM32F103x, STR71x, STR75x and STR91x microcontrollers)
When using the ST7LITE39 daughter boards, set the jumpers as shown in Figure 10. Figure 10. Power area for Raisonance RLink (ST7LITE39 microcontroller)
15/30
Quick start
UM0389
2.4
Building the library
The library software relies on the software and build system framework introduced in the library layout section. What follows is a short introduction, aimed at providing enough knowledge to be able to build the software library using the Ride7 or RIDE toolset.
STM32F103x, STR7x-9x microcontrollers specific library building steps (Ride7 toolset)
1. 2. 3. Open the Ride7 toolset. From the Project, Open Project menu, open the ezsp\libs\ezsp_hal.rprj Ride7 project. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Device and select the specific STM32F103x or STR7x-9x microcontroller (STM32F103RBT6 as STM32F103x microcontroller, STR711FR2 as STR71x microcontroller, STR750FV2 as STR75x microcontroller, STR912FW44 as STR91x microcontroller). From the Options, Project Properties, Advanced ARM Options, Processor menu, open Boot mode and select Flash (the ST microcontroller daughter board Flash jumper has to be fitted). From the Options, Project Properties, GCC Compiler, Defines menu, select Defines and add the ST_STM32 define value for the STM32F103x microcontroller, the ST_STR71X define value for the STR71x microcontroller, the ST_STR75X define value for the STR75x microcontroller or the ST_STR91X define value for the STR91x microcontroller. From the Options, Project Properties, GCC Compiler, Compiler Output menu, open Debugging Information and select No Debug. From the Project menu, select Build Project: the ezsp_hal.lib library file is built in the ezsp\libs directory.
4.
5.
6. 7.
ST7LITE39 microcontroller specific library building steps (RIDE toolset)
1. 2. 3. 4. 5. 6. 7. 8. 9. Open the RIDE toolset. From the Project, Open menu, open the ezsp\libs\ezsp_hal_ST7.prj RIDE project. From the Options, Target, ST7 family menu, open Device and select ST7LITE39. From the Options, Target, ST7 family menu, open Properties, Settings, Memory Model and select Stack Long. From the Options, Project menu, open CXST7, Defines and add the ST_ST7;CODECUT define values. From the Options, Project menu, open CXST7, More and add -ga -oc +compact -pcp +split to the More Controls window. From the Options, Project, CLNK, Hex File Generation menu, select Generate a HEX file and select Intel HEX format. From the Options, Debug menu, open Real machine, Debug tool and select RLink. From the Project menu, select Build All.
10. On the Project tab, double-click on the make_library.wsc script file: a library ezsp_hal_ST7.lib will be produced into the ezsp\libs directory.
16/30
UM0389
Application examples
3
Application examples
Some applications are provided for showing the library package functions.
3.1
Setup the application serial communication channel
The provided application examples require displaying debugging messages and/or interaction with the user. Two serial communication channels are supported: serial COM through RS232 or virtual COM through USB.
Setup a serial COM through RS232 (for all microcontrollers)
1. 2. Connect a serial cable between the PC serial port and the REva SER1 port. Open a HyperTerminal on the serial COM port with the following configuration (the application messages and/or interactions come through the serial HyperTerminal): Bit rate: Data bits: Parity: Stop bits: Flow control: 9600 8 None 1 None
Setup a virtual COM communication through USB (only for STM32F103x and STR71x-91x microcontrollers)
1. Connect the USB-Mini cable to the STM32F103x or STR71x-91x USB mini-B connector and to a PC USB port. (The first time a STM32F103x or STR71x-91x USB device is plugged to the PC USB port, the user is required to install the corresponding USB software driver; select file stmcdc.inf in the serialUSB directory). Using the mouse, right-click on My Computer, select Manage, Device Manager, and open Ports (COM & LPT) to display a STM32F103x or STR71x-91x CDC communication port on a specific COMx port. The STM32F103x or STR71x-91x USB device has been recognized. Open a HyperTerminal on the corresponding USB virtual COMx port with the following configuration: Bit rate: Data bits: Parity: Stop bits: Flow control: 9600 8 None None None
2.
3.
Reset a virtual COMx communication channel
1. 2. 3. Disconnect the COMx HyperTerminal. Reset the REva board (STM32F103x or STR91x case) or Power OFF/ON the board (STR71x case). Make a call on the COMx HyperTerminal. The application messages and/or interactions come through the COMx HyperTerminal.
17/30
Application examples Note: 1
UM0389
When resetting the STR711FR2 microcontroller (using the REva RESET button), the PC is not able to enumerate again the STR71x USB device. To reset the STR71x USB device, power OFF/ON the REva board. The PC is able to recognize only a single STM32F103x or STR71x-91x USB device when plugged on a PC USB port. When connecting a second STM32F103x or STR71x-91x USB device to another PC USB port, the PC will not recognize it. If both the connectors (USB-mini and RS232) are connected, the virtual COM through USB communication is automatically selected by the application.
2
3
3.2
Version application
The version application is a simple application used to perform basic ZigBee operations: 1. 2. 3. Initialize the EmberZnet Stack. ezspVersion for getting the EmberZnet stack version running on the SN260 silicon. Get the Eui64 node address.
The following paragraphs provide a short introduction about how to build and run the application.
Specific building steps for STM32F103x and STR7x-9x microcontrollers (Ride7 toolset)
1. 2. 3. 4. Open the Ride7 toolset and open the Ride7 ezsp_hal.rprj project. Compile the library following the instructions in Section 2.4 on page 16. From the Project, Open Project menu, open the app\version\app\version.rprj Ride7 project. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Device and select the specific STM32F103x or STR7x-9x microcontroller (STM32F103RBT6 as STM32F103x microcontroller, STR711FR2 as STR71x microcontroller, STR750FV2 as STR75x microcontroller, or STR912FW44 as STR91x microcontroller). From the Options, Project Properties, Advanced ARM Options, Processor menu, open Boot mode and select Flash (the ST microcontroller daughter board Flash jumper has to be fitted). From the Options, Project Properties, Advanced ARM Options, Debug environment menu, open Debug tool and select RLink. From the Options, Project Properties, GCC Compiler, Defines menu, select Defines and add the ST_STM32 define value for the STM32F103x microcontroller, the ST_STR71X define value for the STR71x microcontroller, the ST_STR75X define value for the STR75x microcontroller or the ST_STR91X define value for the STR91x microcontroller. From the Options, Project Properties, GCC Compiler, Compiler Output menu, open Debugging Information and select No Debug. From the Options, Project Properties, LD Linker, Scripts menu, open Starter Kit Limitation and select NO.
5.
6. 7.
8. 9.
10. From the Project menu, select Build Project: a binary file is built in the app\version\app directory.
18/30
UM0389
Application examples
Specific building steps for ST7LITE39 microcontrollers (RIDE toolset)
Open the RIDE toolset and open the RIDE ezsp_hal_ST7.prj project. Compile the library following the instructions on Section 2.4 on page 16. From the Project, Open menu, open the app\version\app\version_ST7.prj RIDE project. 4. From the Options, Target, ST7 family menu, open Device and select ST7LITE39. 5. From the Options, Target, ST7 family menu, open Properties, Settings, Memory Model and select Stack Long. 6. From the Options, Project menu, open CXST7, Defines and add the ST_ST7; CODECUT define values. 7. From the Options, Project menu, select CXST7, More and add -ga -oc +compact -pcp +split to the More Controls window. 8. From the Options, Project, CLNK, Hex File Generation menu, select Generate a HEX file and select Intel HEX format. 9. From the Options, Debug menu, open Real machine, Debug tool and select RLink. 10. From the Project menu, select Build All: a binary file version is produced into the app\version\app directory. 1. 2. 3.
3.2.1
To run the version application
1. Connect the REva USB cable between the PC and the RLink.
Specific running steps for STM32F103x and STR7x-9x microcontrollers (Ride7 toolset)
2. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and select Debug for STM32F103x microcontrollers or unselect Debug for STR7x-STR9x microcontrollers. From the Debug menu, select Start. The version application image is then downloaded. Using the STM32F103x microcontroller, from the Debug menu, select Run and then Terminate.
3. 4.
Specific running steps for ST7LITE39 microcontrollers (RIDE toolset)
5. From the Debug menu, select Start version_st7.cos. The version application image is then downloaded.
Further steps for all ST microcontrollers
6. Set up the serial communication channel as described in Section 3.1 on page 17. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17. After setting the serial communication channel, certain messages are displayed in the PC HyperTerminal window. The example below shows a log of a version application execution: * * * Stack initialization performed with success * * * Stack Version = 3059 * * * EUI64 Node ID = 000D6F0 0 09A340. Note: The most recent EmberZNet 3.x stack version is 3059. The Ember ZNet 2.5.x stack version is 2553.
19/30
Application examples
UM0389
3.2.2
Load and run a version pre-built image
A pre-built image of the version application is already present in the bin directory. To download the version image into the ST microcontroller Flash and run the version application, follow these steps: 1. Connect the REva USB cable between the PC and the RLink.
Specific steps for STM32F103x and STR7x-9x microcontrollers (Ride7 toolset)
2. 3. Open the Ride7 toolset. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Device and select the specific STM32F103x or STR7x-9x microcontroller (STM32F103RBT6 as STM32F103x microcontroller, STR711FR2 as STR71x microcontroller, STR750FV2 as STR75x microcontroller, or STR912FW44 as STR91x microcontroller). From the Options, Project Properties, Advanced ARM Options, Debug environment menu, open Debug tool and select RLink. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and deselect Debug. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and select Erase target now! From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options, select Write Target Flash Now and select the bin\version.hex image file. Wait for the image to download into the Flash memory.
4. 5. 6. 7.
Specific steps for ST7LITE39 microcontrollers (RIDE toolset)
8. 9. 10. 11. Open the RIDE toolset. From the Options, Target, ST7 family menu, open Device and select ST7LITE39. From the Options, Debug menu, open Real machine, Tools and select RLink. From the Options, Debug menu, open Advanced Options, deselect Debug, click on Write Target Flash Now and select the bin\version_st7.hex image file. Wait for the image to download into the Flash memory.
Further steps for all ST microcontrollers
12. Set up the serial communication channel as described in Section 3.1 on page 17. 13. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17.
3.2.3
Building/running steps for STM32F103x and STR71x-STR91x microcontrollers using IAR toolset
1. 2. 3. 4. Open the IAR toolset. From the File, Open, Workspace menu, open the app\version\app\IAR\version.eww IAR workspace. From the View menu, select Workspace to display supported projects. (A window opens on the left side of the IAR environment.) From the Workspace selector window, select the application configuration according to the microcontroller to be addressed: version_STM32 for the STM32F103x microcontroller, version_STR71x for the STR71x microcontroller configuration or version_STR91x for the STR91x microcontroller configuration.
20/30
UM0389 5.
Application examples From the Project menu, select Rebuild All. An Intel HEX file version_STR71x.hex (or version_STR91x.hex) is built in the app\version\app\IAR directory.
To download the version application
1. 2. 3. 4. From the Project menu, select Debug. Wait for the image to download into the Flash memory. From the Debug menu, select Stop Debugging. Set the serial communication channel as described in Section 3.1 on page 17. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17.
3.3
Sensor and sink applications
The sensor and sink applications set a distributed sensors network. To build and run the sensor application, follow these steps: Specific building steps for STM32F103x and STR7x-9x microcontrollers (Ride7 toolset) Open the Ride7 toolset and open the Ride7 ezsp_hal.rprj project. Compile the library following the instructions in Section 2.4 on page 16. From the Project, Open Project menu, open the app\sink_sensor\app\sensor.rprj Ride7 project. 4. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Device and select the specific STM32F103x or STR7x-9x microcontroller (STM32F103RBT6 as STM32F103x microcontroller, STR711FR2 as STR71x microcontroller, STR750FV2 as STR75x microcontroller, or STR912FW44 as STR91x microcontroller). 5. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Boot mode and select Flash (the ST microcontroller daughter board Flash jumper has to be fitted). 6. From the Options, Project Properties, Advanced ARM Options, Debug environment menu, open Debug tool and select RLink. 7. From the Options, Project Properties, GCC Compiler, Defines menu, select Defines and add the ST_STM32 define value for the STM32F103x microcontroller, the ST_STR71X define value for the STR71x microcontroller, the ST_STR75X define value for the STR75x microcontroller or the ST_STR91X define value for the STR91x microcontroller. 8. From the Options, Project Properties, GCC Compiler, Defines menu, select Defines and add the SENSOR_APP; EZSP_HOST define values. 9. From the Options, Project Properties, GCC Compiler, Compiler Output menu, open Debugging Information and select No Debug. 10. From the Options, Project Properties, LD Linker, Scripts menu, open Starter Kit Limitation and select NO. 11. From the Project menu, select Build Project: a binary file is built in the app\sink_sensor\app directory. Specific building steps for ST7LITE39 microcontrollers (RIDE toolset) The sink and sensor applications are not supported by the ST7LITE39 microcontroller. 1. 2. 3.
21/30
Application examples
UM0389
3.3.1
To run the sensor application
1. Connect the REva USB cable between the PC and the RLink.
Specific running steps for STM32F103x and STR7x-9x microcontrollers (Ride7 toolset)
2. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and select Debug for STM32F103x microcontrollers and unselect Debug for STR7x-STR9x microcontrollers. From the Debug menu, select Start. The sensor application image is then downloaded. Using the STM32F103x microcontroller, from the Debug menu, select Run and then Terminate.
3. 4.
Specific running steps for ST7LITE39 microcontrollers (RIDE toolset)
The sink and sensor applications are not supported by the ST7LITE39 microcontroller.
Further steps for all ST microcontrollers
5. 6. 7. Set up the serial communication channel as described in Section 3.1 on page 17. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17. Follow the messages displayed in the HyperTerminal window for interacting with the sensor node and to see how this node communicates with a sink node. (The sensor node expects to send data to a sink node.)
Note:
For building and running the sink application, just open the app\sink_sensor\app\sink.rprj Ride7 project. Follow the same steps as for the sensor application, adding the SINK_APP define value instead of the SENSOR_APP one. Furthermore, another PC serial communication channel (serial RS232 or virtual COM through USB) is required for user interaction with the sink application. For a description of the sink and sensor applications refer to the related documentation. The sensor and sink applications are not supported by the ST7LITE39 microcontroller due to its smaller Flash memory (only 8 Kbytes) and RAM (only 384 bytes).
3.3.2
Load and run two sink and sensor pre-built images
Two pre-built images of the subscribed sensor and sink applications images are already present in the bin directory. To download the sensor.hex image into the ST microcontroller Flash and run the sensor application following these steps: 1. Connect the REva USB cable between the PC and the RLink.
Specific steps for STM32F103x and STR7x-9x microcontrollers
2. 3. Open the Ride7 toolset. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Device and select the specific STM32F103x or STR7x-9x microcontroller (STM32F103RBT6 as STM32F103x microcontroller, STR711FR2 as STR71x microcontroller, STR750FV2 as STR75x microcontroller, or STR912FW44 as STR91x microcontroller). From the Options, Project Properties, Advanced ARM Options, Debug environment menu, open Debug tool and select RLink.
4.
22/30
UM0389 5. 6. 7.
Application examples From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and deselect Debug. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and select Erase target now! From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options, select Write Target Flash Now and select the bin\sensor.hex image file. Wait for the image to download into the Flash memory.
Specific steps for ST7LITE39 microcontrollers
The sensor and sink applications are not supported by ST7LITE39 microcontrollers.
Further steps for all ST microcontrollers
8. 9. Set up the serial communication channel as described in Section 3.1 on page 17. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17.
Follow the same steps for configuring another REva board as sink node (using the bin\sink.hex pre-built image). Additionally, another PC serial communication channel (serial RS232 or virtual COM through USB) is required for user interaction with the sink node.
3.3.3
Building/running steps for STM32F103x and STR71x-STR91x microcontrollers using IAR toolset
1. 2. 3. 4. Open the IAR toolset. From the File, Open, Workspace menu, open the app\sink_sensor\app\IAR\sensor.eww IAR workspace. From the View menu, select Workspace to display supported projects. (A window appears on the left side of the IAR environment.) From the Workspace selector window, select the application configuration according to the microcontroller to be addressed: sensor_STM32 for the STM32F103x microcontroller configuration, sensor_STR71x for the STR71x microcontroller configuration or sensor_STR91x for the STR91x microcontroller configuration. From the Project menu, select Rebuild All. A sensor_STM32.hex (or sensor_STR71x.hex or sensor_STR91x.hex) Intel HEX file is built in the app\sink_sensor\app\IAR directory.
5.
To download the sensor application
1. 2. 3. 4. From the Project menu, select Debug. Wait for the image to download into the Flash memory. From the Debug menu, select Stop Debugging. Set up the serial communication channel as described in Section 3.1 on page 17. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17.
When building and running the sink application, just open the app\sink_sensor\app\IAR\sink.eww IAR workspace and follow the same steps as for the sensor application.
23/30
Application examples
UM0389
3.4
Light and switch applications
The light and switch applications control the switching on/off of a light.
Specific building steps for STM32F103x and STR7x-9x microcontrollers (Ride7 toolset)
1. 2. Open the Ride7 toolset and select the Ride7 ezsp_hal.rprj project. Compile the library following the instructions in Section 2.4: Building the library on page 16, and adding the following define value EMBER_SECURITY_LEVEL=0 (from the Options, Project Properties, GCC compiler, Defines menu). From the Project, Open Project menu, open the app\light\app\light.rprj Ride7 project. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Device and select the specific STM32F103x or STR7x-9x microcontroller (STM32F103RBT6 as STM32F103x microcontroller, STR711FR2 as STR71x microcontroller, STR750FV2 as STR75x microcontroller, or STR912FW44 as STR91x microcontroller). From the Options, Project Properties, Advanced ARM Options, Processor menu, open Boot mode and select Flash (the ST microcontroller daughter board Flash jumper has to be fitted). From the Options, Project Properties, Advanced ARM Options, Debug environment menu, open Debug tool and select RLink. From the Options, Project Properties, GCC Compiler, Defines menu, open Defines and add the ST_STM32 define value for the STM32F103x microcontroller, the ST_STR71X define value for the STR71x microcontroller, the ST_STR75X define value for the STR75x microcontroller or the ST_STR91X define value for the STR91x microcontroller. From the Options, Project Properties, GCC Compiler, Compiler Output menu, open Debugging Information and select No Debug. From the Options, Project Properties, LD Linker, Scripts menu, open Starter Kit Limitation and select NO.
3. 4.
5.
6. 7.
8. 9.
10. From the Project menu, select Build Project: a binary file is built in the app\light\app directory.
Specific building steps for ST7LITE39 microcontrollers (RIDE toolset)
1. 2. Open the RIDE toolset and open the RIDE ezsp_hal_ST7.prj project. Compile the library following the instructions on Section 2.4 on page 16, and adding the following new define value: EMBER_SECURITY_LEVEL = 0 (from Options, Project, CXST7 and Defines). From the Project, Open menu, open the app\light\app\light_ST7.prj RIDE project. From the Options, Target, ST7 family menu, open Device and select ST7LITE39. From the Options, Target, ST7 family menu, open Properties, Settings, Memory Model and select Stack Long. From the Options, Project menu, open CXST7, Defines and add the ST_ST7;CODECUT define values. From the Options, Project menu, open CXST7, More and add -ga -oc +compact -pcp +split to the More Controls window. From the Options, Project, CLNK, Hex File Generation menu, select Generate a HEX file and select Intel HEX format.
3. 4. 5. 6. 7. 8.
24/30
UM0389
Application examples 9. From the Options, Debug menu, open Real machine, Tools and select RLink. 10. From the Project menu, select Build All: a binary file is built in the app\light\app directory.
3.4.1
To run the light application
1. Connect the REva USB cable between the PC and the RLink.
Specific running steps for STM32F103x and STR7x-9x microcontrollers (Ride7 toolset)
2. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and select Debug for STM32F103x microcontrollers and unselect Debug for STR7x-STR9x microcontrollers. From the Debug menu, select Start. The light application image is then downloaded. Using the STM32F103x microcontroller, from the Debug menu, select Run and then Terminate.
3. 4.
Specific running steps for ST7LITE39 microcontrollers (RIDE toolset)
5. From the Debug menu, select Start light_st7.cos. The light application image is then downloaded.
Further steps for all ST microcontrollers
6. 7. Note: Set up the serial communication channel as described in Section 3.1 on page 17. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17.
To build and run the switch application, open the app\light\app\switch.rprj (STM32F103x or STR7x-9x Ride7 projects) or app\light\app\switch_ST7.prj (ST7 RIDE projects). Follow the same steps as for the light application. Furthermore, another PC serial communication channel (serial RS232 or virtual COM through USB) is required for getting information from the switch node. For a description of the light and switch applications refer to the corresponding documentation.
25/30
Application examples
UM0389
3.4.2
Load and run two light and switch pre-built images
Two pre-built images of the subscribed light and switch applications images are already present in the bin directory. To download the light.hex (STM32F103x or STR7x-9x case) or the light_st7.hex (ST7 case) image into the ST microcontroller Flash and run the light application, follow these steps: 1. Connect the REva USB cable between the PC and the RLink.
Specific steps for STM32F103x and STR7x-9x microcontrollers
2. 3. Open the Ride7 toolset. From the Options, Project Properties, Advanced ARM Options, Processor menu, open Device and select the specific STM32F103x or STR7x-9x microcontroller (STM32F103RBT6 as STM32F103x microcontroller, STR711FR2 as STR71x microcontroller, STR750FV2 as STR75x microcontroller, or STR912FW44 as STR91x microcontroller). From the Options, Project Properties, Advanced ARM Options, Debug environment menu, open Debug tool and select RLink. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and deselect Debug. From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options and select Erase target now! From the Options, Project Properties, Cortex RLink, Advanced Options menu, open Advanced Options, select Write Target Flash Now and choose the bin\light.hex image file. Wait for the image to download into the Flash.
4. 5. 6. 7.
Specific running steps for ST7LITE39 microcontrollers
8. 9. Open the RIDE toolset. From the Options, Target, ST7 family menu, open Device and select ST7LITE39.
10. From the Options, Debug menu, open Real machine,Tools and select RLink. 11. From the Options, Debug menu, open Advanced Options, deselect Debug, click on Write Target Flash Now and select the bin\light_st7.hex image file. Wait for the image to download into the Flash.
Further steps for all ST microcontrollers
12. Set up the serial communication channel as described in Section 3.1 on page 17. 13. If using the virtual COM, reset the corresponding communication channel as described in Section 3.1 on page 17. Follow the same steps for configuring another REva board as switch node, using the bin\switch.hex (STM32F103x or STR7x-9x case) or bin\switch_st7.hex (ST7 case) pre-built image. Additionally, another PC serial communication channel (serial RS232 or virtual COM through USB) is required for user interaction with the switch node.
26/30
UM0389
Application examples
3.4.3
Building/running steps for STM32F103x and STR71x-STR91x microcontrollers using IAR toolset
1. 2. 3. 4. Open the IAR toolset. From the File, Open, Workspace menu, open the app\light\app\IAR\light.eww IAR workspace. From the View menu, select Workspace to display supported projects. (A window appears on the left side of the IAR environment.) From the Workspace selector window, select the application configuration according to the microcontroller to be addressed: light_STM32 for the STM32F103x microcontroller configuration, light_STR71x for the STR71x microcontroller configuration or light_STR91x for the STR91x microcontroller configuration. From the Project menu, select Rebuild All. An Intel HEX file light_STR71x.hex (or light_STR91x.hex) is built in the app\light\app\IAR directory.
5.
To download the light application
1. 2. 3. 4. Note: From the Project menu, select Debug. Wait for the image to download into the Flash memory. From the Debug menu, select Stop Debugging. Set up the serial communication channel as described in Section 3.1 on page 17. If using the virtual COM, reset the relative communication channel as described in Section 3.1 on page 17.
When building and running the switch application, just open the app\light\app\IAR\switch.eww IAR workspace and follow the same steps as for the light application.
27/30
SPI bootloader
UM0389
4
SPI bootloader
The EmberZNet 3.0.2 stack supports the bootloader through the SPI interface feature. Basically, it is possible to update the SN260 ZigBee stack image by running a simple application on the STM32F103RBT6 microcontroller which is able to put the SN260 in bootloader mode and then sending the new stack image packets through the SPI interface. This application requires the SN260 previously loaded with a stack version (EmberZNet 3.0.1 or more recent) supporting the bootloader. The upload process consists of the following steps: 1. 2. 3. Open a DOS command window. Go to the directory bin/spi_bootloader/ Type the following command for loading the STM32_upload_stack_3_0_2_spi.hex application into the STM32F103RBT6 microcontroller Flash memory: run.bat STM32 STM32_upload_stack_3.0.2_spi.hex During the upload process, LEDs D7 and D6 on the REva board indicate the process status:
LED D7 is ON: Process initialization OK LED D6 blinks every 2 seconds and LED D7 is ON: Upload IN PROGRESS LED D7 is OFF and LED D6 blinks every quarter second: Upload FAILED LEDs D7 and D6 blink alternatively every quarter second: Upload process completed with SUCCESS.
The user can also plug a serial cable to the REva SER1 port to receive upload status messages over the corresponding serial HyperTerminal. The HyperTerminal settings are:
Bit rate: Data bits: Parity: Stop bits: Flow control:
9600 8 None 1 None
5
Limitations and support
For any questions about the library, issues notifications refer to the specific link on the STMicroelectronics web site.
28/30
UM0389
Revision history
6
Revision history
Table 7.
Date 13-Feb-2007 12-Mar-2007 02-Apr-2007 21-May-2007 28-May-2007
Document revision history
Revision 1 2 3 4 5 Initial release. Document updated adding full scope support for STR71xF, STR75xF and ST7LITE39 microcontrollers Document updated adding full scope support for STR71xF, STR75xF, ST7LITE39 and STR91xF microcontrollers Document updated adding full scope support for the EmberZNet 3.0.0 ZigBee stack Document updated adding full scope support for both EmberZNet 2.5.x and EmberZNet 3.x stacks Power selection jumper on the ST7LITE39 daughter board set to 3.3V (Default configuration at delivery) and not to 5V. Added Figure 7: Boot mode setting for STR71x daughter board on page 14 and Figure 8: Power area for REva ST7LITE39 daughter board on page 15. Document updated adding full scope support for the most recent 3.x stack with the SPI bootloader feature. Added IAR toolset support and virtual COM through USB communication. Reviewed REva power area description and library/application building/running steps. Added information concerning Ride7 toolset and STM32F103x microcontrollers. Changes
17-Sep-2007
6
5-Oct-2007
7
3-Dec-2007
8
29/30
UM0389
Please Read Carefully:
Information in this document is provided solely in connection with ST products. STMicroelectronics NV and its subsidiaries ("ST") reserve the right to make changes, corrections, modifications or improvements, to this document, and the products and services described herein at any time, without notice. All ST products are sold pursuant to ST's terms and conditions of sale. Purchasers are solely responsible for the choice, selection and use of the ST products and services described herein, and ST assumes no liability whatsoever relating to the choice, selection or use of the ST products and services described herein. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. If any part of this document refers to any third party products or services it shall not be deemed a license grant by ST for the use of such third party products or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoever of such third party products or services or any intellectual property contained therein.
UNLESS OTHERWISE SET FORTH IN ST'S TERMS AND CONDITIONS OF SALE ST DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY WITH RESPECT TO THE USE AND/OR SALE OF ST PRODUCTS INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE (AND THEIR EQUIVALENTS UNDER THE LAWS OF ANY JURISDICTION), OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS EXPRESSLY APPROVED IN WRITING BY AN AUTHORIZED ST REPRESENTATIVE, ST PRODUCTS ARE NOT RECOMMENDED, AUTHORIZED OR WARRANTED FOR USE IN MILITARY, AIR CRAFT, SPACE, LIFE SAVING, OR LIFE SUSTAINING APPLICATIONS, NOR IN PRODUCTS OR SYSTEMS WHERE FAILURE OR MALFUNCTION MAY RESULT IN PERSONAL INJURY, DEATH, OR SEVERE PROPERTY OR ENVIRONMENTAL DAMAGE. ST PRODUCTS WHICH ARE NOT SPECIFIED AS "AUTOMOTIVE GRADE" MAY ONLY BE USED IN AUTOMOTIVE APPLICATIONS AT USER'S OWN RISK.
Resale of ST products with provisions different from the statements and/or technical features set forth in this document shall immediately void any warranty granted by ST for the ST product or service described herein and shall not create or extend in any manner whatsoever, any liability of ST.
ST and the ST logo are trademarks or registered trademarks of ST in various countries. Information in this document supersedes and replaces all information previously supplied. The ST logo is a registered trademark of STMicroelectronics. All other names are the property of their respective owners.
2007 STMicroelectronics - All rights reserved STMicroelectronics group of companies Australia - Belgium - Brazil - Canada - China - Czech Republic - Finland - France - Germany - Hong Kong - India - Israel - Italy - Japan Malaysia - Malta - Morocco - Singapore - Spain - Sweden - Switzerland - United Kingdom - United States of America www.st.com
30/30
|
