This code example demonstrates how to use the CAPSENSE™ middleware to detect a finger touch and gesture on a self-capacitance-based button widget in PSoC™ 4000T device with multi-sense converter low-power (MSCLP) CAPSENSE™ block.
In addition, this code example also explains how to manually tune the self-capacitance-based button for optimum performance with respect to parameters such as reliability, power consumption, and response time using the CSD-RM sensing technique and CAPSENSE™ Tuner GUI. Here, capacitive sigma-delta (CSD) represents the self-capacitance sensing technique, and RM represents the ratiometric method.
Provide feedback on this code example.
-
ModusToolbox™ v3.2 or later
Note: This code example version requires ModusToolbox™ version 3.2 or later and is not backward compatible with v3.1 or older versions.
-
Board support package (BSP) minimum required version: 3.2.0
-
Programming language: C
-
Associated parts: PSoC™ 4000T
- GNU Arm® Embedded Compiler v11.3.1 (
GCC_ARM) - Default value ofTOOLCHAIN - Arm® Compiler v6.16 (
ARM) - IAR C/C++ Compiler v9.30.1 (
IAR)
- PSoC™ 4000T CAPSENSE™ Evaluation Kit (
CY8CKIT-040T) - DefaultTARGET
This example uses the board's default configuration. See the kit user guide to ensure that the board is configured correctly to use VDDA at 1.8 V.
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 "PSoC™ 4: MSCLP self-capacitance button tuning" application with the desired name "MSCLPButtonTuning" configured for the CY8CKIT-040T BSP into the specified working directory, C:/mtb_projects:
project-creator-cli --board-id CY8CKIT-040T --app-id mtb-example-psoc4-msclp-self-capacitance-button --user-app-name MSCLPButtonTuning --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).
Keil µVision
Double-click the generated {project-name}.cprj file to launch the Keil µVision IDE.
For more details, see the 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 micro USB cable through the KitProg3 USB connector as follows:
Figure 1. Connecting the CY8CKIT-040T kit with the PC
-
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).
Using CLI
From the terminal, execute the
make programcommand to build and program the application using the default toolchain to the default target. The target and the toolchain is specified manually:make program TARGET=<BSP> TOOLCHAIN=<toolchain>Example:
make program TARGET=CY8CKIT-040T TOOLCHAIN=GCC_ARM -
-
After programming, the application starts automatically.
Note: After programming, you will see the following error message if debug mode is disabled. This can be ignored or enabling debug solves this error.
"Error: Error connecting Dp: Cannot read IDR"-
To test the application, place your finger over the CAPSENSE™ button and notice that the LED1 turns ON with a green color when touched, and turns OFF when the finger is lifted. Observe the following LED2 colors for respective gesture performed:
-
One finger single-click > red color
-
One finger double-click > blue color
-
-
You can also monitor the CAPSENSE™ data using the CAPSENSE™ Tuner application as follows:
-
Open the CAPSENSE™ Tuner from the Tools section in the IDE Quick Panel.
You can also run the CAPSENSE™ Tuner application standalone from {ModusToolbox™ install directory}/ModusToolbox/tools_{version}/capsense-configurator/capsense-tuner. In this case, after opening the application, select File > Open and open the design.cycapsense file of the respective application, which is present in the {Application root directory}/bsps/TARGET_APP_<BSP-NAME>/config folder.
See the ModusToolbox™ user guide (locally available at ModusToolbox™ install directory/docs_{version}/mtb_user_guide.pdf) for options to open the CAPSENSE™ Tuner application using the CLI.
-
Ensure the kit is 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, select the I2C checkbox under KitProg3 and configure as follows:
- I2C address: 8
- Sub-address: 2-Bytes
- Speed (kHz): 400
These are the same values set in the EZI2C resource.
Figure 2. Tuner Communication Setup parameters
-
Click Connect or select Communication > Connect to establish a connection.
Figure 3. Establish connection
-
Click Start or select Communication > Start to start data streaming from the device.
Figure 4. Start Tuner Communication
The Widget/Sensor parameters tab gets updated with the parameters configured in the CAPSENSE™ Configurator window. The tuner displays the data from the sensor in the Widget View and Graph View tabs.
-
Set the Read mode to Synchronized mode. Navigate to the Widget View tab, and you can see the Button_SELF_CAP widget highlighted in blue color when you touch it.
Figure 5. Widget View of the CAPSENSE™ Tuner
-
You can view the raw count, baseline, difference count, and status for each sensor in the Graph View tab. For example, to view the sensor data for Button_SELF_CAP, select Button_SELF_CAP_Sns0 under Button_SELF_CAP.
Figure 6. Graph View for the CAPSENSE™ Tuner
-
Observe the Widget/Sensor parameters section in the CAPSENSE™ Tuner window as shown in Figure 6.
-
Switch to the SNR Measurement tab for measuring the SNR. Verify that the SNR is greater than 5:1 and the signal count is above 50. Select the Button_SELF_CAP and Button_SELF_CAP_Sns0 sensors, and then click Acquire Noise as shown in Figure 7.
Figure 7. CAPSENSE™ Tuner – SNR measurement: Acquire noise
-
Once the noise is acquired, place the metal finger (6 mm finger is used in this example) at a position on the button and then click Acquire Signal. Ensure that the metal finger remains on the button as long as the signal acquisition is in progress. Observe that the SNR is above 5:1 and the signal count is above 50.
The calculated SNR on this button is displayed as shown in Figure 8. Based on your end- system design, test the signal with a finger that matches the size of your normal use case. Typically, finger-size targets are ~4 to 8 mm. Consider testing with smaller sizes that should be rejected by the system to ensure that they do not reach the finger threshold.
Figure 8. CAPSENSE™ Tuner – SNR measurement: Acquire signal
-
Gesture Monitor provides visual indication for a detected gesture. Gesture Event History logs the detected gestures information.
Note: To open the Gesture Monitor window, select View > Gesture Monitor/Gesture Event History
Figure 9. Gesture monitor view of the CAPSENSE™ Tuner
CY8CKIT-040T kit supports operating voltages of 1.8 V, 3.3 V, and 5 V. Use voltage selection switch available on top of the kit to set the preferred operating voltage and see the Setup the VDDA supply voltage and Debug mode section.
This application functionalities are optimally tuned for 1.8 V. However, you can observe the basic functionalities working across other voltages.
It is recommended to tune the application with the preferred voltages for better performance.
Create a custom BSP for your board
-
Create a custom BSP for your board having any device, by following the steps given in ModusToolbox™ BSP Assistant user guide. This code example was created for the device "CY8C4046LQI-T452".
-
Open the design.modus file from the {Application root directory}/bsps/TARGET_APP_<BSP-NAME>/config/ folder obtained in the previous step and enable CAPSENSE™ to get the design.cycapsense file. CAPSENSE™ configuration can then be started from scratch as follows.
The following steps explain the tuning procedure:
Note: See the section "Selecting CAPSENSE™ hardware parameters" in the PSoC™ 4 and PSoC™ 6 MCU CAPSENSE™ design guides to learn about the considerations for selecting each parameter value.
Figure 10. CSD button widget tuning flow
-
Connect the board to your PC using the provided USB cable through the KitProg3 USB connector.
-
Launch the Device Configurator tool.
You can launch the Device Configurator in Eclipse IDE for ModusToolbox™ from the Tools section in the IDE Quick panel or in standalone mode from {ModusToolbox™ install directory}/ModusToolbox/tools_{version}/device-configurator/device-configurator. In this case, after opening the application, select File > Open and open the design.modus file of the respective application, located in the {Application root directory}/bsps/TARGET_APP_<BSP-NAME>/config/ folder.
-
In the PSoC™ 4000T kit, the button pin is connected to CAPSENSE™ channel (MSCLP 0). Therefore, make sure to enable CAPSENSE™ channel in the Device Configurator as shown in Figure 11.
Figure 11. Enable MSCLP channels in Device Configurator
Save the changes and close the window.
-
Launch the CAPSENSE™ Configurator tool.
You can launch the CAPSENSE™ configurator tool in Eclipse IDE for ModusToolbox™ from the 'CAPSENSE™' peripheral setting in the device configurator or directly from the Tools section in the IDE Quick panel. You can also launch it in standalone mode from {ModusToolbox™ install directory}/ModusToolbox/tools_{version}/capsense-configurator/capsense-configurator. In this case, after opening the application, select File > Open and open the design.cycapsense file of the respective application, which is present in the {Application root directory}/bsps/TARGET_APP_<BSP-NAME>/config/ folder.
See the ModusToolbox™ CAPSENSE™ configurator tool guide for step-by-step instructions on how to configure and launch CAPSENSE™ in ModusToolbox™.
-
In the Basic tab, note that the button widget 'Button_SELF_CAP' is configured as a CSD-RM (self-cap).
Figure 12. CAPSENSE™ Configurator – Basic tab
-
Go to Advanced > General tab, and do the following:
-
Select CAPSENSE™ IMO clock frequency as 46 MHz.
-
Set Modulator clock divider to 1 to obtain the maximum available modulator clock frequency as recommended in the PSoC™ 4 and PSoC™ 6 MCU CAPSENSE™ design guide.
Note: The modulator clock frequency can be set to 46,000 kHz after changing the CAPSENSE™ IMO clock frequency to 46 MHz, because the modulator clock is derived from the CAPSENSE™ IMO clock. In the CAPSENSE™ IMO clock frequency drop-down list, select 46 MHz.
-
Number of init sub-conversions is set based on the hint shown when you hover over the edit box. Retain the default value.
-
Because CIC2 filter is enabled, it is recommended to enable the IIR filter. Retain the default settings for all filters. You can enable the filters later depending on the signal-to-noise ratio (SNR) requirements mentioned in Stage 3.
Filters are used to reduce the peak-to-peak noise. Using filters will result in higher scan time.
Figure 13. CAPSENSE™ Configurator - General settings
Note: Each tab has a Restore Defaults button to restore the parameters of that tab to their default values.
-
-
Go to the CSD Settings tab and make the following changes:
-
Set Inactive sensor connection as Shield.
-
Set Shield mode as Active.
-
Set Total shield count to 11.
To improve noise immunity, configure all the unused sensor pins as shield.
-
Raw count calibration level (%) helps in achieving the required CDAC calibration levels (85% of maximum count by default) for all sensors in the widget, while maintaining the same sensitivity across the sensor elements.
Raw count calibration level can be reduced if the application reaches the saturation level on a touch event.
Figure 14. CAPSENSE™ Configurator - Advanced CSD settings
-
-
Go to the Widget Details tab. Select Button_SELF_CAP from the left pane, and then set the following:
-
Sense clock divider: Retain default value (will be set in Stage 2)
-
Clock source: Direct
Note: Spread spectrum clock (SSC) or PRS clock can be used as a clock source to deal with EMI/EMC issues.
-
Number of sub-conversions: 60
'60' is a good starting point to ensure a fast scan time and sufficient signal. This value will be adjusted as required in Stage 4.
-
Finger threshold: 20
-
Noise threshold: 10
-
Negative noise threshold: 10
-
Low-baseline reset: 30
-
Hysteresis: 5
-
ON debounce: 3
These values reduces the influence of baseline on the sensor signal, which helps to get the true difference-count. Retain the default values for the widget threshold parameters; these parameters are set in Stage 4.
Figure 15. CAPSENSE™ Configurator - Widget details tab under the Advanced tab
-
-
Go to the Scan Configuration tab to select the pins, the scan slots, and do the following:
-
Configure the pin for the electrode using the drop-down menu.
-
Configure the scan slot using the Auto-Assign Slots option or each sensor is allotted a scan slot based on the entered slot number.
-
Check the notice list for warning or errors.
Note: Enable the Notice List in the View menu if it is not visible.
Figure 16. Scan Configuration tab
-
-
Click Save to apply the settings.
The sense clock is derived from the modulator clock using a clock-divider and is used to scan the sensor by driving the CAPSENSE™ switched capacitor circuits. Both the clock source and clock divider are configurable. The sense clock divider should be configured such that the pulse width of the sense clock is long enough to allow the sensor capacitance to charge and discharge completely. This is verified by observing the charging and discharging waveforms of the sensor, using an oscilloscope and an active probe. The sensors should be probed close to the electrode, and not at the sense pins or the series resistor.
Refer to Figure 17 and Figure 18 for waveforms observed on the shield. Figure 17 shows proper charging when sense clock frequency is correctly tuned. The pulse width is at least 5 tau i.e., the voltage is reaching at least 99.3% of the required voltage at the end of each phase. Figure 18 shows incomplete settling (charging/discharging).
Figure 17. Proper charge cycle of a sensor
Figure 18. Improper charge cycle of a sensor
-
Program the board and launch CAPSENSE™ Tuner.
-
Observe the charging waveform of the sensor as described above.
-
If the charging is incomplete, increase the Sense clock divider. This can be done in CAPSENSE™ Tuner by selecting the sensor and editing the Sense clock divider parameter in the Widget/Sensor Parameters panel.
Note: The sense clock divider should be divisible by 4. This ensures that all four scan phases have equal durations.
After editing the value click the Apply to Device button and observe the waveform again. Repeat this until complete settling is observed.
-
Click the Apply to Project button so that the configuration is saved to your project.
Figure 19. Sense clock divider setting
-
Repeat this process for all the sensors and the shield. Each sensor might require a different sense clock divider value to charge/discharge completely. But all the sensors which are in the same scan slot need to have the same sense clock source, sense clock divider, and number of sub-conversions. Therefore take the largest sense clock divider in a given scan slot and apply it to all the other sensors that share that slot.
The sensor should be tuned to have a minimum SNR of 5:1 and a minimum signal of 50 to ensure reliable operation. The sensitivity can be increased by increasing number of sub-conversions and noise can be decreased by enabling filters.
Note: If the sensor raw count saturates (equals Max Raw count) on touch, reduce the Raw count calibration level (%) to help with avoiding saturation.
The steps for optimizing these parameters are as follows:
-
Measure the SNR as mentioned in the Operation section.
-
If the SNR is less than 5:1, increase the number of sub-conversions. Edit the number of sub-conversions (Nsub) directly in the Widget/Sensor parameters tab of the CAPSENSE™ Tuner.
Note: Number of sub-conversion should be greater than or equal to 8.
-
Load the parameters to the device and measure SNR as mentioned in steps 9 and 10 in the Monitor data using the Tuner section.
Repeat steps 1 to 3 until the following conditions are met:
- Measured SNR from the previous stage is greater than 5:1
- Signal count is greater than 50
-
If the system is very noisy (>40% of Signal), enable filters.
This example has the CIC2 filter enabled, which increases the resolution for the same scan time. See AN234231 - Achieving lowest-power capacitive sensing with PSoC™ 4000T for detailed information on the CIC2 filter. Whenever CIC2 filter is enabled, it is recommended to enable the IIR filter for optimal noise reduction. Therefore this example has the IIR filter enabled as well.
-
Open CAPSENSE™ Configurator from ModusToolbox™ Quick Panel and select the appropriate filter:
Figure 20. Filter settings in CAPSENSE™ Configurator
-
Enable the filter based on the type of noise in your system. See AN85951 – PSoC™ 4 and PSoC™ 6 MCU CAPSENSE™ design guide for more details.
-
Click Save and close CAPSENSE™ Configurator. Program the device to update the filter settings.
Note : Increasing number of sub-conversions and enabling filters will increase the scan time which in turn decreasing the responsiveness of the Sensor. Increase in scan time also increases the power consumption. Therefore the number of sub-conversions and filter configuration must be optimized to achieve a balance between SNR, power and refresh rate.
Various thresholds, relative to the signal, need to be set for each sensor. Do the following in CAPSENSE™ Tuner to set up the thresholds for a widget:
-
Switch to the Graph View tab and select Button_SELF_CAP.
-
Touch the sensor and monitor the touch signal in the sensor signal graph, as shown in Figure 21.
Figure 21. Sensor signal when the sensor is touched
-
When the signal is measured, set the thresholds according to the following recommendations:
-
Finger threshold = 80% of the signal
-
Noise threshold = 40% of the signal
-
Negative noise threshold = 40% of the signal
-
Hysteresis = 10% of the signal
-
Debounce = 6
-
-
Set the threshold parameters in the Widget/Sensor Parameters section of the CAPSENSE™ Tuner:
Figure 22. Widget threshold parameters
-
Apply the settings to the device and to the project by clicking Apply to Device.
Figure 23. Apply settings to device
After applying the configuration test the performance by touching the button. If your sensor is tuned correctly, you will observe the touch status go from 0 to 1 in the Status panel of the Graph View tab as Figure 24 shows. The status of the button is also indicated by LED1 in the kit; LED1 turns ON when the finger touches the button and turns OFF when the finger is removed.
Figure 24. Sensor status in CAPSENSE™ Tuner
-
Click Apply to Project as Figure 25 shows. The change is updated in the design.cycapsense file. Close CAPSENSE™ Tuner and launch CAPSENSE™ Configurator. You should now see all the changes that you made in the CAPSENSE™ Tuner reflected in the CAPSENSE™ Configurator.
Figure 25. Apply settings to project
Table 1. Software tuning parameters obtained based on sensors for CY8CKIT-040T
Parameter CY8CKIT–040T (Pin P4.1) Signal 919 Finger threshold 735 Noise threshold 367 Negative noise threshold 367 Hysteresis 91 ON debounce 6 Low baseline reset 30
You can set the gesture parameters directly in the Widget/Sensor parameters tab of the CAPSENSE™ Tuner and observe the results in the Gesture Monitor/Gesture View.
Note: Click on the parameter to understand the definition and its valid range.
Figure 26. Gesture parameters
In this application gesture parameters have been set for the typical use case, but you can change these parameters as per the need of application use case.
You can debug this project to step through the code. In the 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.
By default, the debug option is disabled in the Device Configurator. To enable the debug option, see the Setup VDDA and Debug mode section. To achieve low power consumption, it is recommended to disable it.
The project contains a button widget configured in CSD-RM sensing mode. See the Tuning procedure section for step-by-step instructions to configure the other settings of the CAPSENSE™ Configurator.
The project uses the CAPSENSE™ middleware (see ModusToolbox™ user guide for more details on selecting a middleware). See AN85951 - PSoC™ 4 and PSoC™ 6 MCU CAPSENSE™ design guide for more details on CAPSENSE™ features and usage.
The ModusToolbox™ provides a GUI-based tuner application for debugging and tuning the CAPSENSE™ system. The CAPSENSE™ Tuner application works with EZI2C and UART communication interfaces. This project has an SCB block configured in EZI2C mode to establish communication with the on-board KitProg, which in turn enables reading the CAPSENSE™ raw data by the CAPSENSE™ Tuner. See EZI2C - Peripheral settings.
The CAPSENSE™ data structure that contains the CAPSENSE™ raw data is exposed to the CAPSENSE™ Tuner by setting up the I2C communication data buffer with the CAPSENSE™ data structure. This enables the tuner to access the CAPSENSE™ raw data for tuning and debugging CAPSENSE™.
The successful tuning of the button is indicated by the RGB LED in the Evaluation Kit; the LED is turned ON when the finger touches the button and turned OFF when the finger is removed from the button.
The MOSI pin of the SPI slave peripheral is used to transfer data to the three serially connected LEDs for controlling color, brightness, and ON or OFF operation. The three LEDs form a daisy-chain connection, and communication happens over the serial interface to create an RGB configuration. The LED accepts a 32-bit input code, with three bytes for red, green, and blue colors, five bits for global brightness, and three blank '1' bits. See the LED datasheet for more details.
-
Open Device Configurator from the Quick panel.
-
Go to the System tab. Select the Power resource, and set the VDDA value under Operating Conditions as shown in Figure 27.
Figure 27. Setting the VDDA supply in the System tab of the Device Configurator
-
By default, the Debug mode is disabled for this application to reduce power consumption. Enable the Debug mode to enable the SWD pins as follows:
Figure 28. Enable Debug mode in the System tab of the Device Configurator
Figure 29. EZI2C settings
Figure 30. SPI settings
Resource Alias/object Purpose SCB (EZI2C) (PDL) CYBSP_EZI2C EZI2C slave driver to communicate with CAPSENSE™ Tuner CAPSENSE™ CYBSP_MSC CAPSENSE™ driver to interact with the MSCLP hardware and interface the CAPSENSE™ sensors Digital pin CYBSP_SERIAL_LED To show the button operation SCB (SPI) (PDL) CYBSP_MASTER_SPI SPI master driver to drive the serial LED which visualizes button response Figure 31. Firmware flowchart
Resources Links Application notes AN79953 - Getting started with PSoC™ 4
AN85951 - PSoC™ 4 and PSoC™ 6 MCU CAPSENSE™ design guide
AN234231 - Achieving lowest-power capacitive sensing with PSoC™ 4000TCode examples Using ModusToolbox™ on GitHub Device documentation PSoC™ 4 datasheets
PSoC™ 4 technical reference manualsDevelopment kits Select your kits from the Evaluation board finder Libraries on GitHub mtb-hal-cat2 - Hardware Abstraction Layer (HAL) library Middleware on GitHub CAPSENSE™ Middleware Library - CAPSENSE™ library 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 and Bluetooth® connectivity devices. 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: CE235178 - PSoC™ 4: MSCLP self-capacitance button tuning
Version Description of change 1.0.0 New code example.
This version is not backward compatible with ModusToolbox™ v2.4.1.0.1 Minor readme update. 1.1.0 Minor folder structure changes that doesn't break backward compatibility. 2.0.0 Major update to support ModusToolbox™ v3.1 and the BSP changes. This version is not backward compatible with previous versions of ModusToolbox™. 2.1.0 Gesture feature demonstrated on CSD Button. 2.1.1 Minor configuration and readme update 3.0.0 Major update to support ModusToolbox™ v3.2 and CAPSENSE™ Middleware v5.0. This version is not backward compatible with previous versions of ModusToolbox™.
All other trademarks or registered trademarks referenced herein 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.
© 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, 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 respecti -
