Disclaimer: This is a community code example (CCE) released for the benefit of the community users. These projects have only been tested for the listed BSPs, tools versions, and toolchains documented in this readme. They are intended to demonstrate how a solution / concept / use-case can be achieved on a particular device. For official code examples, please click here.
This community code example (CCE) demonstrates sensorless three-phase BLDC motor control application using XMC1300 Boot Kit. In order to test this software, XMC1000 Motor Control Application Kit is needed.
- ModusToolbox™ software v3.1 or later (tested with v3.1)
- SEGGER J-Link software v7.90a
- Programming language: C
- Associated parts: XMC1300 MCU
- GNU Arm® embedded compiler v11.3 (
GCC_ARM) - Default value ofTOOLCHAIN
- XMC1300 Boot Kit (
KIT_XMC13_BOOT_001)
Before using this code example, make sure that the XMC1300 board is correctly connected to the PMSM Low Voltage 15W Motor Card which also needs to be supplied by an external DC power supply (12V to 24V) from its power jack. Please see this User Manual for more details. A complete hardware setup example can be seen in Figure 1 below.
Figure 1. Complete hardware setup example with XMC1000 Motor Application Kit
Note: Make sure that the SWCLK is on before using the debugger as shown in Figure 2.
Figure 2. SWCLK switch is on for the debugger
This code example uses Micro Inspector Pro application by default to run and control the motor from a GUI. Click here to download the application.
Please follow the steps below to control the motor from the Micro Inspector Pro application.
Create the project and open it using one of the following:
In Eclipse IDE for ModusToolbox™ software (recommended)
-
Click the New Application link in the Quick Panel (or, use File > New > ModusToolbox™ Application). This launches the Project Creator tool.
-
Select the kit
KIT_XMC13_BOOT_001from the XMC™ BSPs list shown in the Project Creator - Choose Board Support Package (BSP) dialog. -
In the Project Creator - Select Application dialog, choose the example from the list Community Code Examples by enabling the checkbox.
-
(Optional) Change the suggested New Application Name.
-
The Application(s) Root Path defaults to the Eclipse workspace which is usually the desired location for the application. If you want to store the application in a different location, you can change the Application(s) Root Path value. Applications that share libraries should be in the same root path.
-
Click Create to complete the application creation process.
-
To build the project, click Build Application from the Quick Panel.
-
To start the debugging session to run the motor, click Generate Launches for "YourApplicationName" in Quick Panel. Then click to YourApplicationName Debug (Jlink). A debugging window will appear and the session will automatically pause in a breakpoint. Click Resume button from the above toolbar to continue the session.
-
While the debugging session is running, open the Micro Inspector Pro application. Click Open Workspace button from the upper left corner.
Figure 3. Opening the workspace folder in Micro Inspector Pro
- Find the "BLDC_SCALAR_SL_XMC13_uCProbe.wspx" file from your ModusToolbox workspace folder and select Open. A pop-up window will appear to show the existing elf file. Select the one shown and click Open.
Figure 4. Selecting the elf file
- To run and control the motor speed from the GUI, switch to BLDC: Speed Control mode and click Run button.
Note: If you face any issues or errors with Micro Inspector GUI while the kit is in debug mode, please reset the GUI while the debug session is on and restart from step 9.
Figure 5. Switching to running mode
- Press Motor Start to run the motor. You can also adjust the motor speed by changing the value under Setting Target Speed.
Figure 6. Motor control part of the running mode
- Right click the Oscilloscope tab and select New Vertical Tab Group in order to observe your parameters from the oscilloscope on the right side while observing the motor control parameters on the left side simultaneously.
Figure 7. BLDC Motor parameters observed from the oscilloscope
Note: This code does not use the Device Configurator in ModusToolbox. All peripheral definitions and initializations are directly integrated within the software using low level drivers by calling the necessary libraries. When the user wants to change a configuration variable or parameter, it should be done within the code in the user config header files rather than in the Device Configurator.
Figure 8. Device Configurator in ModusToolbox
For more details, see the Eclipse IDE for ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/ide_{version}/docs/mtb_ide_user_guide.pdf).
In command-line interface (CLI)
ModusToolbox™ software provides the Project Creator as both a GUI tool and the command line tool, "project-creator-cli". The CLI tool can be used to create applications from a CLI terminal or from within batch files or shell scripts. This tool is available in the {ModusToolbox™ software install directory}/tools_{version}/project-creator/ directory.
Alternatively, you can manually create the application using the following steps:
-
Download and unzip this repository onto your local machine, or clone the repository.
-
Use a CLI terminal to invoke the "project-creator-cli" tool. On Windows, use the command line "modus-shell" program provided in the ModusToolbox™ software installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ software tools. You can access it by typing
modus-shellin the search box in the Windows menu. In Linux and macOS, you can use any terminal application.
The "project-creator-cli" tool has the following arguments:
| Argument | Description | Required/optional |
|---|---|---|
--board-id |
Defined in the <id> field of the BSP manifest |
Required |
--app-id |
Defined in the <id> field of the CE manifest |
Required |
--target-dir |
Specify the directory in which the application is to be created if you prefer not to use the default current working directory | Optional |
--user-app-name |
Specify the name of the application if you prefer to have a name other than the example's default name | Optional |
The following example clones the "BLDC Scalar SL XMC13" application with the desired name "cce-mtb-xmc-bldc-scalar-sl" configured for the KIT_XMC13_BOOT_001 BSP into the specified working directory, C:/mtb_projects:
project-creator-cli --board-id KIT_XMC13_BOOT_001 --app-id cce-mtb-xmc-bldc-scalar-sl --user-app-name cce-mtb-xmc-bldc-scalar-sl --target-dir "C:/mtb_projects"
Note: The cloned application contains a default BSP file (TARGET_xxx.mtb) in the bsps folder. Use the Library Manager (make modlibs command) to select or add a different BSP file, if required. If the selected kit does not have the required resources or is not supported, the application may not work.
- Import the required libraries by executing the
make getlibscommand.
Various CLI tools include a -h option that prints help information to the terminal screen about that tool. For more details, see the ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mtb_user_guide.pdf).
In third-party IDEs
Note: Only VS Code is supported.
-
Follow the instructions from the In command-line interface (CLI) section to create the application, and import the libraries using the
make getlibscommand. -
Export the application to a supported IDE using the
make <ide>command.For a list of supported IDEs and more details, see the "Exporting to IDEs" section of the ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mtb_user_guide.pdf).
-
Follow the instructions displayed in the terminal to create or import the application as an IDE project.
| Resources | Links |
|---|---|
| Code examples | Using ModusToolbox™ software on GitHub |
| Kit guide | XMC1300 boot kit – Board user‘s manuals. Describes the schematic and hardware of XMC1300 board. |
| Device documentation | XMC1000 family datasheets XMC1000 family technical reference manuals |
| Development kits | Buy at www.infineon.com KIT_XMC13_BOOT_001 – Boot kit XMC1300 KIT_XMC1X_AK_MOTOR_001 – XMC1000 Motor Control Application Kit |
| Libraries on GitHub | mtb-xmclib-cat3 – XMC™ peripheral driver library (XMCLib) and docs |
| Tools | Eclipse IDE for ModusToolbox™ software – ModusToolbox™ software is a collection of easy-to-use software and tools enabling rapid development with Infineon MCUs, covering applications from embedded sense and control to wireless and cloud-connected systems. |
Infineon provides a wealth of data at www.infineon.com to help you select the right device, and quickly and effectively integrate it into your design.
For XMC™ MCU devices, see 32-bit XMC™ Industrial microcontroller based on Arm® Cortex®-M.
Document title: CCE#002-38984 - BLDC SCALAR Sensorless XMC13
| Version | Description of change |
|---|---|
| 1.0.0 | New community code example |
All other trademarks or registered trademarks referenced herein are the property of their respective owners.
© 2023 Infineon Technologies AG
All Rights Reserved.
The information given in this document shall in no event be regarded as a guarantee of conditions or characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any information regarding the application of the device, Infineon Technologies hereby disclaims any and all warranties and liabilities of any kind, including without limitation, warranties of non-infringement of intellectual property rights of any third party.
For further information on technology, delivery terms and conditions and prices, please contact the nearest Infineon Technologies Office (www.infineon.com).
Due to technical requirements, components may contain dangerous substances. For information on the types in question, please contact the nearest Infineon Technologies Office.
Infineon Technologies components may be used in life-support devices or systems only with the express written approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system or to affect the safety or effectiveness of that device or system. Life support devices or systems are intended to be implanted in the human body or to support and/or maintain and sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other persons may be endangered.