EZ-PD™ PMG1 MCU: Multiple GPIO interrupts

This code example demonstrates a method to detect multiple GPIO interrupts on the same port of EZ-PD™ PMG1 MCU devices. Detect multiple GPIO interrupts from the same port using the pin status bits of a port.

View this README on GitHub.

Provide feedback on this code example.

Requirements

• ModusToolbox™ software v3.0 or later (tested with v3.0)
• Board support package (BSP) minimum required version: 3.0.0
• Programming language: C
• Associated parts: All EZ-PD™ PMG1 MCU parts

Supported toolchains (make variable 'TOOLCHAIN')

• GNU Arm® Embedded Compiler v10.3.1 (GCC_ARM) - Default value of TOOLCHAIN
• Arm® Compiler v6.16 (ARM)
• IAR C/C++ Compiler v9.30.1 (IAR)

Supported kits (make variable 'TARGET')

• EZ-PD™ PMG1-S0 Prototyping Kit (PMG1-CY7110) - Default value of TARGET
• EZ-PD™ PMG1-S1 Prototyping Kit (PMG1-CY7111)
• EZ-PD™ PMG1-S2 Prototyping Kit (PMG1-CY7112)
• EZ-PD™ PMG1-S3 Prototyping Kit (PMG1-CY7113)

Hardware setup

1. See the kit user guide to ensure that the board is configured correctly.

2. Make a connection between the PIN_0 and PIN_1 pin listed in Table 1 for each of the EZ-PD™ PMG1 devices.

Table 1. GPIO pin connections

PMG1 Prototyping kit 0	PIN_0 & user switch	PIN_1
PMG1-CY7110	J7.8(P2.0)	J7.6(P2.3)
PMG1-CY7111	J7.13(P2.0)	J7.15(P2.2)
PMG1-CY7112	J7.15(P1.2)	J7.12(P1.5)
PMG1-CY7113	J6.11(P3.3)	J6.12(P3.0)

3. If the DEBUG_PRINT macro is enabled in the application, a debug UART connection is supported in the firmware. To view the UART messages connect the UART Tx and UART Rx lines from the PMG1 kit to J3.8 and J3.10 on KitProg3 respectively. This establishes a UART connection between KitProg3 and the PMG1 device for the revisions of the PMG1 Prototyping kits listed in Table 2.

Table 2. PMG1 kit UART connection

PMG1 Prototyping kit	UART Tx	UART Rx
PMG1-CY7110 (revision 3 or lower)	J6.10 to J3.8	J6.9 to J3.10
PMG1-CY7111 (revision 2 or lower)	J6.10 to J3.8	J6.9 to J3.10
PMG1-CY7112 (revision 2 or lower)	J6.10 to J3.8	J6.9 to J3.10
PMG1-CY7113 (revision 3 or lower)	J6.10 to J3.8	J6.9 to J3.10

Note: All protoyping kits with a higher revision have UART pins internally connected. Therefore, external wiring is not required. Review compile-time configuration for more information on MACRO DEBUG_PRINT.

Software setup

Install a terminal emulator to display the serial data. Instructions in this document use Tera Term.

Note: If the DEBUG_PRINT macro is enabled, Tera Term is used to view UART print messages.

Using the code example

Create the project and open it using one of the following:

In Eclipse IDE for ModusToolbox™

1. Click the New Application link in the Quick Panel (or, use File > New > ModusToolbox™ Application). This launches the Project Creator tool.

2. Pick a kit supported by the code example from the list shown in the Project Creator - Choose Board Support Package (BSP) dialog.

   When you select a supported kit, the example is reconfigured automatically to work with the kit. To work with a different supported kit later, use the Library Manager to choose the BSP for the supported kit. You can use the Library Manager to select or update the BSP and firmware libraries used in this application. To access the Library Manager, click the link from the Quick Panel.

   You can also just start the application creation process again and select a different kit.

   If you want to use the application 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.

3. In the Project Creator - Select Application dialog, choose the example by enabling the checkbox.

4. (Optional) Change the suggested New Application Name.

5. 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 must be in the same root path.

6. Click Create to complete the application creation process.

For more details, see the Eclipse IDE for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/ide_{version}/docs/mt_ide_user_guide.pdf).

In command-line interface (CLI)

