Release Notes for ST MC Workbench

Copyright © 2021 STMicroelectronics
The ST Motor Control Workbench software tool provides the following features:
Supported devices and boards
Supported Devices:
- STM32F0xx Family:
STM32F030RC / STM32F030R8 / STM32F031C6 / STM32F051R8 / STM32F051C8 / STM32F072VB / STM32F072RB
- STSPIN32 Family:
STSPIN32F0601 / STSPIN32F0602 / STSPIN32F0251 / STSPIN32F0252 / STSPIN32F0B
- STM32F1xx Family:
STM32F103 High, Medium and Low Densities
- STM32F3xx Family:
STM32F302VB / STM32F302VC / STM32F302R8 / STM32F303VB / STM32F303VC / STM32F303ZE / STM32F303VE / STM32F303RE
- STM32F4xx Family:
STM32F417IG / STM32F415ZG / STM32F407IG / STM32F446ZE / STM32F446RE / STM32F401RE
- STM32F7xx Family:
STM32F746ZG / STM32F769NI
- STM32L4xx Family:
STM32L452RE / STM32L476RG
- STM32G0xx Family:
STM32G081
- STM32G4xx Family:
STM32G431CB / STM32G431RB / STM32G474QE
- STM32H7xx Family: partially supported with examples
STM32H745ZI
Control Boards
STM32F0xxFamily:
- NUCLEO-F030R8
- NUCLEO-F072RB
- STM32072B-EVAL
STM32F1xx Family :
- NUCLEO-F103RB
- STM3210E-Eval
STM32F3xx Family:
- NUCLEO-F302R8
- NUCLEO-F303RE/NUCLEO-F303RB
- STM32303E-EVAL
STM32F4xx Family:
- NUCLEO-F446RE
- NUCLEO-F401RE
- STM3240G-EVAL
- STM3241G-EVAL
- STM32446E-EVAL
- STEVAL-IHM039V1
STM32F7xx Family:
- NUCLEO-F746ZG
- STM32F769I-EVAL
STM32L4xx Family:
- NUCLEO-L452RE
- NUCLEO-L476RG
- STM32L476G-EVAL
STM32G0xx Family:
STM32G4xx Family:
- NUCLEO-G431RB
- STM32G474E-EVAL
STM32H7xx Family:
Power Boards:
- STEVAL-IHM023V3
- STEVAL-IHM025V1
- STEVAL-IHM028V2
- STEVAL-IHM045V1
- STEVAL-IPM05F
- STEVAL-IPM07F
- STEVAL-IPM08B
- STEVAL-IPM10B
- STEVAL-IPM10F
- STEVAL-IPM15B
- STEVAL-IPMNG3Q
- STEVAL-IPMNG3S
- STEVAL-IPMNG5Q
- STEVAL-IPMNG8Q
- STEVAL-IPMNM1N
- STEVAL-IPMNM2N
- STEVAL-IPMNM1S
- STEVAL-CTM009V1
- X-NUCLEO-IHM07M1
- X-NUCLEO-IHM08M1
- X-NUCLEO-IHM11M1
- X-NUCLEO-IHM16M1
Inverter Boards
- STEVAL-IHM034V2 (STM32F1)
- STEVAL-IHM042V1
- STEVAL-SPIN3201
- STEVAL-SPIN3202
- X-NUCLEO-IHM16 + NUCLEO-F303RE bundle
- STEVAL-ESC001V1
- B-G431B-ESC1
- EVSPIN32F0601S1
- EVSPIN32F0601S3
- EVSPIN32F0251S1
- EVSPIN32F0602S1
- STEVAL-HKI001V2
- STEVAL-CTM010V1
Known Limitations
The MC SDK installer, the ST Motor Profiler and the ST Motor Control Workbench software tools are running only on a PC system, and have been tested using a Windows 7 Operating System.
LCD on EVAL boards are not yet supported;
Ac6 System Workbench for STM32 (SW4STM32) toolchain is not yet supported;
F030x usage with Encoder or Hall sensor configurations are not yet supported;
During the STM32CubeMX generation, the F303x usage pops-up an error window while generation is still OK (only true with version 4.24.0, the issue disappears with version 4.25.0).
With Keil MDK-ARM toolchain, using an STM32F3 MCU, packs STM32F3xx_DFP version 2.0.0 and 2.0.1 are not supported by CubeMx. Version 1.4.0 of the pack is the last version known to work well.
The example provided for the NUCLEO-H745ZI control board now requires ST32CubeMx version 5.6.0 or later to be generated properly.
With STM32CubeMx 6.2.0:
- MC Workbench reports an error when generating projects for STM32G0xx devices with STM32CubeMx 6.2.0. This error actually is a warning from STM32CubeMx that does not prevent a correct generation of the project. Generated projects are functional.
Update History
5.4.8.21553-1.5.1.template-21-11-15 / 20-Nov-2021
Main Changes
Version 5.4.8 is a bug fix release of X-Cube-MCSDK v5.4.7. It adds support for STM32CubeMx 6.4.0.
Earlier versions of ST Motor Control SDK do not work with STM32CubeMx 6.4.0 and newer. This version of ST Motor Control SDK requires STM32CubeMx 6.2.0 or newer to work.
Note: This bug fix release of X-Cube-MCSDK still supports IARM EWARM 7.x. See the V5.4.5 release section and IAR EWARM 7.x end of support paragraph below.
It fixes also :
- the Standalone opamp mode IOC generation for G4 only and CubeMx 6.x has been fixed
- reinserted for the STM32G474E-EVAL board the pin
PC5
in OPAMP2 as inverting pin
STM32Cube Environment
- STM32CubeMX v6.4.0
- STM32Cube_FW_F0_V1.11.3
- STM32Cube_FW_F1_V1.8.4
- STM32Cube_FW_F3_V1.11.3
- STM32Cube_FW_F4_V1.26.2
- STM32Cube_FW_F7_V1.16.1
- STM32Cube_FW_G0_V1.5.0
- STM32Cube_FW_G4_V1.5.0
- STM32Cube_FW_L4_V1.17.0
- STM32Cube_FW_H7_V1.9.0
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v8.4.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2
- STM32CubeIDE v1.6.1
- STM32CubeProgrammer 2.6.0
5.4.7.21279-1.4.0.template-21-02-18 / 22-Jul-2021
Main Changes
Version 5.4.7 is a bug fix release of X-Cube-MCSDK v5.4.6. It adds support for STM32CubeMx 6.3.0.
Earlier versions of ST Motor Control SDK do not work with STM32CubeMx 6.3.0 and newer. This version of ST Motor Control SDK requires STM32CubeMx 6.2.0 or newer to work.
Note: This bug fix release of X-Cube-MCSDK still supports IARM EWARM 7.x. See the V5.4.5 release section and IAR EWARM 7.x end of support paragraph below.
STM32Cube Environment
- STM32CubeMX v6.3.0
- STM32Cube_FW_F0_V1.11.2
- STM32Cube_FW_F1_V1.8.4
- STM32Cube_FW_F3_V1.11.2
- STM32Cube_FW_F4_V1.26.1
- STM32Cube_FW_F7_V1.16.1
- STM32Cube_FW_G0_V1.5.0
- STM32Cube_FW_G4_V1.4.0
- STM32Cube_FW_L4_V1.17.0
- STM32Cube_FW_H7_V1.9.0
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2
- STM32CubeIDE v1.6.1
- STM32CubeProgrammer 2.6.0
5.4.6.21068-1.2.3.template-21-02-18 / 15-Mar-2021
Main Changes
Version 5.4.6 is a bug fix release of X-Cube-MCSDK v5.4.5.
Note: This bug fix release of X-Cube-MCSDK still supports IARM EWARM 7.x. See the 5.4.5.20506 release section and IAR EWARM 7.x end of support paragraph below
5.4.5.20506-1.2.2.template-20-11-05 / 18-Dec-2020
Main Changes
Version 5.4.4 is mainly a bug fix release of X-Cube-MCSDK v5.4.4. It also introduces a few new features.
End of support of IAR EWARM 7.x for the Web release variant. Binary libraries delivered with the Web variant of MCSDK, for the IAR EWARM toolchain, were built with IAR EWARM version 7.80 in previous releases. Starting with MCSDK 5.4.5, they are built with IAR EWARM version 8.20. MCSDK 5.4.5 still provides binary libraries built with IAR EWAM 7.80, though. See section... for more details. Note that future MCSDK releases will not provide libraries for IAR EWARM 7 anymore.
Added support for the following power boards:
- STEVAL-IPMM10B
- STEVAL-IPMM15B
- STEVAL-IPM20B
- STEVAL-IPM30B
- STEVAL-IPMnM3Q
- STEVAL-IPMnM5Q
Added support for STM32G4 Cut 2.2
Fixed issues with the default parameters used when creating projects with the following boards or kit
- STEVAL-CTM009V1 power board
- B-G431B-ESC1 inverter (over current protection)
- P-NUCLEO-IHM03 kit (ADC sampling time)
- NUCLEO-G071RB (FOC Duration error)
Updated Workbench to work with STM32CubeMx v6.0.1.
Fixed issues with setting OpAmps' external gains in Workbench
Fixed an issue with optimization level for projects generated for STM32CubeIDE
IAR EWARM 7.x end of support
This section is meaningful for the web variant of the MCSDK only. The Full variant of MCSDK is not impacted since it is not delivered with binary libraries.
Binary libraries built with version 7.x of IAR EWARM can be used to generate MCSDK projects that build with IAR EWARM 7.x and 8.x. However, when used in EWARM 8.x projects, warnings are generated due to different sizes of the wchar_t
type between EWARM 7.x and 8.x. These warnings are a source of frequent problem reports though they do not have negative consequences. In addition, EWARM 8.x has been available for a few years now. So, it is time now to definitively switch to EWARM 8.x and drop support for EWARM 7.x.
Starting with the next release of MCSDK, Web variant binary libraries will be built with EWAM 8.x. This will make it impossible to build with EWARM 7.x and older.
For the present release, Web variant binary libraries are provided both for EWARM 7.x and EWARM 8.x. However, when generating a project for IAR EWARM, only EWARM 8.x libraries are pulled in the project even if EWARM 7.x was selected in the workbench. To use the EWARM 7.x libraries the following procedure can be used:
- Remove the EWARM 8.x library from the generated project. It is located in the
MCSDK_v5.4.5/MotorControl/lib
folder in the generated project and named libmc-iar_M*.a
, with M*
the name of the Cortex M core used by the STM32 in the project. The folder contains all the libraries for all the cores and toolchains. Only one of them is actually used and its name is listed in the EWARM project. - Copy the EWARM 7.x library file needed for the project from the
Middlewares/ST/MotorControl/lib
folder found in the MCSDK installation location. In this folder, EWARM v7.x libraries are named libmc-iar7_M*.a
. - Rename the
libmc-iar7_M*.a
file into libmc-iar_M*.a
.
5.4.4.20160-1.1.0.template-20-04-17 / 19-May-2020
Main Changes
- Atollic TrueSTUDIO & SW4STM32 Deprecation. Atollic TrueSTUDIO and SW4STM32 IDEs are no longer actively developed and ST's strategy is to replace them with STM32CubeIDE. Recent STM32 series like STM32G4 devices for instance, are already not supported by all these IDEs. In a near future release of the Motor Control SDK, support for these IDE will be dropped and it will not be possible anymore to generate a project for them from the Workbench.
- In the workbench, the maximum PWM frequency can now be set as high as 500 KHz.
- Fixed an issue with NVIC configuration for IHM34V2 inverter boards
- Fixed a Workbench issue that resulted in a wrong pin assignment when creating new projects based on the NUCLEO-G431RB control board. See section Pin assignment with NUCLEO-G431RB for more details.
- Fixed an issue that resulted in incorrect overcurrent settings with some power boards. See section Over current settings correction for some power boards
- Enable users to select DAC channel 2 with STM32L452
Pin assignment with NUCLEO-G431RB
The selection of NUCLEO-G431RB in combination with any power board that require the X-NUCLEO-IHM09 adapter now results in the following settings:
Over current settings correction for some power boards
Analyzing the UM of the boards and, verifying the formula with the application team, it appears that the UMs contain typos on the suggested values for the following OCP fields:
- Comparator threshold
- Over current network gain
- Expected over-current threshold
As a consequence, values has been changes as following:
- STEVAL-IPM05F
- Comparator threshold:
0.53
--> 0.8 - Expected over-current threshold:
5.3
--> 8.0 - STEVAL-IPM07F
- Comparator threshold:
0.52
--> 0.8 - Expected over-current threshold:
6.5
--> 10.0 - STEVAL-IPM08B
- Comparator threshold:
0.52
--> 0.8 - Expected over-current threshold:
13
--> 10.0 - STEVAL-IPM10B
- STEVAL-IPM10F
- Comparator threshold:
0.52
--> 0.8 - Expected over-current threshold:
8.6667
--> 13.3333 - STEVAL-IPM15B
- Comparator threshold:
0.52
--> 0.8 - Expected over-current threshold:
13
--> 20.0 - STEVAL-IPMNG3Q
- STEVAL-IPMNG3S
- Comparator threshold:
0.53
--> 0.83 - Over current network gain:
0.1
--> 0.2 - Expected over-current threshold:
5.3
--> 4.1500 - STEVAL-IPMNG5Q
- Comparator threshold:
0.1
--> 0.83 - Expected over-current threshold:
8.3
--> 6.3846 - STEVAL-IPMNG8Q
- Comparator threshold:
1.2
--> 0.83 - Over current network gain:
0.1
--> 0.082 - Expected over-current threshold:
12
--> 10.1220 - STEVAL-IPMNM1N
- STEVAL-IPMNM1S
- Comparator threshold:
0.14
--> 0.83 - Over current network gain:
0.1
--> 0.68 - Expected over-current threshold:
1.4
--> 1.2206 - STEVAL-IPMNM2N
- STEVAL-IPMNM2N
- Comparator threshold:
0.3
--> 0.83 - Over current network gain:
0.1
--> 0.33
V5.4.3.19514-1.0.6.template-19-11-14 / 18-Nov-2019
Main Changes
- Fixed an issue with the Workbench that prevented the user from saving complex firmware examples.
Complex firmware examples are Motor Control configuration examples that consist in more than an *.stmcx file. These usually are examples that add extra code to the projects generated by the Workbench.
- Fixed incorrect HSE clock setting for STM32G431CB devices. Selecting 8 MHz as the oscillator frequency in the Workbench would actually result in HSE being set to 24 MHz. This impacts the B-G431B-ESC1 board.
- Fixed an issue the support of STM32CubeIDE for firmware examples.
- Listed the Position Control example in workbench.
Using STM32CubeIDE with the Motor Control SDK
It is now possible to generate Motor Control application projects for STM32CubeIDE. These projects come with two build configuration, Release
and Debug
.
The Release
configuration builds the application with the highest level of optimization, geared towards speed (-Ofast
) but does not provide any debug capability. This configuration is meant for production firmware.
The Debug
configuration, on the contrary, will provide the highest level of debug capability (-g3
) but no optimization (-O0
). Unfortunately, this configuration may not work out of the box with Motor Control Application:
- The absence of any optimization may result in a binary that is too large to fit in the target MCU. When this occurs, the build fails at the link step;
- Without any optimization, it is very likely that the application will emit a "FOC duration" fault immediately when the motor is started.
To be able to debug the application, the Debug
build configuration needs to be modified to add optimization. This can be done in the Project properties dialog, section C/C++ Build, selecting the Debug
configuration and selecting Optimize for Speed for the MCU GCC Compiler / Optimization item.
V5.4.2.19506-1.0.6.template-19-10-28 / 04-Nov-2019
Main Changes
Added support for the following features to configurations based on STM32G4xx devices:
Introduction of the Position Control feature for configurations using a Quadrature Encoder as speed and position feedback. See the section Using the Position Control feature below for more details.
Projects can now be generated for the STM32CubeIDE IDE.
Introduced the support of STGAP1S drives family.
Added support for the STSPIN32F0B device.
Added support for HSI on STM32G0 based Nucleo boards.
Enabling the use of the fastest available timer clock source on STM32F3 (144 MHz) and STM32G0 (128 MHz).
The following issues have been fixed:
- ADC not enabled in Single Shunt configuration with STM32F3 devices when ADC clock is set to 18 MHz
- DAC channels 1 and 2 cannot be set independently with STM32F4 configurations. If one is used for Debug the other one cannot be used to generate a voltage reference.
- Wrong ADC channel selection when ICS is used.
- STMCX files with space in file name right before the file extension prevent project generation
- TIM3 can be selected for debug in Single Shunt configurations though it is used as auxiliary timer. This leads to non functional configurations.
- Internal PGA gain parameter missing from Workbench for STM32G4xx devices.
Using the Position Control feature
The position control feature can be activated on any configuration that uses an Encoder for speed and position feedback. To activate it, open the Drive Settings dialog from the main configuration panel of the workbench, and select the Position Control item from the Control mode combo box. Dual drive configurations are also supported; the position control can then be activated on any motor equipped with an Encoder.
V5.4.1.19301.1.0.3.template-19-06-27 / 05-July-2019
Main Changes
V5.4.0.19215-1.0.2.template-19-05-15 / 27-May-2019
Main Changes
Added support for the STM32G4 family.
Added FreeRTOS support for F1, F43, F4, F7, L4 and G4 families.
Added support for negative amplifying network gains in Power stage - Current sensing.
Support arbitrary Timer peripherals for the Virtual DAC feature.
Support for the following boards has been added:
STEVAL-CTM009V1
power board configured in ICS topology in WorkbenchSTEVAL-IPMNG3S
for 3Sh and 1Sh topology in WorkbenchSTEVAL-IPMNM1S
for 3Sh and 1Sh topology in WorkbenchSTEVAL-IPMNM2S
for 3Sh and 1Sh topology in Workbench
The following issues have been fixed:
- IOC clocks frequencies definitions for G0 MCUs.
- Shunt resistor(S) value can’t be set less than 1 milliohm
- Expected over-current can’t be set more than 99.99A
- Changed the Shunt Resistor minimum value to 0.0001
Working with STM32CubeIDE for Motor Control projects
Motor Control projects generated with STM32 Motor Control Workbench fail to build. Before a solution can be developed for this issue, a work around exists that allows to use ST's new IDE with Motor Control projects by following the procedure described in this section and by respecting a few rules.
- In STM32 Motor Control Workbench, when generating or updating a project, choose either
ST SW4 STM32
or ST TrueSTUDIO
as the Target Toolchain.
Note: STM32G4 based projects cannot be generated with TrueSTUDIO
. - Open
STM32CubeIDE
, go to the File menu and select the "Open Projects from File System..." item. - In the dialog that opens, click the "Directory..." button on the "Import source" line. Navigate to the directory that contains the generated project and select it.
- The Dialog should now propose two projects for import. Select only the one that has the "Convert 'TrueSTUDIO..." or "Convert 'System Workbench..." mention in the "Import as column". The other one must not be selected.
- the imported project should build and run as expected.
It is important to follow a few rules when working with such imported projects:
- Do not edit the project's IOC file from the STM32CubeMx perspective embedded in STM32CubeIDE. A standalone version of STM32CubeMx should be used instead.
- Do not generate the sources of the project from the STM32CubeMx perspective embedded in STM32CubeIDE. A standalone version of STM32CubeMx should be used instead.
- Each time the project is (re)generated (wether from CubeMx or from MC Workbench), it needs to be imported again in STM32CubeIDE.
STM32Cube Environment
- STM32CubeMX v5.2.0
- STM32Cube_FW_F0_V1.10.0
- STM32Cube_FW_F1_V1.7.0
- STM32Cube_FW_F3_V1.10.0
- STM32Cube_FW_F4_V1.24.1
- STM32Cube_FW_F7_V1.15.0
- STM32Cube_FW_G0_V1.2.0
- STM32Cube_FW_G4_V1.0.0
- STM32Cube_FW_L4_V1.14.0
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2
- Atollic TrueSTUDIO for STM32 version 9.2.0
- ST-LINK/V2 v4.2.0
V5.3.2.18569-0.15.6.template-19-01-16 / 18-Jan-2018
Main Changes
- Fixed an issue with the building of projects generated for devices of the STM32G0 family.
- Fixed an issue that prevented the use of the DAC peripheral for some STM32F0 MCUs like the STM32F051xxx.
- Complex firmware examples are now accessible directly from Workbench.
STM32Cube Environment
- STM32CubeMX v5.0.1
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F1_V1.7.0
- STM32Cube_FW_F3_V1.10.0
- STM32Cube_FW_F4_V1.22.0
- STM32Cube_FW_F7_V1.13.0
- STM32Cube_FW_G0_V1.0.0
- STM32Cube_FW_L4_V1.13.0
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2
- Atollic TrueSTUDIO for STM32 version 9.2.0
- ST-LINK/V2 v4.2.0
V5.3.2.18569-0.15.6.template-18-12-06 / 21-Dec-2018
Main Changes
- Reintroduced some example projects that had been removed in previous version
- Fixed the incorrect configuration of HSE value with STM3240G-EVAL and STM3241G-EVAL control boards when converting projects from older Workbench versions
- Fixed pinning configuration issues when creating projects based on IHM042V1, NUCLEO-F302R8 + IHM08M1, F4 and some F3 boards.
STM32Cube Environment
- STM32CubeMX v5.0.0
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F1_V1.7.0
- STM32Cube_FW_F3_V1.10.0
- STM32Cube_FW_F4_V1.22.0
- STM32Cube_FW_F7_V1.13.0
- STM32Cube_FW_G0_V1.0.0
- STM32Cube_FW_L4_V1.13.0
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2
- Atollic TrueSTUDIO for STM32 version 9.1.0
- ST-LINK/V2 v4.2.0
V5.3.0.18528-0.15.6.template-18-12-06 / 10-Dec-2018
Main Changes
- Added support for the STM32G0 family (See Supported devices and boards above). Note that this support does not include Atollic TrueSTUDIO yet.
- The Workbench now lets the user selects the LL/HAL version to use.
STM32Cube Environment
- STM32CubeMX v5.0.0
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F1_V1.7.0
- STM32Cube_FW_F3_V1.10.0
- STM32Cube_FW_F4_V1.22.0
- STM32Cube_FW_F7_V1.13.0
- STM32Cube_FW_G0_V1.0.0
- STM32Cube_FW_L4_V1.13.0
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2
- Atollic TrueSTUDIO for STM32 version 9.1.0
- ST-LINK/V2 v4.2.0
V5.2.0.18501-0.13.2.template-18-08-02
Main Changes
- Added support for the STM32F7 family (See Supported devices and boards above)
- Added support for the STM32L4 family (See Supported devices and boards above)
- Added support for the STM32F401 device and the NUCLEO-F401RE board
- Display Firmware version used by ST MotorControl Workbench in "About" dialog of the Workbench
- Fixed an issue in workbench where the list of proposed ADC channels would not match the selected ADC peripheral for STM32F4 devices.
- Fixed an issue in workbench that only allowed for selecting TIM3 and TIM4 for Hall Sensors and Encoder handling for F4 Series. Now, TIM2 and TIM5 can also be selected.
STM32Cube Environment
- STM32CubeMX v4.25.1 / STM32CubeMX v4.26.1
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F1_V1.6.1
- STM32Cube_FW_F3_V1.10.0
- STM32Cube_FW_F4_V1.21.0
- STM32Cube_FW_F7_V1.11.0 / STM32Cube_FW_F7_V1.12.0
- STM32Cube_FW_L4_V1.11.0
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.25
- Atollic TrueSTUDIO for STM32 version 9.0.0
- ST-LINK/V2 v4.2.0
V5.1.2.18276-0.11.6.template-18-06-25 / 06-Jul-2018
This release is a bug fix release.
Main Changes
- Added support for STM32F1 based Nucleo board
- Added support for the STM32F3 based ESC inverter board
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.25
- Atollic TrueSTUDIO for STM32 version 9.0.0
- ST-LINK/V2 v4.2.0
STM32Cube Environment
- STM32CubeMX v4.25.1 / STM32CubeMX v4.26
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F1_V1.6.1
- STM32Cube_FW_F3_V1.9.0 / STM32Cube_FW_F3_V1.9.1
- STM32Cube_FW_F4_V1.19.0
V5.1.0.18254C+WB_to_Mx_0.11.5.template-18-06-05 / 07-Jun-2018
This release is a bug fix release.
Main Changes
- Fixed the handling of Low sides Idle state for all families. Setting it to a different value than that the High sides is now has the expected effect.
- Fixed the handling of the High sides Polarity and Idle state for STM32F1 and STM32F4 families. Setting them to values that differ from the defaults now has the expected effect.
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.25
- Atollic TrueSTUDIO for STM32 version 9.0.0
- ST-LINK/V2 v4.2.0
STM32Cube Environment
- STM32CubeMX v4.25.1 / STM32CubeMX v4.26
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F1_V1.6.1
- STM32Cube_FW_F3_V1.9.0 / STM32Cube_FW_F3_V1.9.1
- STM32Cube_FW_F4_V1.19.0
V5.1.0.18254C+WB_to_Mx_0.11.5.template-18-06-04 / 05-Jun-2018
Main Changes
Added support for the STM32F1 High Density series (See Supported devices and boards below);
Added support for STEVAL-SPIN devices (See Supported devices and boards below);
Added a set of power boards (See Supported devices and boards below);
Added support for Atollic® TrueSTUDIO® IDE on STM32F3 Family;
Added the possibility for the user to choose the version of STM32CubeMx to use;
Added support for IP initialization with LL libraries (except for STM32F1 family)
Bug fixes, among which:
- Restored support for IAR 7.x versions
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2.0
- Atollic TrueStudio for STM32, version 9.0.0. Note that, though the Workbench can generate TrueStudio projects, version 5.0.2 of the Motor Control Firmware does not support this toolchain.
- ST-LINK/V2 v4.2.0.
STM32CubeMX Environment
- STM32CubeMX v4.25.1
- STM32Cube_FW_F0_V1.9.0 / STM32Cube_FW_F0_V1.9.1
- STM32Cube_FW_F3_V1.9.0
- STM32Cube_FW_F4_V1.19.0
V5.0.2+WB_to_Mx_0.9.9.templates-18-03-22B / 17-Apr-2018
Main Changes
- Fixed the detection of the latest STM32CubeMx versions by ST Motor Control Workbench
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4 and v8.20.2.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2.0
- Atollic TrueStudio for STM32, version 9.0.0. Note that, though the Workbench can generate TrueStudio projects, version 5.0.2 of the Motor Control Firmware does not support this toolchain.
- ST-LINK/V2 v4.2.0.
STM32CubeMX Environment
- STM32CubeMX v4.25.0
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F3_V1.9.0
- STM32Cube_FW_F4_V1.19.0
V5.0.2 / 04-Apr-2018
Main Changes
- Version 5.0.2, bug fix release of ST Motor Control Workbench v5.0
- Support for several, parallel versions of the Motor Control SDK (See below)
- Access to the documentation from the GUI.
- Removal of projects targeting obsolete boards.
Parallel Motor Control SDKversions support
Several versions of the Motor Control SDK can be installed in parallel on the same PC.Version 5.0.1 of the Motor Control Workbench would install the Motor Control Firmware in the user’s STM32Cube repository in the MotorControl
folder (typically in C:\Users\<username>\STM32Cube\Repository\MotorControl
). With version 5.0.2 onwards, the firmware is installed in the MCSDK_vX.Y.Z\MotorControl
subfolder of the user’s STM32Cube repository where X.Y.Z
is the version of the SDK (for instance C:\Users\JohnDoe\STM32Cube\Repository\MCSDK_v5.0.2\MotorControl
). This allows for keeping several versions of the SDK and so to keep on working on application projects developed with different versions of the SDK.
The version of the SDK used on a given project is that of the Motor Control Workbench used to generate that project. Put in other words, Motor Control Workbench generates projects for the SDK version it is delivered with.
The version of the SDK to use is not stated in the .stmcx
file. It is in the .ioc
file generated by the workbench. So, when a project has been generated with a given version of the workbench is sticks to it. Unless it is generated again or updated with another version of the Workbench. In that latter case, it is recommended to erase the MCSDK_vX.Y.Z
folder from the previous version…
V5.0.1 / 08-Mar-2018
Main Changes
- First release of the ST Motor Control Workbench v5.0.
Development Toolchains
- IAR Embedded Workbench for ARM (IAR Systems AB) v7.80.4.
- μVision® IDE for Arm® (Keil® MDK) v5.24.2.0
- ST-LINK/V2 v4.2.0
STM32CubeMX Environment
- STM32CubeMX v4.25.0
- STM32Cube_FW_F0_V1.9.0
- STM32Cube_FW_F3_V1.9.0
- STM32Cube_FW_F4_V1.19.0
License
This software package is licensed by ST under ST license SLA0048, the "License"; You may not use this package except in compliance with the License. You may obtain a copy of the License at: