This code example shows how to configure low-voltage detection (LVD) in MCU to monitor VDDD and generate an interrupt when VDDD drops below the configured threshold.
Provide feedback on this code example.
- ModusToolbox™ v3.6 or later (tested with v3.6)
- Board support package (BSP) minimum required version: 3.0.0
- Programming language: C
- Associated parts: TRAVEO™ T2G family Cluster series, XMC5000 MCUs and TRAVEO™ T2G family body high CYT4BF series
- GNU Arm® Embedded Compiler v14.2.1 (
GCC_ARM) – Default value ofTOOLCHAIN - Arm® Compiler v6.22 (
ARM) - IAR C/C++ Compiler v9.50.2 (
IAR)
- TRAVEO™ T2G Cluster 6M Lite Kit (
KIT_T2G_C-2D-6M_LITE)– Default value ofTARGET - TRAVEO™ T2G Cluster 4M Lite Kit (
KIT_T2G_C-2D-4M_LITE) - TRAVEO™ T2G Body high Lite Kit (
KIT_T2G-B-H_LITE) - TRAVEO™ T2G Body high Evaluation Kit (
KIT_T2G-B-H_EVK) - XMC5200 Evaluation Kit (
KIT_XMC52_EVK)
This example needs a power supply to power VDDD of the kit listed in the Supported kits section. Remove the VDDD power jumper in the board and power external VDDD through pin listed in the following table. Default external VDDD is 3.3 V.
Table 1. Connection jumper pin for external power supply
| Board | Jumper pin | Note |
|---|---|---|
| KIT_T2G_C-2D-6M_LITE, KIT_T2G_C-2D-4M_LITE | X101, Pin2 | - |
| KIT_T2G-B-H_LITE | J20, Pin2 | - |
| KIT_T2G-B-H_EVK | J15, Pin1 | The J10 jumper need to be connected to the 2-3 pin side for 3.3V operation. |
| KIT_XMC52_EVK | J4, Pin2 | - |
Except the above mentioned, uses the board's default configuration. See the kit user guide to ensure that the board is configured correctly.
See the ModusToolbox™ tools package installation guide for information about installing and configuring the tools package.
This example requires no additional software or tools.
The ModusToolbox™ tools package provides the Project Creator as both a GUI tool and a command line tool.
Use Project Creator GUI
-
Open the Project Creator GUI tool
There are several ways to do this, including launching it from the dashboard or from inside the Eclipse IDE. For more details, see the Project Creator user guide (locally available at {ModusToolbox™ install directory}/tools_{version}/project-creator/docs/project-creator.pdf)
-
On the Choose Board Support Package (BSP) page, select a kit supported by this code example. See Supported kits
Note: To use this code example for a kit not listed here, you may need to update the source files. If the kit does not have the required resources, the application may not work
-
On the Select Application page:
a. Select the Applications(s) Root Path and the Target IDE
Note: Depending on how you open the Project Creator tool, these fields may be pre-selected for you
b. Select this code example from the list by enabling its check box
Note: You can narrow the list of displayed examples by typing in the filter box
c. (Optional) Change the suggested New Application Name and New BSP Name
d. Click Create to complete the application creation process
Use Project Creator CLI
The 'project-creator-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™ install directory}/tools_{version}/project-creator/ directory.
Use a CLI terminal to invoke the 'project-creator-cli' tool. On Windows, use the command-line 'modus-shell' program provided in the ModusToolbox™ installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ tools. You can access it by typing "modus-shell" in the search box in the Windows menu. In Linux and macOS, you can use any terminal application.
The following example clones the "mtb-example-ce240765-lvd-interrupt" application with the desired name "LvdInterrupt" configured for the KIT_T2G_C-2D-6M_LITE BSP into the specified working directory, C:/mtb_projects:
project-creator-cli --board-id KIT_T2G_C-2D-6M_LITE --app-id mtb-example-ce240765-lvd-interrupt --user-app-name LvdInterrupt --target-dir "C:/mtb_projects"
The 'project-creator-cli' tool has the following arguments:
| Argument | Description | Required/optional |
|---|---|---|
--board-id |
Defined in the field of the BSP manifest | Required |
--app-id |
Defined in the 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 |
Note: The project-creator-cli tool uses the
git cloneandmake getlibscommands to fetch the repository and import the required libraries. For details, see the "Project creator tools" section of the ModusToolbox™ tools package user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).
After the project has been created, you can open it in your preferred development environment.
Eclipse IDE
If you opened the Project Creator tool from the included Eclipse IDE, the project will open in Eclipse automatically.
For more details, see the Eclipse IDE for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_ide_user_guide.pdf).
Visual Studio (VS) Code
Launch VS Code manually, and then open the generated {project-name}.code-workspace file located in the project directory.
For more details, see the Visual Studio Code for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_vscode_user_guide.pdf).
Arm® Keil® µVision®
Double-click the generated {project-name}.cprj file to launch the Keil® µVision® IDE.
For more details, see the Arm® Keil® µVision® for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_uvision_user_guide.pdf).
IAR Embedded Workbench
Open IAR Embedded Workbench manually, and create a new project. Then select the generated {project-name}.ipcf file located in the project directory.
For more details, see the IAR Embedded Workbench for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_iar_user_guide.pdf).
Command line
If you prefer to use the CLI, open the appropriate terminal, and navigate to the project directory. On Windows, use the command-line 'modus-shell' program; on Linux and macOS, you can use any terminal application. From there, you can run various make commands.
For more details, see the ModusToolbox™ tools package user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).
-
Connect the board to your PC using the provided USB cable through the KitProg3 USB connector.
-
Power VDDD with 3.3 V from an external power supply.
-
Program the board using one of the following:
Using Eclipse IDE
-
Select the application project in the Project Explorer.
-
In the Quick Panel, scroll down, and click <Application Name> Program (KitProg3_MiniProg4).
In other IDEs
Follow the instructions in your preferred IDE.
Using CLI
From the terminal, execute the
make programcommand to build and program the application using the default toolchain to the default target. The default toolchain is specified in the application's Makefile but you can override this value manually:make program TOOLCHAIN=<toolchain>Example:
make program TOOLCHAIN=GCC_ARM -
-
After successful programming, the application starts automatically. Confirm that the LED1 is blinking at 20 Hz.
-
Drop external VDDD from 3.3 V below 2.8 V and observe that the LED2 blinks five times.
You can debug the example to step through the code.
In Eclipse IDE
Use the <Application Name> Debug (KitProg3_MiniProg4) configuration in the Quick Panel. For details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ user guide.
In other IDEs
Follow the instructions in your preferred IDE.
The following table lists the resources used in this example and their purpose.
Table 2. Application resources
| Resource | Alias/object | Purpose |
|---|---|---|
| LVD1 | CY_LVD_HT_SELECT_LVD_1 | Monitor VDDD |
| GPIO (LED1) | CYBSP_USER_LED1 | Example normal running |
| GPIO (LED2) | CYBSP_USER_LED2 | LVD interrupt warning |
| Resources | Links |
|---|---|
| Application notes | AN235305 – Getting started with TRAVEO™ T2G family MCUs in ModusToolbox&trade AN220193 – GPIO usage setup in TRAVEO™ T2G family AN220222 - Low-power mode procedure in TRAVEO T2G family; AN241720 – Getting started with XMC5000 MCU on ModusToolbox™ software |
| Code examples | Using ModusToolbox™ on GitHub |
| Device documentation | TRAVEO™ T2G body high family MCUs datasheets TRAVEO™ T2G body high family MCUs architecture/registers reference manuals TRAVEO™ T2G cluster family MCUs datasheets for CYT4DN TRAVEO™ T2G cluster family MCUs architecture/registers reference manuals for CYT4DN TRAVEO™ T2G cluster family MCUs datasheets for CYT3DL TRAVEO™ T2G cluster family MCUs architecture/registers reference manuals for CYT3DL XMC5000 MCUs documents |
| Development kits | Select your kits from the Evaluation board finder. |
| Libraries on GitHub | mtb-pdl-cat1 – Peripheral Driver Library (PDL) |
Tools |
ModusToolbox™ – ModusToolbox™ software is a collection of easy-to-use libraries and tools enabling rapid development with Infineon MCUs for applications ranging from wireless and cloud-connected systems, edge AI/ML, embedded sense and control, to wired USB connectivity using PSoC™ Industrial/IoT MCUs, AIROC™ Wi-Fi and Bluetooth® connectivity devices, XMC™ Industrial MCUs, and EZ-USB™/EZ-PD™ wired connectivity controllers. ModusToolbox™ incorporates a comprehensive set of BSPs, HAL, libraries, configuration tools, and provides support for industry-standard IDEs to fast-track your embedded application development. |
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.
Document title: CE240765 – PDL: LVD interrupt
| Version | Description of change |
|---|---|
| 1.0.0 | New code example |
| 1.1.0 | Added support for KIT_XMC52_EVK, KIT_T2G_C-2D-4M_LITE, KIT_T2G-B-H_EVK and KIT_T2G-B-H_LITE and updated to support ModusToolbox™ v3.6 |
All referenced product or service names and trademarks are the property of their respective owners.
The Bluetooth® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc., and any use of such marks by Infineon is under license.
PSOC™, formerly known as PSoC™, is a trademark of Infineon Technologies. Any references to PSoC™ in this document or others shall be deemed to refer to PSOC™.
(c) 2024-2026, Infineon Technologies AG, or an affiliate of Infineon Technologies AG. All rights reserved.
This software, associated documentation and materials ("Software") is owned by Infineon Technologies AG or one of its affiliates ("Infineon") and is protected by and subject to worldwide patent protection, worldwide copyright laws, and international treaty provisions. Therefore, you may use this Software only as provided in the license agreement accompanying the software package from which you obtained this Software. If no license agreement applies, then any use, reproduction, modification, translation, or compilation of this Software is prohibited without the express written permission of Infineon.
Disclaimer: UNLESS OTHERWISE EXPRESSLY AGREED WITH INFINEON, THIS SOFTWARE IS PROVIDED AS-IS, WITH NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ALL WARRANTIES OF NON-INFRINGEMENT OF THIRD-PARTY RIGHTS AND IMPLIED WARRANTIES SUCH AS WARRANTIES OF FITNESS FOR A SPECIFIC USE/PURPOSE OR MERCHANTABILITY. Infineon reserves the right to make changes to the Software without notice. You are responsible for properly designing, programming, and testing the functionality and safety of your intended application of the Software, as well as complying with any legal requirements related to its use. Infineon does not guarantee that the Software will be free from intrusion, data theft or loss, or other breaches (“Security Breaches”), and Infineon shall have no liability arising out of any Security Breaches. Unless otherwise explicitly approved by Infineon, the Software may not be used in any application where a failure of the Product or any consequences of the use thereof can reasonably be expected to result in personal injury.