ModusToolbox™ 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™ 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 "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 "Multiple GPIO Interrupts" application with the desired name "multiple_gpio_interrupts" configured for the PMG1-CY7110 BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id PMG1-CY7110 --app-id mtb-example-pmg1-multiple-gpio-interrupts --user-app-name multiple_gpio_interrupts --target-dir "C:/mtb_projects"

Note: The project-creator-cli tool uses the git clone and make getlibs commands to fetch the repository and import the required libraries. For details, see the "Project creator tools" section of the ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).

To work with a different supported kit later, use the Library Manager to choose the BSP for the supported kit. You can invoke the Library Manager GUI tool from the terminal using make library-manager command or use the Library Manager CLI tool (library-manager-cli) to change the BSP.

The "library-manager-cli" tool has the following arguments:

Argument	Description	Required/optional
--add-bsp-name	Name of the BSP that should be added to the application	Required
--set-active-bsp	Name of the BSP that should be as active BSP for the application	Required
--add-bsp-version	Specify the version of the BSP that should be added to the application if you do not wish to use the latest from manifest	Optional
--add-bsp-location	Specify the location of the BSP (local/shared) if you prefer to add the BSP in a shared path	Optional

The following example adds the PMG1-CY7110 BSP to the already created application and makes it the active BSP for the app:

~/ModusToolbox/tools_3.0/library-manager/library-manager-cli --project "C:/mtb_projects/MyMultipleGPIOInterrupts" --add-bsp-name PMG1-CY7110 --add-bsp-version "latest-v3.X" --add-bsp-location "local"

~/ModusToolbox/tools_3.0/library-manager/library-manager-cli --project "C:/mtb_projects/MyMultipleGPIOInterrupts" --set-active-bsp APP_PMG1-CY7110

In third-party IDEs

Use one of the following options:

• Use the standalone Project Creator tool:

  1. Launch Project Creator from the Windows Start menu or from {ModusToolbox™ install directory}/tools_{version}/project-creator/project-creator.exe.

  2. In the initial Choose Board Support Package screen, select the BSP, and click Next.

  3. In the Select Application screen, select the appropriate IDE from the Target IDE drop-down menu.

  4. Click Create and follow the instructions printed in the bottom pane to import or open the exported project in the respective IDE.

• Use command-line interface (CLI):

  1. Follow the instructions from the In command-line interface (CLI) section to create the application, and then import the libraries using the make getlibs command.

  2. Export the application to a supported IDE using the make <ide> command.

  3. Follow the instructions displayed in the terminal to create or import the application as an IDE project.

For a list of supported IDEs and more details, see the "Exporting to IDEs" section of the ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).

Operation

1. Ensure that the steps listed in the Hardware setup section are completed.

2. Ensure that the jumper shunt on power selection jumper (J5) is placed at position 2-3(programming mode) to enable programming.

3. Connect the board to the PC using the USB cable through the KitProg3 USB connector(J1). This cable is used for programming the PMG1 device and as a USB-UART bridge to the PC during operation.

4. Program the board using one of the following:

   Using Eclipse IDE for ModusToolbox™

   1. Select the application project in the Project Explorer.

   2. In the Quick Panel, scroll down, and click <Application Name> Program (KitProg3_MiniProg4).

   Using CLI

   From the terminal, execute the make program command 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
   

5. After programming the kit, disconnect the USB cable and change the position on power selection jumper (J5) to 1-2 to power the kit through the USBPD port.

6. If the DEBUG_PRINT macro is enabled, to see the UART messages, connect the USB cable back to the KitProg3 USB connector and open a terminal program. Select the KitProg3 COM port. Set the serial port parameters to 8N1 and 115200 baud.

7. Power the kit through the USB PD port (J10) using a second USB cable.

8. The application starts automatically. If debug print is enabled, confirm that "PMG1 MCU: Multiple GPIO interrupts" is displayed on the UART terminal as shown in Figure 1.

   Figure 1. "PMG1 MCU: Multiple GPIO Interrupts" in terminal output

   

9. Confirm that the kit user LED is OFF.

10. Press the kit USER SWITCH once to trigger both the PIN_0 interrupt and PIN_1 interrupt.

