gint#
Overview#
This example shows how to use SDK drivers to use the Group GPIO input interrupt peripheral.
Supported Boards#
FRDM-MCXW23
Hardware requirements
Type-C USB cable
FRDM-MCXW23 Board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a USB cable between the host PC and the FRDM board J10.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 event is configured
Press corresponding switch to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW2 and SW5 switches are pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal.
LPCXpresso51U68
Hardware requirements
Micro USB cable
LPCXpresso51U68 board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a micro USB cable between the PC host and the CMSIS DAP USB port (J6) on the board
Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number):
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW1 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when both the switches SW2 and SW3 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
LPCXpresso54628
Hardware requirements
Micro USB cable
LPCXpresso54628 board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a micro USB cable between the host PC and the LPC-Link USB port (J8) on the target board.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW2 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when both the switches SW3 and SW4 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
LPCXpresso54S018
Hardware requirements
Micro USB cable
LPCXpresso54S018 board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a micro USB cable between the host PC and the LPC-Link USB port (J8) on the target board.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
This demo is an external flash plain load demo, ROM will copy image in external flash to SRAMX to run:
Build the demo to generate a bin file. Note: If need to generate bin file using MCUXpresso IDE, below steps need to be followed: Set in example Properties->C/C++ Build->Settings->Build steps->Post-build steps->Edit enbable arm-none-eabi-objcopy -v -O binary “&{BuildArtifactFileName}” “&{BuildArtifactFileBaseName}.bin”
This plainload example linked the vector table to 0x00000000, but program to external flash 0x10000000.
Program the bin file to external on board flash via SEGGER J-FLASH Lite(V6.22 or higher):
a. Open SEGGER J-FLASH Lite, select device LPC54S018.
b. Click the ‘Erase Chip’ to erase the extrenal flash.(if can not success, press SW4 button and reset the board, and try to erase again)
c. Select the bin data file, set the ‘.bin/Erase Start’ address to 0x10000000, then click ‘Program Device’ Note: Please use above way to program the binary file built by armgcc tool chain to external flash. For IAR, KEIL, MCUXpresso IDE, you can use the IDE tool to program the external flash.
Launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW2 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when both the switches SW3 and SW4 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
LPCXpresso54S018M
Hardware requirements
Micro USB cable
LPCXpresso54S018M board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a micro USB cable between the host PC and the LPC-Link USB port (J8) on the target board.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
This demo is an external flash plain load demo, ROM will copy image in external flash to SRAMX to run:
Build the demo to generate a bin file. Note: If need to generate bin file using MCUXpresso IDE, below steps need to be followed: Set in example Properties->C/C++ Build->Settings->Build steps->Post-build steps->Edit enbable arm-none-eabi-objcopy -v -O binary “&{BuildArtifactFileName}” “&{BuildArtifactFileBaseName}.bin”
This plainload example linked the vector table to 0x00000000, but program to external flash 0x10000000.
Program the bin file to external on board flash via SEGGER J-FLASH Lite(V6.22 or higher):
a. Open SEGGER J-FLASH Lite, select device LPC54S018M.
b. Click the ‘Erase Chip’ to erase the extrenal flash.(if can not success, press SW4 button and reset the board, and try to erase again)
c. Select the bin data file, set the ‘.bin/Erase Start’ address to 0x10000000, then click ‘Program Device’ Note: Please use above way to program the binary file built by armgcc tool chain to external flash. For IAR, KEIL, MCUXpresso IDE, you can use the IDE tool to program the external flash.
Launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW2 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when both the switches SW3 and SW4 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
LPCXpresso55S06
Hardware requirements
Micro USB cable
LPCXpresso55S06 board
Personal Computer
Board settings
Prepare the Demo
Connect a micro USB cable between the PC host and the CMSIS DAP USB port (J1) on the board
Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number):
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
“Group GPIO interrupt 1”” is configured to be invoked when both the switches SW1 and SW4 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal. This example configures “Group GPIO interrupt 0”” to be invoked when SW3 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal.
LPCXpresso55S16
Hardware requirements
Micro USB cable
LPCXpresso55S16 board
Personal Computer
Board settings
The jumper setting: Default jumpers configuration does not work, you will need to add JP20 and JP21 (JP22 optional for ADC use)
Prepare the Demo
Connect a micro USB cable between the PC host and the CMSIS DAP USB port (J1) on the board
Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number):
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW4 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when both the switches SW1 and SW3 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
LPCXpresso55S28
Hardware requirements
Micro USB cable
LPCXpresso55S28 board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Note: MCUXpresso IDE project default debug console is semihost
Connect a micro USB cable between the PC host and the CMSIS DAP USB port (P6) on the board
Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number):
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW1 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when both the switches SW2 and SW3 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
LPCXpresso55S36
Hardware requirements
Micro USB cable
LPCXpresso55S36 board
Personal Computer
Board settings
Prepare the Demo
Connect a micro USB cable between the PC host and the CMSIS DAP USB port (J1) on the board
Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number):
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW1 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when SW3 is pressed by the user. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
LPCXpresso55S69
Hardware requirements
Micro USB cable
LPCXpresso55s69 board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Note: MCUXpresso IDE project default debug console is semihost
Connect a micro USB cable between the PC host and the CMSIS DAP USB port (P6) on the board
Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number):
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 and GINT1 events are configured
Press corresponding switches to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW1 switch is pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal. “”Group GPIO interrupt 1”” is configured to be invoked when both the switches SW2 and SW3 are pressed at the same time. The interrupt callback prints “GINT1 event detected” message on the serial terminal.
MCXW23-EVK
Hardware requirements
Mini/micro USB cable
MCXW23-EVK Board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a USB cable between the host PC and the EVK board J33.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
Running the demo
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
The following lines are printed to the serial terminal when the demo program is executed.
Group GPIO input interrupt example
GINT0 event is configured
Press corresponding switch to generate events
This example configures “Group GPIO interrupt 0”” to be invoked when SW3 and SW4 switches are pressed by the user. The interrupt callback prints “GINT0 event detected” message on the serial terminal.