PSOC™ 4: CAPSENSE™ pipeline scan and process

This code example demonstrates how to implement pipeline scanning in CAPSENSE™ to improve performance. When a particular widget is processed, the next widget in line can be scanned in parallel. This method is more efficient than the traditional method of scanning all the widgets and then processing the scanned data later.

View this README on GitHub.

Provide feedback on this code example.

Requirements

ModusToolbox™ v3.5 or later (tested with v3.5)
Board support package (BSP) minimum required version: 3.1.0
Programming language: C
Associated parts: PSOC™ 4 HV (High Voltage)

Supported toolchains (make variable 'TOOLCHAIN')

GNU Arm® Embedded Compiler v11.3.1 (GCC_ARM) – Default value of TOOLCHAIN
Arm® Compiler v6.22 (ARM)
IAR C/C++ Compiler v9.50.2 (IAR)

Supported kits (make variable 'TARGET')

PSOC™ 4 HVMS-64K Evaluation Kit (KIT_PSOC4-HVMS-64K_LITE) - Default value of TARGET
PSOC™ 4 HVMS-128K Evaluation Kit (KIT_PSOC4-HVMS-128K_LITE)

Hardware setup

This example uses the board's default configuration. See the kit user guide to ensure that the board is configured correctly.

Software setup

See the ModusToolbox™ tools package installation guide for information about installing and configuring the tools package.

This example requires no additional software or tools.

Using the code example

Create the project

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 "PSOC™ 4: CAPSENSE™ Pipeline scan and process" application with the desired name "PipelineScan" configured for the KIT_PSOC4-HVMS-64K_LITE BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id KIT_PSOC4-HVMS-64K_LITE --app-id mtb-example-ce241761-capsense-pipeline-scan-and-process --user-app-name PipelineScan --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 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™ tools package user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf).

Open the project

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).

Operation