11. Confirm that the kit USER LED blinks twice. If debug print is enabled, confirm that "PIN_0 interrupt(falling edge) detected." and "PIN_1 interrupt(falling edge) detected." is displayed on the UART terminal as shown in Figure 2.

    Figure 2. "PIN_0 and PIN_1 interrupt detected" in terminal output

    

12. Alternatively, press and hold the user switch to trigger the PIN_0 interrupt and confirm that the kit user LED blinks once. Release the kit user switch to trigger the PIN_1 interrupt and confirm that the kit user LED blinks once.

Debugging

You can debug the example to step through the code. In the IDE, use the <Application Name> Debug (KitProg3_MiniProg4) configuration in the Quick Panel. Ensure that the board is connected to your PC using the USB cable through the KitProg3 USB connector and the jumper shunt on power selection jumper (J5) is placed at position 1-2. See the "Debug mode" section in the kit user guide for debugging the application on CY7110 prototyping kit. For more details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ user guide.

Design and implementation

On PMG1 devices, each GPIO pin of a port can be configured to generate an interrupt on the rising edge, falling edge, or both edges.

Multiple GPIO interrupts from the same port can be detected by using the pin status bits of a port.

When a GPIO interrupt is triggered by a signal on an interrupt-enabled port pin, the Port Interrupt Status Register is updated. The firmware can read this register to determine which GPIO triggered the interrupt. Firmware can then clear the interrupt request (IRQ) bit by writing a ‘1’ to its corresponding bit.

In this application two GPIOs, PIN_0 and PIN_1, from the same port are configured as inputs with a falling edge interrupt and a rising edge interrupt, respectively.

PIN_0 is the kit user switch configured as a resistive pull-up pin with an initial state of High(1) and PIN_1 is a kit header pin configured as a resistive pull-up pin with an initial state of High(1).

Following the hardware connections in Table 1, PIN_0 and PIN_1 are at High(1) states when the PMG1 device is powered.

When the USER SWITCH is pressed PIN_0 and PIN_1 are driven to a Low(0) state.

• The falling edge event triggers the PIN_0 interrupt, which sends out a port interrupt request (PIRQ) signal.
• The interrupt service routine (ISR) for the GPIO port sets the PIN_0 interrupt flag.

When the user switch is released, PIN_0 and PIN_1 are driven back to a High(1) state.

• The rising edge event triggers the PIN_1 interrupt, which sends out a PIRQ signal.
• The ISR for the GPIO port sets the PIN_1 interrupt flag.

The firmware actively checks whether any of the interrupt flags have been set by the GPIO port ISR.

If an interrupt flag has been set by the ISR, the firmware clears the corresponding flag and blinks the LED once.

Therefore, when the kit user switch is pressed once, the user LED will blink twice. The first blink caused by the PIN 0 interrupt and the second blink caused by the PIN_1 interrupt.

Figure 3. Multiple GPIO interrupts firmware flowchart

Compile-time configurations

The code example functionality can be customized through a set of compile-time parameters that can be turned ON/OFF in the main.c file.

Macro name	Description	Allowed values
DEBUG_PRINT	Debug print macro to enable UART print	1u or 0u

The 'CY_DEVICE_SERIES_PMG1Sx' macro is automatically set by ModusToolbox when the PMG1-Sx device is selected.

Resources and settings

Table 3. Application resources

Resource	Alias/object	Purpose
GPIO Pin (BSP), SWITCH (BSP)	CYBSP_PIN_0, _CYBSP_USER_SW	PIN 0 with a Falling Edge interrupt
GPIO Pin (BSP)	CYBSP_PIN_1	PIN_1 with a Rising Edge interrupt
UART (BSP)	CYBSP_UART	UART object used to send Debug messages via terminal
LED (BSP)	CYBSP_USER_LED	User LED to show the output

The application uses a UART to print messages in a UART terminal emulator when Debug Print is enabled. The application uses the USER LED to indicate a GPIO interrupt event.

Related resources

Resources	Links
Application notes	AN232553 – Getting started with EZ-PD™ PMG1 MCU on ModusToolbox™ AN232565 – EZ-PD™ PMG1 hardware design guidelines and checklist
Code examples	Using ModusToolbox™ on GitHub
Device documentation	EZ-PD™ PMG1 MCU datasheets
Development kits	Select your kits from the Evaluation board finder page.
Libraries on GitHub	mtb-pdl-cat2 – Peripheral Driver Library (PDL) and documents
Tools	Eclipse IDE for ModusToolbox™ ModusToolbox™ 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 using AIROC™ Wi-Fi & Bluetooth® combo devices.

