WLAN low power

This code example demonstrates the low-power operation of a host MCU and a WLAN device using the network activity handlers provided by the low power assistant (LPA) middleware.

The code example connects to a configured network. After connecting to the network successfully, it configures the WLAN device in a power-save mode, suspending the network stack to put the host MCU in wait state. During this wait state, the host MCU enters a low-power state, and wakes up when any network activity is detected on the MAC interface.

View this README on GitHub.

Provide feedback on this code example.

Requirements

• ModusToolbox™ v3.1 or later (tested with v3.1)
• Board support package (BSP) minimum required version: 4.0.0
• Programming language: C
• Associated parts: All PSoC™ 6 MCU parts, AIROC™ CYW20819 Bluetooth® & Bluetooth® LE SoC, AIROC™ CYW43012 Wi-Fi & Bluetooth® combo chip, AIROC™ CYW4343W Wi-Fi & Bluetooth® combo chip, AIROC™ CYW4373 Wi-Fi & Bluetooth® combo chip, AIROC™ CYW43439 Wi-Fi & Bluetooth® combo chip,AIROC™ CYW43022 Wi-Fi & Bluetooth® combo chip

Supported toolchains (make variable 'TOOLCHAIN')

• GNU Arm® Embedded Compiler v11.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')

• PSoC™ 62S2 Wi-Fi Bluetooth® Prototyping Kit (CY8CPROTO-062S2-43439) – Default value of TARGET
• PSoC™ 6 Wi-Fi Bluetooth® Prototyping Kit (CY8CPROTO-062-4343W)
• PSoC™ 6 Wi-Fi Bluetooth® Pioneer Kit (CY8CKIT-062-WIFI-BT)
• PSoC™ 62S1 Wi-Fi Bluetooth® Pioneer Kit (CYW9P62S1-43438EVB-01)
• PSoC™ 62S1 Wi-Fi Bluetooth® Pioneer Kit (CYW9P62S1-43012EVB-01)
• PSoC™ 62S2 Wi-Fi Bluetooth® Pioneer kit (CY8CKIT-062S2-43012)
• PSoC™ 62S3 Wi-Fi Bluetooth® Prototyping Kit (CY8CPROTO-062S3-4343W)
• PSoC™ 64 "Secure Boot" Wi-Fi Bluetooth® Pioneer Kit (CY8CKIT-064B0S2-4343W)
• PSoC™ 62S2 Evaluation Kit (CY8CEVAL-062S2-LAI-4373M2, CY8CEVAL-062S2-LAI-43439M2, CY8CEVAL-062S2-MUR-43439M2,CY8CEVAL-062S2-CYW43022CUB,`CY8CEVAL-062S2-CYW955513SDM2WLIPA')
• PSoC™ 6 AI Evaluation Kit (CY8CKIT-062S2-AI)

Hardware setup

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

Note: The PSoC™ 6 Bluetooth® LE Pioneer Kit (CY8CKIT-062-BLE) and the PSoC™ 6 Wi-Fi Bluetooth® Pioneer Kit (CY8CKIT-062-WIFI-BT) ship with KitProg2 installed. ModusToolbox™ requires KitProg3. Before using this code example, make sure that the board is upgraded to KitProg3. The tool and instructions are available in the Firmware Loader GitHub repository. If you do not upgrade, you will see an error like "unable to find CMSIS-DAP device" or "KitProg firmware is out of date".

Software setup

See the ModusToolbox™ tools package installation guide for information about installing and configuring the tools package. Install a terminal emulator if you don't have one. Instructions in this document use Tera Term.

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

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

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

3. 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 "WLAN Lowpower" application with the desired name "WlanLowPower" configured for the CY8CPROTO-062S2-43439 BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id CY8CPROTO-062S2-43439 --app-id mtb-example-mtb-example-wifi-wlan-lowpower --user-app-name wlanlowpower --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).

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

Operation

1. Connect the board to your PC using the provided USB cable through the KitProg3 USB connector.

2. Modify the WIFI_SSID, WIFI_PASSWORD, and WIFI_SECURITY macros to match the credentials of the Wi-Fi network that you want to connect to. These macros are defined in the lowpower_task.h file.

   Note: See the AP's configuration page for the security type. See the cy_wcm_security_t enumeration in cy_wcm.h to pass the corresponding WCM security type in the WIFI_SECURITY macro.

3. Ensure that your PC is connected to the same Wi-Fi AP that you have configured in Step 2.

4. Open a terminal program and select the KitProg3 COM port. Set the serial port parameters to 8N1 and 115200 baud.

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

6. After programming, the application starts automatically. The example connects to the AP and suspends the network stack.

   Figure 1. Connected to AP and suspend the network stack

   

7. Open command prompt and ping the IP address displayed on the serial terminal:

   ping <IP address>
   

   The network stack resumes. The device displays the deep sleep and Wi-Fi SDIO bus statistics on the terminal. The LED is toggled after resuming the network stack after which the network stack is again suspended until network activity is detected.

   Note: The CY8CEVAL-062S2-CYW43022CUB kit will not wake up the host MCU through a ping. The AIROC™ CYW43022 Wi-Fi & Bluetooth® combo chip takes care of the ping request and supports ARP offload by default. This means that the chip can perform ARP resolution for the host MCU, reducing network activity and further decreasing power consumption. However, the host MCU can still be woken up by other network activity such as broadcast or multicast packets issued by the access point.

   Note: The host MCU will wake up when any network activity is detected and not necessarily due to the ping from the PC. The reasons for network activity could be due to the broadcast or multicast packets issued by the AP. Further power saving can be done by employing offload features like packet filtering, which will increase the time the host MCU will be in deep sleep. See AN227910 - Low-power system design with AIROC™ CYW43012 Wi-Fi & Bluetooth® combo chip and PSoC™ 6 MCU for more details.

   Figure 2. Resuming the network stack

   

   See Measuring the current consumption for instructions on how to measure the current consumed by the PSoC™ 6 MCU and the Wi-Fi device.

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. For details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ user guide.

Note: (Only while debugging) On the CM4 CPU, some code in main() may execute before the debugger halts at the beginning of main(). This means that some code executes twice – once before the debugger stops execution, and again after the debugger resets the program counter to the beginning of main(). See KBA231071 to learn about this and for the workaround.

Design and implementation

This code example uses the lwIP network stack, which runs multiple network timers for various network-related activities. These timers need to be serviced by the host MCU. As a result, the host MCU will not be able to stay in sleep or deep sleep state longer.

In this example, after successfully connecting to an AP, the host MCU suspends the network stack after a period of inactivity. The example uses two macros, INACTIVE_INTERVAL_MS and INACTIVE_WINDOW_MS, to determine whether the network is inactive. The host MCU monitors the network for inactivity in an interval of length INACTIVE_INTERVAL_MS. If the network is inactive for a continuous duration specified by INACTIVE_WINDOW_MS, the network stack will be suspended until there is a network activity.

The host MCU is alerted by the WLAN device on network activity, after which the network stack resumes. The host MCU is in deep sleep when the network stack is suspended. Because there are no network timers to be serviced, the host MCU stays in deep sleep for longer. This state where the host MCU is in deep sleep waiting for network activity is referred to as the wait state.

For more information on low-power system design that involves offloading tasks to the WLAN device for even better power savings, see AN227910 - Low-power system design with AIROC™ CYW43012 Wi-Fi & Bluetooth® combo chip and PSoC™ 6 MCU.

Creating a custom device configuration for low power

This code example overrides the default device configuration provided by library-manager or bsp-assistance with the one provided in <application_folder>/templates/TARGET_<kit> for the supported kits.

Note: This section provides instructions only for the targets CY8CPROTO-062-4343W and CY8CKIT-062S2-43012. For other targets, you can follow the same instructions to create a custom configuration. See the bsps/TARGET_<kit>/configs/GeneratedSource/cycfg_pins.h file for pin details such as CYBSP_WIFI_HOST_WAKE.

The custom configuration disables the phase-locked loop (PLL) and HF clock for unused peripherals such as audio or USB, and configures the buck regulator instead of the low dropout (LDO) regulator to power the PSoC™ 6 MCU device. This configuration reduces the current consumed by the PSoC™ 6 MCU device in an active state.

If your application uses any of the disabled peripherals, the corresponding peripherals and clocks should be enabled using the Device Configurator. Launch this tool from the Quick Panel inside the Eclipse IDE for ModusToolbox™ or from the command-line using the following command:

make config TARGET=<TARGET-KIT-NAME>

For example,

make config TARGET=CY8CKIT-062S2-43012

Do the following to create a custom configuration for a new kit:

1. Create a new directory inside templates with the same name as the target you are building the example for, such as <application_folder>/templates/TARGET_<kit>.

2. Copy the design.modus of the default bsp into the folder created in the previous step <application_folder>/templates/TARGET_<kit>/design.modus.

3. Open the copied design.modus file using the Device Configurator.

4. On the PSoC™ 6 MCU Pins tab of the Device Configurator, do the following:

Note: For CY8CEVAL-062S2-CYW955513SDM2WLIPA, Drive Mode should be set to Resistive Pull UP, Input Buffer ON.

CY8CKIT-062S2-43012:

1. Enable the Host WAKE pin P4[1] and name it CYBSP_WIFI_HOST_WAKE.

2. In the Parameters pane, change the following:

   • Drive Mode: Analog High-Z. Input buffer off

   • Initial Drive State: High(1)

   • Interrupt Trigger Type: Rising Edge

   Figure 3. Configuring the Host WAKE pin for CY8CKIT-062S2-43012

   

CY8CPROTO-062-4343W:

1. Enable the Host WAKE pin P0[4], and name it CYBSP_WIFI_HOST_WAKE.

2. In the Parameters pane, change the following:

   • Drive Mode: Analog High-Z. Input buffer off

   • Initial Drive State: High(1)

   • Interrupt Trigger Type: Rising Edge

   Figure 4. Configuring the Host WAKE pin for CY8CPROTO-062-4343W

   

Note: The Wi-Fi host driver takes care of the drive mode configuration of the Host WAKE pin.

5. Go to the Wi-Fi tab and enable the host wake configuration and set Host Device Interrupt Pin to CYBSP_WIFI_HOST_WAKE. This configuration applies to all supported kits.

   Figure 5. Enable Host Wake pin

   

6. Switch to the System tab, expand the System Clocks resource, and do the following:

   1. Clear the box in the FLL+PLL section to disable the PLL.

   2. In the High-Frequency section, disable HF clocks for the peripherals that are not being used in this code example.

      Do the following kit-specific changes:

      CY8CKIT-062S2-43012:

      1. Disable PLL0 and PLL1, and high-frequency clocks CLK_HF2 and CLK_HF3.

      2. PLL is the source clock for CLK_HF0. After disabling the PLL, change the source clock for CLK_HF0 to FLL.

         Figure 6. Clock settings in CY8CKIT-062S2-43012

         

      3. In the System Clocks resource, select CLK_HF0 and modify the Source Clock to CLK_PATH0.

         Figure 7. CLK_HF0 settings for CY8CKIT-062S2-43012

         

      CY8CPROTO-062-4343W:

      1. Disable PLL1 and high-frequency clocks CLK_HF2 & CLK_HF3.

         Figure 8. Clock settings in CY8CPROTO-062-4343W

         

7. Under the Power resource, change the Core Regulator under General to Normal Current Buck.

   Figure 9. Configuring the core regulator as normal current buck

   

8. Optionally, you can make higher power savings by switching to ULP mode. However, this mode requires the CM4 CPU to be limited to a maximum operating frequency of 50 MHz.

   CY8CPROTO-062-4343W:

   1. Under the Power resource, change the System Active Power Mode under General to ULP.

      Note: Switching to ULP causes a few errors to appear for FLL and CLK_PERI because their frequencies are greater than 50 MHz and 25 MHz respectively.

      Figure 10. Configuring System Active power mode

      

   2. Under the System tab, expand the System Clocks resource, select FLL, and modify the Desired Frequency to 50.000 MHz.

      Figure 11. FLL settings

      

   3. In the System Clocks resource, select CLK_PERI and modify the Divider to 2.

      Figure 12. CLK_PERI settings

      

   CY8CKIT-062S2-43012:

   1. Under the Power resource, change the System Active Power Mode under General to ULP.

      Note that switching to ULP causes a few errors to appear for FLL and CLK_PEI because their frequencies are greater than 50 MHz and 25 MHz respectively.

      Figure 13. Configuring System Active power mode

      

   2. Under the System tab, expand the System Clocks resource, select FLL, and modify the Desired Frequency to 50.000 MHz.

      Figure 14. FLL settings

      

9. Save the file to generate the source files.

   Note: See the schematic to determine the LED which is not powered directly by P6_VDD. If the LED is connected directly to P6_VDD, the LED current consumed will be added to the current measurement of the PSoC™ 6 MCU device. Find the corresponding macro for that LED in cybsp_types.h at <application_folder>/libs/TARGET_<kit>/cybsp_types.h. Provide that macro as the value for USER_LED in lowpower_task.h.

Measuring the current consumption

CY8CKIT-062S2-43012, CYW9P62S1-43438EVB-01, and CYW9P62S1-43012EVB-01

For PSoC™ 6 MCU:

1. Remove J25 to eliminate leakage currents across potentiometer R1.

2. Measure the current at J15 across VTARG and P6_VDD.

For CYW43xxx:

1. Measure the current at supplies VDDIO_WL used for SDIO communication interface and at VBAT used for powering CYW43xxx.

2. Measure the current at VDDIO_WL across VDDIO_WL and VCC_VDDIO2 at J17.

3. Measure the current at VBAT across VBAT and VCC_VBAT at J8.

Note: The level translator, U17, consumes approximately 110 uA and adds this leakage when measuring across VDDIO_WL. Therefore, remove U17 which is on the back of the board below J3.1. In addition, remove R114 to disconnect WL_JTAG_SEL from VDDIO_WL.

CY8CPROTO-062-4343W

For PSoC™ 6 MCU:

1. Remove R65 on the right of the board close to the USB connector of the PSoC™ 6 MCU device.

2. Connect an ammeter between VTARG (J2.32) and P6_VDD (J2.24).

3. Remove R24 at the back of the board, below J1.9, to eliminate the leakage current.

   R24 is the pull-up resistor attached to the WL_HOST_WAKE pin P0_4, which leaks approximately 330 uA because P0_4 is driven LOW when there is no network activity. In total, the PSoC™ 6 MCU deep sleep current is approximately 350 uA.

For CYW4343W:

Measure the current at the VDDIO_1LV supply used for the SDIO communication interface, and at VBAT1 and VBAT2 supplies used for powering CYW4343W. VBAT1 and VABT2 are shorted to each other.

1. Remove R87 on the back of the board towards the right and above J2.33.

2. Connect an ammeter between the pads of R87 to measure the current.

3. Measure the current at VDDIO_1LV:

   1. Remove the resistor R86 on the back of the board below J1.27.

   2. Connect an ammeter between the pads of R86 to measure the current.

Note that the current at VDDIO_1LV depends on the SDIO transactions that happen because of the pull-up resistors on the lines to VDDIO_1LV. Also, VDDIO_1LV (named VDDIO_1DX in the carrier module (CY8CMOD_062_4343W) schematic) allows a current of 38 uA through R24 because WL_HOST_WAKE is LOW. This current needs to be deducted from the observed value of VDDIO_1LV.

CY8CKIT-062-WIFI-BT

For PSoC™ 6 MCU:

1. Measure the current by connecting an ammeter to the PWR MON jumper J8.

For CYW4343W:

1. Measure the current at WL_VDDIO used for the SDIO communication interface and at WL_VBAT used for powering CYW4343W.

2. Measure the current at WL_VBAT by removing L3 along the right edge of the board close to the CYW4343W module and connecting an ammeter between the pads of L3.

3. Measure the current at WL_VDDIO by removing L7 on the top left corner of the back of the board, and connecting an ammeter between the pads of L7.

Typical current measurement values

The following table provides the typical current measurement values for the CY8CKIT-062S2-43012 kit. All measurements were made in the presence of external radio interference and not in an isolated environment with a single AP. Note that the typical values of current consumed by the supply powering the SDIO interface between the host MCU and WLAN device are not provided because the value of current varies with the transaction over the interface.

Here, PSoC™ 6 MCU is operated with Arm® Cortex®-M4 running at 50 MHz in ultra-low-power (ULP) mode with full RAM retention.

Table 1. Typical current values for CY8CKIT_062S2_43012

State	Device	Current
Deep sleep	PSoC™ 6 MCU	12.6 uA
	CYW43012 (VBAT)	2.4 uA
Average current over 3 DTIM periods for AP (2.4 GHz) beacon interval of 100 and AP DTIM of 1	PSoC™ 6 MCU	14 uA
	CYW43012 (VBAT)	317.5 uA
Average current over 3 DTIM periods for AP (2.4 GHz) beacon interval of 100 and AP DTIM of 3	PSoC™ 6 MCU	14 uA
	CYW43012 (VBAT)	112.6 uA
Average current over 3 DTIM periods for AP (5 GHz) beacon interval of 100 and AP DTIM of 1	PSoC™ 6 MCU	14 uA
	CYW43012 (VBAT)	279.2 uA
Average current over 3 DTIM periods for AP (5 GHz) beacon interval of 100 and AP DTIM of 3	PSoC™ 6 MCU	14 uA
	CYW43012 (VBAT)	69.2 uA

Related resources

Resources	Links
Application notes	AN228571 – Getting started with PSoC™ 6 MCU on ModusToolbox™ AN215656 – PSoC™ 6 MCU: Dual-CPU system design
Code examples	Using ModusToolbox™ on GitHub
Device documentation	PSoC™ 6 MCU datasheets PSoC™ 6 technical reference manuals
Development kits	Select your kits from the Evaluation board finder.
Libraries on GitHub	mtb-pdl-cat1 – PSoC™ 6 Peripheral Driver Library (PDL) mtb-hal-cat1 – Hardware Abstraction Layer (HAL) library retarget-io – Utility library to retarget STDIO messages to a UART port
Middleware on GitHub	capsense – CAPSENSE™ library and documents psoc6-middleware – Links to all PSoC™ 6 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.

For PSoC™ 6 MCU devices, see How to design with PSoC™ 6 MCU - KBA223067 in the Infineon Developer community.

Document history

Document title: CE230106 – WLAN low power

Version	Description of change
1.0.0	New code example
1.1.0	Minor changes in Makefile and source files
2.0.0	Major update to support ModusToolbox™ v2.2 and LPA v3.0.0. This version is not backward compatible with ModusToolbox™ v2.1.
2.1.0	Added support for Rapid IoT Connect Developer Kit (CYSBSYSKIT-DEV-01)
2.2.0	Updated to FreeRTOS v10.3.1
2.3.0	Added support for new kits
3.0.0	Updated to BSP v3.X and added support for new kits
4.0.0	Major update to support ModusToolbox™ v3.0. This version is not backward compatible with previous versions of ModusToolbox™.
4.1.0	Updated to low power assistant (LPA) middleware v4.x and added support for CY8CEVAL-062S2-LAI-43439M2
4.2.0	Added support for CY8CPROTO-062S2-43439
4.3.0	Added support for CY8CEVAL-062S2-CYW43022CUB and updated to use low power assistant (LPA) middleware v5.x
4.4.0	Added support for CY8CKIT-062S2-AI
4.5.0	Added support for CY8CEVAL-062S2-CYW955513SDM2WLIPA

---

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