Connect the board to your PC using the provided USB cable through the KitProg3 USB connector
Program the board using one of the following:
Using Eclipse IDE
1. Select the application project in the Project Explorer
2. 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 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
```
After programming, the application starts automatically. The status of the on-board user buttons can be visually observed through their corresponding on-board user LEDs. By default or during a no-press condition, LEDs are turned OFF. A button press or slider segment press is visually indicated by turning ON the corresponding LED
You can implement the same design process in your application. The higher the number of sensors in the application, the more noticeable and faster the response

Monitor data using CAPSENSE™ Tuner

Launch the CAPSENSE™ tuner from the 'BSP Configurators' section in the IDE Quick Panel to monitor the CAPSENSE™ data
Ensure that the kits are in CMSIS-DAP Bulk mode (KitProg3 Status LED is ON and not blinking). See Firmware Loader to learn how to update the firmware and switch modes in KitProg3
In the tuner application, click on the Tuner communication setup icon or select Tools > Tuner Communication Setup. In the window that appears, select the I2C checkbox under KitProg3 and configure it as follows:

UART baudrate: 115200

These are the same values set in the UART resource.

Figure 1. Tuner communication setup parameters

Click Connect or select Communication > Connect to establish a connection.

Figure 2. Establish connection
Click Start or navigate to Communication > Start to start data streaming from the device

Figure 3. Start tuner communication
Set the Read mode to Synchronized mode. Navigate to the Widget view tab and observe that the Button0 widget is highlighted in blue when touched

Figure 4. Widget View tab of the CAPSENSE™ Tuner
The Tuner GUI displays the data from the sensor in the Widget View and Graph View tabs

Scan architecture

Pipeline scanning is a technique to scan and process widgets in parallel rather than sequentially scanning all the sensors/widgets and then processing them altogether. A faster method is when the CAPSENSE™ controller scans a particular widget while the previous widget is processed by the processor and the device is put into Deep Sleep until the scan is complete. The WDT (Watchdog Timer) is used to wake up the device periodically from Deep Sleep. This reduces the total effective scan time and minimizes the power consumption of the application.

A comparison between the two scanning methods is shown in Figure 5.

Figure 5. Scan flow for pipeline and sequential scan methods

Debugging

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.

Note: For all kits, the debug port is by default disabled in order to achieve low power. If debugging is required, do the following:

Enable the Debug mode under the Systems tab in the Device Configurator and change the Debug mode setting to SWD.
Select the pins P3[2] (SWDIO) and P3[3] (SWDCK) under the SWD pin setting.
Select the Drive mode of both the pins as "Strong Drive,Input buffer on" under the Pins tab in the Device Configurator.

Design and implementation

The project contains multiple button widgets is configured in the CSX sensing mode. For details on CAPSENSE™ CSD and CSX sensing modes, see the "CAPSENSE™ CSX sensing method" section in the AN85951 – PSOC™ 4 and PSOC™ 6 MCU CAPSENSE™ design guide.

The sensing elements are mapped to the onboard user buttons. The status of an onboard user button is conveyed by controlling the LED state. The LED turns ON when a button press is registered and remains OFF when the button is not pressed.

Refer to the PSOC™ 4 MCU: CAPSENSE™ CSX button tuning code example to tune the CSX sensors.

The WDT in PSOC™ 4 is a 16-bit timer and uses the internal low-speed oscillator (ILO) clock of 40 kHz as a source. The accuracy of ILO is (-50% to +100%). Therefore, the match value of WDT is set after compensating the ILO with IMO. The firmware flow is as follows:

Enable the ILO, which is the source for the WDT. Start ILO measurement and get the value of ilo_compensated_counts which must be set after every interrupt match
Write the match value. The WDT can generate an interrupt when the WDT counter reaches the match count. The match count is generated using DESIRED_WDT_INTERVAL
Enable interrupt generation and assign the interrupt service routine (wdt_isr)
Enable the WDT. Since the ILO has low accuracy, the ilo_compensated_counts are calculated, and the match value of the WDT is updated following a WDT interrupt
The System is put into Deep Sleep in idle mode to save power. Since the watchdog timer works on a low-frequency clock (LFCLK), its operation will not be affected when the system is put into Deep Sleep mode. The watchdog timer interrupt will wake the device from Deep Sleep mode

Note:

The WDT is configured to generate interrupts at WDT_INTERRUPT_INTERVAL_MS intervals. The default value of WDT_INTERRUPT_INTERVAL_MS is 10 ms. The WDT generates an interrupt on reaching the match value. The WDT counter is not reset on a match; it continues to count across the full 16-bit resolution. Therefore, the new match value of the WDT counter is generated and updated on every WDT interrupt event to generate an interrupt after the present interrupt. The WDT interrupt flag is set inside the WDT interrupt service routine; it is checked in the main loop.
The WDT can be enabled using Device Configurator as shown in Figure 6.
The WDT interrupt interval and WDT interrupt priority can be configured and updated using the macros in main.c as shown in Figure 7.

Figure 6. WDT settings

Figure 7. Accessing macros

Set up the VDDA supply voltage and Debug mode in Device Configurator

Open Device Configurator from the Quick Panel
Navigate to the System tab. Select the Power resource and set the VDDA value under Operating conditions
By default, SWD pins are active in all device power modes. Disable Debug mode to disable the SWD pins and thereby reduce power consumption as follows:

Figure 8. Disable Debug mode in the System tab of Device Configurator

Resources and settings

Figure 9. UART settings

Related resources

Resources	Links
Application notes	AN0034 – PSOC™ 4 and PSOC™ 6 MCU CAPSENSE™ design guide
Code examples	Using ModusToolbox™ on GitHub
Device documentation	PSOC™ high voltage (HV) mixed signal (MS) automotive MCU 128K datasheets PSOC™ high voltage (HV) mixed signal (MS) automotive MCU 64K datasheets PSOC™ high voltage (HV) mixed signal (MS) MCU: PSOC™ HVMS-128K registers reference manuals PSOC™ high voltage (HV) mixed signal (MS) MCU: PSOC™ HVMS-64K registers reference manuals PSOC™ high voltage (HV) mixed signal (MS) MCU architecture reference manuals
Development kits	Select your kits from the Evaluation board finder page.
Libraries on GitHub	mtb-pdl-cat2 – PSOC™ 4 Peripheral Driver Library (PDL)
Middleware on GitHub	capsense – CAPSENSE™ library and documents psoc4-middleware – Links to all PSOC™ 4 MCU middleware
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.

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: CE241761 - PSOC™ 4: CAPSENSE™ pipeline scan and process

Version	Description of change
1.0.0	New code example

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™.

© Cypress Semiconductor Corporation, 2025. 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, 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.

License

Infineon/mtb-example-ce241761-capsense-pipeline-scan-and-process

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages