Table of Contents
[hemmerling] STMicroelectronics ARM-based MPUs
Company & Products & Community
Company & Products
- mikrocontroller.net "STM32" - “ARM Cortex-M3 CPU”.
- Evalboard STMicroelectronics "STM32F100".
- STMicroelectronics MCU strategy is a “without MMU” and so “no Linux” aka “no Windows CE Embedded”.
Community
E-Learning
-
-
- 2016-01-25, 8:00 CET - 2016-01-29, 17:00 CET → I registered.
- 2016-04-04, 8:00 CET - 2016-04-08, 17:00 CET → I registered.
- 2016-06-13, 8:00 CET - 2016-06-17, 17:00 CET.
- STM32F7 online course, with hands-on exercises.
- 2016-02-08, 8:00 CET - 2016-02-12, 17:00 CET → I registered.
- 2016-03-14, 8:00 CET - 2016-03-18, 17:00 CET.
- 2016-05-23, 8:00 CET - 2016-05-27, 17:00 CET → I registered.
-
Events
- As of 2017-10, if you don´t get a confirmation for participating in a free German STMicroelectronics workshop,
- Call by phone the German office “STMicroelectronics GmbH, Bahnhofstraße 18, D-85609 Aschheim, +49 89 460060” and negociate, that you may send your confirmation wish by E-Mail to reception.munich@st.com.
Tools
STLink ( ST-Link ) Link Utilities
- STMicroelectronics "STSW-LINK004. STM32 ST-LINK utility" - Current version of ST-Link in 2016-10. Recommended also for Windows 8 → Work on Win8.1, 32-bit
. Current version of ST-Link in 2016-10.
USB drivers for Link Utilities
- STMicroelectronics "STSW-LINK009" - “ST-LINK, ST-LINK/V2, ST-LINK/V2-1 USB driver signed for Windows7, Windows8, Windows10”. Current version of ST-Link USB drivers in 2016-10.
Software Design Support Concepts
System Workbench for STM32 ( SW4STM32 )
- Keyboard command “CTRL”+“Space” - Enable autocompletion % intellisense function.
- On my Win10Pro-64bit system, I need to setup SW4STM32 by “C++ Build / Builder Type” from “External Builder” to “Internal Builder”.
STM Studio ( STMStudio )
-
- “STM Studio run-time variables monitoring and visualization tool for STM32 microcontrollers” → Access to MPU registers, e.g for touch applications.
- “STMStudio requires the Java Runtime Environmen version 7 at minimum (32bit version preferred)”
STM32Cube ( formerly: MicroXplorer )
The Tool
- The free software
- STMicroelectronics "STM32CubeMX - STM32Cube initialization code generator (UM1718)" - “STM32CubeMX is an extension of the existing MicroXplorer tool”.
- STMicroelectronics "STM32Cube Ecosystem", 2022-02.
- Tools:
- STM32CubeMX, a configuration tool for any STM32 device. This easy-to-use graphical user interface generates initialization C code for Cortex-M cores and generates the Linux device tree source for Cortex-A cores.
- STM32CubeIDE, an Integrated Development Environment. Based on open-source solutions like Eclipse or the GNU C/C++ toolchain, this IDE includes compilation reporting features and advanced debug features. It also integrate additional features present in other tools from the ecosystem, such as the HW and SW initilialization and code generation from STM32CubeMX.
- STM32CubeProgrammer, a programming tool. It provides an easy-to-use and efficient environment for reading, writing and verifying devices and external memories via a wide variety of available communication media (JTAG, SWD, UART, USB DFU, I2C, SPI, CAN, etc.).
- STM32CubeMonitor family of tools. Powerful monitoring tools that help developers fine-tune the behavior and performance of their applications in real time.
- Packages:
- STM32Cube MCU and MPU packages, dedicated to each STM32 series. Packages offer all the required embedded software bricks to operate the available set of STM32 peripherals. They include drivers (HAL, low-layer, etc.), middleware, and lots of example code used in a wide variety of real-world use cases.
- STM32Cube expansion packages, for application-oriented solutions. Complementing and expanding the STM32Cube MCU Package offer with additional embedded software bricks, STM32 expansion packages come either from ST or approved partners to create an extensive and scalable embedded software offer around the STM32.
- The free legacy software Archive.org "STMicroelectronics: MicroXplorer - MCU graphical configuration tool" for Windows.
GitHub Repository
Eclipse Plugin
- STMicroelectronics "STSW-STM32095" - “STM32CubeMX Eclipse plug in for STM32 configuration and initialization C code generation”.
Necessary Add-Ons
- To operate STM32Cube, you need both.
- Compiler / IDE support, so that the code generated by STM32Cube may be compiled ( “Project Settings / Toolchain/IDE” ).
- Targets:
- EWARM - IAR 7.40 is shipped with STM32Cube support. No extras must be installed.
- MDK-ARM V5 - Keil MDK 5.40 needs a MDK5 Software Packs for each board, e.g. “KeilSTM32F4xx_DFP.?.?.?.pack”, “KeilSTM32L0xx_DFP.?.?.?.pack”.
- TrueSTUDIO.
- SW4SM32 - The generated code is for the free “System Workbench for STM32”.
- For STM32Cube project, be shure to set the language standard to C99.
- Project name - mouse rightclick, “Properties / C/C++ Build / Settings / MCU GCC Compiler / Dialect”.
- Select “ISO C99 (-std=c99)” as “Language standard”.
- Em::Blocks, inoffically.
- The generated code for TrueSTUDIO SW4SM32 and is for GNU C/C++ compiler. I was told by experts that the generated code may be compiled with the OpenSource IDE “Em::Blocks” → See ARM Embedded Systems ( ARM7, ARM8, ARM9, ARM11, Cortex ). How to proceed:
- Set the right target ( “Project / Settings / Project / Toolchain/IDE” ) - “TrueSTUDIO” or “SW4STM32”.
- Let STM32CubeMX generate the code ( “Project / Generate Code” ).
- Create an empty “Em::Blocks” project.
- Delete files and directories:
- Delete the directories of the “Em::Blocks” project.
- cmsis.
- incl.
- SPL.
- src.
- Delete the two GNU linker scripts ( “*.ld” ) of the root directory of the “Em::Blocks” project.
- Copy files and directories:
- Copy the directories of the code generated by STM32Cube to the “Em::Blocks” project directory:
- Drivers.
- Inc.
- Src.
- Copy the GNU linker script, e.g. “TrueSTUDIO\gpio\STM32F429ZI_FLASH.ld” of the STM32CubeMX project to the root of the of the empty “Em::Blocks” project.
- Delete files and directories:
- Delete the directories of the the “Em::Blocks” project:
- “Drivers / CMSIS / Device / STM32F4xx / Source / Templates / arm”.
- If you include these files by error in your project, you will get the error message “Drivers\CMSIS\Device\ST\STM32F4xx\Source\Templates\arm\startup_stm32f427xx.s:1: Error: junk at end of line, first unrecognized character is `*'”
, as the GCC Assembler just support C/C++ style comments ( ”/ /” and ”/* .. */” ), but not the traditional Assembly comment style ”;”.
- “Drivers / CMSIS / Device / STM32F4xx / Source / Templates / iar”.
- Load the “Em::Blocks” project.
- Right-mouseclick “Remove Files”, “Multiple Selection” → (ok).
- Right-mouseclick “Add files recursively”, “Multiple Selection” → (ok), “Select the targets this file should belong to” → (ok).
- At “Drivers / CMSIS / Device / STM32F4xx / Source / Templates / gnu”, exclude all files with the exception of the proper startup file ( e.g. “startup_st32f427xx.s” from the project, by marking the files, mouse-rightclick “Remove files from project”.
- Exclude the file “Drivers / STM32F4xx_HAL_Driver / Src / stm32f4xx_hal_msp_template.c” from the project - “This file contains the HAL System and Peripheral (PPP) MSP initialization and de-initialization functions. It should be copied to the application folder and renamed into 'stm32f4xx_hal_msp.c'”.
- If you fail, you will get the error message “Src/stm32f4xx_hal_msp.c:45: multiple definition of 'HAL_MspInit'”
- GoodKook's Place "STM32CubeMX and examples of using the Eclipse CDT / GNU tools: LED On (Part 2 compilation and build)" - The author suggests to set the global symbol “USE_HAL_DRIVER” and a MCU target specific global symbol e.g. “STM32F429xx”.
- At “Project / Build options / Compiler settings / #defines” add the symbol name for your MCU, e.g “STM32F429xx”, as suggested in the file “Drivers / CMSIS / Device / ST / STM32F4xx / Include / stm32f4xx.h”. If you fail, the compilation breaks by the error message '#error “Please select first the target STM32F4xx device used in your application (in stm32f4xx.h file)”'.
- Tips & tricks:
- There are two kind of “*.ioc” files:
- The original “*.ioc” one is that which contains the ST32Cube project. In the root of each created code export directory, another “*.ioc” file is stored.
- With the original “*.ioc” file, you may set a path to export code.
- With the exported “*.ioc” files, this option is grayed.
- Loading the exported “*.ioc” file and republishing code by “Project / Generate Code” is not suggested ( neither for another target compiler, nor for the same target compiler ). If you republish a second ”.iot” file for with SW4SM32, the code still compiles successfully, but the project configuration information is corrupt:
- In the debug configuration settings, you can´t set the name of the project anymore - the “current” project is not offered as choice.
- By this, the transfer to the target by the GDB debugger fails by an error message of the GDB debugger.
- Minimum project configuration by STM32Cube:
- “Sys / Debug” option with “Serial Wire Debug (SWD)” - If you forget, you won´t be able to debug the software.
- “Project / Settings / Code Generator / HAL Settings” - ”[ ] Set all free pins analog (to optimize the power consumption)”.
- There are 2 reporting options:
- “Project / Generate Report” generates a PDF.
- “Pinout / Generate CSV pinout text file”.
- To use the “High Speed External” ( HSE ) clock, you just define a pin at “Reset & Clock Control” ( RCC ).
- “GPIO Maximum Output Speed” ( STM term ) = “Slew Rate” ( usual engineering term ).
- Hardware support for a board, by STM32Cube.
- Hardware abstraction layer for MCUs and boards ( “Board support packages” ), for use with “STM32Cube”. Please don´t unzip the ZIP files, this is done automatically by the import process of the “New Libraries Manager” available at STM32CubeMX by “Help / Install New Libraries”:
Resources
- The USP feature of STM32CubeMX is the interactive “Clocktree Overview” chart.
- The Assembly code generated by STM32Cube requires the generated GNU linker script.
- Be shure to understand the difference between ”.S” ( may contain preprocessor commands, e.g. C-style comments ) and ”.s” files with GCC.
STM32Snippets
Tools for NFC
- The free Keil MDK-ARM for STM32L0.
- KEIL "MDK for STMicroelectronics STM32F0 and STM32L0 Installation & Activation", Product Serial Number (PSN) to activate the MDK for STM32F0 and STM32L0: “U1E21-CM9GY L3G4L”.
- KEIL "Limitations" for “MDK-ARM Lite Edition”.
- The PC CR95HF development software STMicroelectronics "STSW-95HF001. PC software executable for DEMO-CR95HF-A board (UM1084)".
-
- M24LR board.
- RF transceiver board - CR95HF-VMD5T 13.56 MHz multi-protocol contactless transceiver IC.
- Smartphone apps:
Tools for NFC 2017 Workshop
- Workshop STMicroelectronics "Complete NFC solution for embedded applications hands-on workshop", 2017-10-19 in München.
- Hardware.
- Software.
TouchGFX - Your Free Graphical UI Tool in the STM32 Ecosystem
Libraries & Frameworks
The legacy Standard Periphal Library
- With the SP library, the software developer is responsible for timing.
Hardware Abstraction Layer ( HAL ) & Low Level Library
Hardware Abstraction Layer ( HAL )
- HAL libraries makes use of:
- Trap handlers.
- Calbacks.
- With the HAL library, the library takes care of necessary timing to access hardware and wait for response signals.
Low Level Library
- With the LL library, the software developer is responsible for timing.
- It is the successor of the SP library, for boards & MCUs with low resources ( RAM, Flash ROM,..).
CMSIS
emWin, STemWin
- The commercial source code graphics library SEGGER Microcontroller GmbH & Co. KG "emWin".
- The free binary-only graphics library STMicroelectronics "STemWin. Professional graphical stack library enabling the building up of Graphical User Interfaces (GUIs) (AN4323)".
- en.radzio.dxp.pl "STemWin library STM32F429 example" - “Due to STemWin flash usage any serious application that use this library exceeds 32kB of Flash memory, so we can't use demo version of Keil uVision”.
Resources
MCUs with LoRa Support
STM32WLEx
LoRa
- See Wireless Networks.
Boards
- The DISCOVERY boards includes an ST-LINK/V2 embedded debug tool interface that is supported by the following software toolchains: IAR, KEIL, ATOLL ( so you don´t need to buy a ST-Link/V2 ).
- DISCOVERY boards are a small application with as much sensors and actors as you can, while the NUCLEO board are in Arduino format, a base frame without (much) sensors and actors.
1. My STM32 Value Line Discovery Board -> STM32F100RB, based on Cortex M3
- Evalboard STMicroelectronics "STM32 Discovery Board" with STM32F100RB MCU ( 128 KB Flash, 8 KB RAM ).
2a. My STM32L-Discovery Board -> STM32L1, based on Cortex M3
- Evalboard STMicroelectronics "STM32L-DISCOVERY", STMicroelectronics "STM32L Discovery Board" with STM32L152RB MCU ( 128 KBytes Flash, 16 KBytes RAM, 4 KB EEPROM ).
- I was told by experts that the STM32L chip series is on the power consumption level of Texas Instruments MSP430!
2b. My STM32 L1 Discovery Special Edition Board -> STM32L152RTC6, based on Cortex M3
- Evalboard “STM32 L1 Discovery Special Edition” with “STM32L152RTC6” MCU ( STMicroelectronics "STM32L151/152" ).
3. My STM32 F3 Discovery Board -> STM32 F3, based on Cortex M4
- 2 x Evalboard STMicroelectronics "STM32 F3 Discovery Board", STMicroelectronics "STM32F3DISCOVERY" with STM32F303 MCU ( 256 KB Flash, 48 KB RAM ) and with compass & gyroscope.
- If you remove the 2 jumpers of at the top of the board next to the inscripts “ST-Link” & “Discovery”, you might use the STLink Debugger for your own boards.
4. My STM32 F4 Discovery Board -> STM32F4, based on Cortex M4
- Evalboard STMicroelectronics "STM32F4DISCOVERY Discovery kit for STM32F407/417 lines - with STM32F407VG MCU" with STM32F407VG MCU ( 1 MB of Flash memory, 192+4 KB of RAM ) and with 3-axis accelerometer, audio sensor, omni-directional digital microphone and audio DAC with integrated class D speaker driver.
5. My STM32 F4 Discovery Board -> STM32F429, based on Cortex M4
- Evalboard STMicroelectronics "32F429IDISCOVERY Discovery kit for STM32 F429/439 lines", STMicroelectronics "STM32 F4 Discovery Board" with STM32F429ZI MCU ( 2 MB of Flash memory, 256 KB of RAM ).
- Useful addon tools:
- The OpenSource graphics tool GIMP for Linux, Windows.
- The free graphics format convertion tool “ST32 Imager” by STMicroelectronics for Windows.
- Output formats:
- 32bpp.
- 24bpp.
- 16bpp ARGB1555.
- 16bpp ARGB4444.
- 16bpp RGB565.
- 8bpp Indexed.
- 4bpp Indexed.
- 2bpp Indexed.
- 1bpp Indexed
- 8bpp Transparency.
- 4bpp Transparency.
- The free command line tool “bin2c” converter by STMicroelectronics for Windows.
- STM32Cube “STM32F4”, “STM32F429/439”, “LQFP144”, “STM32F439ZITx”.
- Input frequency for this board ( HCLK ) = 8 Mhz ).
-
6. STM32 M24LR Discovery Board -> STM32F103CB, based on Cortex M3
- Evalboard STMicroelectronics "M24LR-DISCOVERY. Discovery kit for M24LR04E Dual Interface EEPROM with energy harvesting" with 2 boards.
- RF transceiver board with STMicroelectronics "STM32F103CB".
- M24LR board.
- STMicroelectronics "STSW-95HF001. PC software executable for DEMO-CR95HF-A board (UM1084) - “CR95HF Development Software”.
7. Nucleo Boards
Overview
The M24SR Ecosystem
7.1 My STM32L053R8 Nucleo -> STML053R8T6, based on Cortex M0+
- “STML053R8T6” MCU with 64 KBytes of Flash, 8 Kbytes of SRAM.
- Similar board: mbed "ST Nucleo L152RE".
- Software for this board can be compiled by the free online development system mbed.
- The board is in Ardunio format. Additionaly to the standard Ardunio interface, it has extra ST interfaces.
7.2 My STM32L476 Nucleo-64 -> STML476RG, based on Cortex M4
7.3 My STM32F207 Nucleo-144 -> STMF207ZGT6, based on Cortex M3
7.4 My NUCLEO-F303ZE Nucleo-144 -> STM32F303ZE, based on Cortex M4
7.5 My P-NUCLEO-LRWAN1 Nucleo with LoRa RF Extension -> STM32L073RZT6, based on Cortex M0+
-
- “NUCLEO-L073RZ Nucleo Development Board”.
- “SX1272MB2DAS LoRa RF Expanion Board”.
- STMicroelectronics "I-CUBE-LRWAN" - “LoRaWAN software expansion for STM32Cube (UM2073)”.
7.6 My P-NUCLEO-IHM001 Nucleo Pack FOC and 6-step motor control -> STM32F302R8, based on Cortex M4
- "P-NUCLEO-IHM001" - “Motor Control Nucleo Pack with NUCLEO-F302R8 and X-NUCLEO-IHM07M1”.
Shields
- My M24SR shield “Wi-Fi expansion board based on SWPF01SA module for STM32 Nucleo”:
- My M24SR shield “Dynamic NFC tag expansion board based on M24SR for STM32 Nucleo”:
- My M24SR shield “Sub-GHz RF expansion board for STM32 Nucleo”:
- My M24SR shield “Bluetooth low energy expansion board based on BlueNRG for STM32 Nucleo”:
- My M24SR shield “Bluetooth Low Energy expansion board based on SPBTLE-RF module for STM32 Nucleo”:
- My M24SR shield “MEMS Inertial and Environmental expansion board for STM32 Nucleo”:
- My M24SR shield “Stepper Motor driver expansion board based on easySPIN L6474 for STM32 Nucleo”:
- My M24SR shield “Two axis stepper motor driver expansion board based on the L6470 for STM32 Nucleo”:
- My M24SR shield “Three-phase brushless DC motor driver expansion board based on L6230 for STM32 Nucleo”:
- My M24SR shield “Industrial input/output expansion board based on VNI8200XP and CLT01-38SQ7 for STM32 Nucleo”:
- My M24SR shield “Digital MEMS microphones expansion board based on MP34DT01-M for STM32 Nucleo”:
8. My M24LR-DISCOVERY
-
- Hardware:
- The red M24LR board with STM8L152C6T6 CPU.
- SWIM connector for programming and debugging. Hardware debugger:
- Or you may use any “STM8 discovery” board, separate the shipped ST-Link debugger or just pull off a jumper to use it for debugging by SWIM connector.
- The green RF transceiver board, with STM32F103CB CPU.
- Windows USB devicename: “MB 1054A CR95HF”.
- Software: STMicroelectronics "STSW-95HF001. PC software executable for DEMO-CR95HF-A board (UM1084) - “CR95HF Development Software”.
- Resources.
9. My STM32L053 Discovery -> STML053R8T6, based on Cortex M0+
- STMicroelectronics "32L0538DISCOVERY Discovery kit with STM32L053C8 MCU", with E-paper display,.
10. My STM32F746G Discovery -> STM32F746NG, based on Cortex M7
- Recommended software:
- The commercial IDE IAR 7.4, 30 day evaluation timeout.
- Make sure you have the latest JAVA and .NET environments.
11. My STM32 LoRa Discovery -> STM32L072CZY6TR, based on Cortex M0
- STM32Cube “STM32L4”, “STM32L4x6”, “LQFP100”, “STM32L476VGTx”.
- By the windows executable application “qspieraser.bin”, you can delete the USB flash disk more quicky, than by accessing the Windows explorer.
- Remember that the evaluation board is not intended to be an audio player, i.e. the Flash memory is not intended for frequent data changes, like by copying new audio files to the file system.
12. My 32L476 Discovery -> STM32L467VGT6, based on Cortex M4
13. My IoT tracker node kit
- I was invited to join the exhibition and conference WT - Wearable Technologies Europe 2019 ( WT ) at Messe München in München, Germany, 2019-02-05 - 2019-02-06. Especially I participated in the “STMicroelectronics and Sigfox Developer Workshop 2019” of “Innovation World Cup Series” in München during that event, on 2019-02-05.
- Innovation World Cup Munich "STMicroelectronics and Sigfox Developer Workshop 2019" in München, 2019-02-05.
- The IoT tracker node kit includes an STM32 Microcontroller and two expansion boards for Sigfox connectivity along with inertial and environmental sensors.
- NUCLEO-L053R8 (STM32 Nucleo-64 development board with STM32L053 MCU)
- X-NUCLEO-S2868A1 (Sub-1 GHz 868 MHz RF expansion board based on S2-LP radio)
- X-NUCLEO-IKS01A2 (motion MEMS and environmental sensor expansion board)
- Instructions and downloads:
- armKEIL "MDK5 Device List / STMicroelectronics STM32L053R8" - “For S2-LP Hands On - Check for STM32L0 package update”.
14. My STEVAL-IDB008V2 Discovery Board & My STEVAL-FKI868V2 Board
- My hands-on workshop STMicroelectronics "Easy, fast and affordable low-power RF design with BlueNRG-2 and S2-LP" in Dortmund, 2019-04-09.
- Instructions and downloads:
STEVAL-IDB008V2 Discovery Board
- STMicroelectronics "STEVAL-IDB008V2" - “Evaluation platform based on the BlueNRG-2”.
- Smartphone App
- Software.
- armKEIL "STMicroelectronics BlueNRG-2" - “Device Family Pack. STMicroelectronics BlueNRG-2 Series Device Support”.
- STMicroelectronics "STSW-BLUENRG1-DK" - “The STSW-BLUENRG1-DK evaluation SW package is based on the BlueNRG-1 and BlueNRG-2 very low power Bluetooth low energy (BLE) single-mode systems-on-chip with 160 KB and 256 KB of Flash memory, respectively, 24 KB of RAM, 32-bit core ARM Cortex-M0 and ADC, GPIOs, I²C, RTC, SPI, Timers, UART, WDG and RTC peripherals”.
- STMicroelectronics "STSW-BNRGUI" - “The STSW-BNRGUI software package consists of a graphical user interface (GUI) PC application that can be used to interact and evaluate the capabilities both of the BlueNRG and BlueNRG-MS Bluetooth low energy network processors, which are low power Bluetooth® Smart ICs, compliant with the Bluetooth specifications. It also supports the BlueNRG-1 and BlueNRG-2 Bluetooth low energy systems-on-chip: low power Bluetooth smart ICs that are compliant with the Bluetooth® specification, both in master and slave roles”.
- “Window10 driver installation issues”.
- PDF document “Window10 driver installation issues. Users of Windows 10 –issue with BlueNRGand S2-LP driver installation. Issue linked to signed driver enforcement policy on Windows 10”.
-
- How can I install drivers that are not digitally signed? Windows 10 enforces driver signatures by default. This can be disabled to install drivers that are not digitally signed. Use the following steps to disable driver signature enforcement.
- Click the Start Start menu and select Settings.
- Click Update and Security.
- Click on Recovery.
- Click Restart now under Advanced Startup.
- Click Troubleshoot.
- Click Advanced options.
- Click Startup Settings.
- Click on Restart.
- On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.
- Your computer will restart and you will be able to install non-digitally signed drivers. If you restart your computer again the driver signature enforcement will be re-enabled.
STEVAL-FKI868V2 Board
- STMicroelectronics "STEVAL-FKI868V2" - “Sub-1GHz (860-940 MHz) transceiver development kit based on S2-LP”.
- Software.
- armKEIL "STMicroelectronics STM32L053R8" - “Device Family Pack. STMicroelectronics STM32L0 Series Device Support, Drivers and Examples”.
- STMicroelectronics "STSW-S2LP-DK. Evaluation SW package based on S2-LP" - “The STSW-S2LP-DK is an evaluation SW package based on the S2-LP high performance ultra-low power RF transceiver for RF wireless applications in the sub-1 GHz band. It is designed to operate in both the license-free ISM and SRD frequency bands at 433, 868 and 920 MHz, but can also be programmed to operate at additional frequencies in the 413-479 MHz, 452-527 MHz, 826-958 MHz, 904-1055 MHz bands”.
- STMicroelectronics "STSW-S2LP-SFX-DK. Evaluation SW package based on S2-LP" - “The STSW-S2LP-SFX-DK is an evaluation SW package for Sigfox networking with the S2-LP high performance, ultra-low power RF transceiver. It is designed to operate in the majority of radio configuration zones (RCZ) described by Sigfox”.
15. Motor Control Kits
- STMicroelectronics "STM32100B-MCKIT" - “Motor control starter kit for STM32F100 (128KB Flash) Value Line MCUs”.
- STMicroelectronics "STM3210B-MCKIT" - “Motor control starter kit for STM32 (128KB flash) Performance and Access Line microcontrollers”.
16. Boards with STM32F4 MCUs for .NET Micro Framework and .NET Gadgeteer
- See Microsoft .NET Framework 3/3, section ”.NET Micro Framework and .NET Gadgeteer”.
Appropriate OpenDirectory Directory Pages
When this document changes ! Site Navigation ( My Business ! My Topics ! Imprint / Contact ! Privacy Policy ! Keyword Index ! Google+ Author "Rolf Hemmerling" ! Google+ Publisher "hemmerling" )