Other resources

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 history

Document Title: CE237319 – EZ-PD™ PMG1 MCU: Multiple GPIO interrupts

Version	Description of change
1.0.0	New code example

---

© Cypress Semiconductor Corporation, 2023. This document is the property of Cypress Semiconductor Corporation, an Infineon Technologies company, and its affiliates ("Cypress"). This document, including any software or firmware included or referenced in this document ("Software"), is owned by Cypress under the intellectual property laws and treaties of the United States and other countries worldwide. Cypress reserves all rights under such laws and treaties and does not, except as specifically stated in this paragraph, grant any license under its patents, copyrights, trademarks, or other intellectual property rights. If the Software is not accompanied by a license agreement and you do not otherwise have a written agreement with Cypress governing the use of the Software, then Cypress hereby grants you a personal, non-exclusive, nontransferable license (without the right to sublicense) (1) under its copyright rights in the Software (a) for Software provided in source code form, to modify and reproduce the Software solely for use with Cypress hardware products, only internally within your organization, and (b) to distribute the Software in binary code form externally to end users (either directly or indirectly through resellers and distributors), solely for use on Cypress hardware product units, and (2) under those claims of Cypress’s patents that are infringed by the Software (as provided by Cypress, unmodified) to make, use, distribute, and import the Software solely for use with Cypress hardware products. Any other use, reproduction, modification, translation, or compilation of the Software is prohibited.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS DOCUMENT OR ANY SOFTWARE OR ACCOMPANYING HARDWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. No computing device can be absolutely secure. Therefore, despite security measures implemented in Cypress hardware or software products, Cypress shall have no liability arising out of any security breach, such as unauthorized access to or use of a Cypress product. CYPRESS DOES NOT REPRESENT, WARRANT, OR GUARANTEE THAT CYPRESS PRODUCTS, OR SYSTEMS CREATED USING CYPRESS PRODUCTS, WILL BE FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE, HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (collectively, "Security Breach"). Cypress disclaims any liability relating to any Security Breach, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any Security Breach. In addition, the products described in these materials may contain design defects or errors known as errata which may cause the product to deviate from published specifications. To the extent permitted by applicable law, Cypress reserves the right to make changes to this document without further notice. Cypress does not assume any liability arising out of the application or use of any product or circuit described in this document. Any information provided in this document, including any sample design information or programming code, is provided only for reference purposes. It is the responsibility of the user of this document to properly design, program, and test the functionality and safety of any application made of this information and any resulting product. "High-Risk Device" means any device or system whose failure could cause personal injury, death, or property damage. Examples of High-Risk Devices are weapons, nuclear installations, surgical implants, and other medical devices. "Critical Component" means any component of a High-Risk Device whose failure to perform can be reasonably expected to cause, directly or indirectly, the failure of the High-Risk Device, or to affect its safety or effectiveness. Cypress is not liable, in whole or in part, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any use of a Cypress product as a Critical Component in a High-Risk Device. You shall indemnify and hold Cypress, including its affiliates, and its directors, officers, employees, agents, distributors, and assigns harmless from and against all claims, costs, damages, and expenses, arising out of any claim, including claims for product liability, personal injury or death, or property damage arising from any use of a Cypress product as a Critical Component in a High-Risk Device. Cypress products are not intended or authorized for use as a Critical Component in any High-Risk Device except to the limited extent that (i) Cypress’s published data sheet for the product explicitly states Cypress has qualified the product for use in a specific High-Risk Device, or (ii) Cypress has given you advance written authorization to use the product as a Critical Component in the specific High-Risk Device and you have signed a separate indemnification agreement.
Cypress, the Cypress logo, and combinations thereof, WICED, ModusToolbox, PSoC, CapSense, EZ-USB, F-RAM, and Traveo are trademarks or registered trademarks of Cypress or a subsidiary of Cypress in the United States or in other countries. For a more complete list of Cypress trademarks, visit www.infineon.com. Other names and brands may be claimed as property of their respective owners.