Skip to content

Latest commit

 

History

History

PSoC6_WiFi_HTTPS_Server

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
.vscode
.vscode
 
 
bsps/TARGET_APP_CY8CEVAL-062S2-LAI-4373M2
bsps/TARGET_APP_CY8CEVAL-062S2-LAI-4373M2
 
 
configs
configs
 
 
deps
deps
 
 
images
images
 
 
libs
libs
 
 
source
source
 
 
templates/TARGET_CY8CKIT-064B0S2-4343W/COMPONENT_CM4
templates/TARGET_CY8CKIT-064B0S2-4343W/COMPONENT_CM4
 
 
.cyignore
.cyignore
 
 
.mtbqueryapi
.mtbqueryapi
 
 
ExampleWebpage.png
ExampleWebpage.png
 
 
LICENSE
LICENSE
 
 
Makefile
Makefile
 
 
PSoC6_WiFi_HTTPS_Server.code-workspace
PSoC6_WiFi_HTTPS_Server.code-workspace
 
 
README.md
README.md
 
 
generate_ssl_certs.sh
generate_ssl_certs.sh
 
 
mysecurehttpclient.crt
mysecurehttpclient.crt
 
 
mysecurehttpclient.key
mysecurehttpclient.key
 
 
mysecurehttpclient.pfx
mysecurehttpclient.pfx
 
 
mysecurehttpserver.local.crt
mysecurehttpserver.local.crt
 
 
mysecurehttpserver.local.key
mysecurehttpserver.local.key
 
 
openocd.tcl
openocd.tcl
 
 
root_ca.crt
root_ca.crt
 
 
root_ca.key
root_ca.key
 
 
root_ca.srl
root_ca.srl
 
 

README.md

Infineon PSoC6 wolfSSL HTTPS Server Example (using wolfTPM)

Tested on PSoC 62S2 eval kit (CY8CEVAL-062S2) and Sterling LWB5+ Wifi module.

The wolfTPM support for updating Infineon SLB9672/SLB9673 firmware was added here: wolfSSL/wolfTPM#339

Based on the Wi-Fi_HTTPS_Server example. TLS ported to wolfSSL. TPM uses wolfTPM

Build steps:

  • make getlibs
  • Update ../mtb_shared/secure-sockets with Infineon/secure-sockets#1
  • Update ../mtb_shared/wpa3-external-supplicant with Infineon/wpa3-external-supplicant#2
  • Update bsps/TARGET_APP_CY8CEVAL-062S2-LAI-4373M2/config/GeneratedSource/cycfg_system.h -> #define CY_CFG_PWR_DEEPSLEEP_LATENCY 125UL.
  • Update source/secure_http_server.h WiFi settings (WIFI_SSID and WIFI_PASSWORD)
  • make build -j8
  • make program
  • See wolfTPM Firmware Example for next steps

HTTPS server

This code example demonstrates the implementation of an HTTPS server with PSoC™ 6 MCU and AIROC™ CYW43xxx Wi-Fi & Bluetooth® combo chips.

It employs the HTTPS server middleware library, which takes care of all the underlying socket connections with the HTTPS client. In this example, the HTTPS server establishes a secure connection with an HTTPS client through an SSL handshake. After the SSL handshake completes successfully, the HTTPS client can make GET, POST, and PUT requests with the server.

View this README on GitHub.

Provide feedback on this code example.

Requirements

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

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.

Note: This code example also uses the cURL utility to test the HTTPS server. This utility helps to send HTTPS GET, POST, and PUT requests to the server. The cURL utility (version 7.59.0) is already shipped with the ModusToolbox™ software v2.2 or later; it is available under {ModusToolbox™ install directory}/tools_<version>/modus-shell/bin).

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 "Hello world" application with the desired name "MyHelloWorld" 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-psoc6-hello-world --user-app-name MyHelloWorld --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

If using a PSoC™ 64 "Secure" MCU kit (like CY8CKIT-064B0S2-4343W), the PSoC™ 64 device must be provisioned with keys and policies before being programmed. Follow the instructions in the "Secure Boot" SDK user guide to provision the device. If the kit is already provisioned, copy-paste the keys and policy folder to the application folder.

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

  2. Open secure_http_server.h and modify the WIFI_SSID, WIFI_PASSWORD, and WIFI_SECURITY_TYPE macros to match the credentials of the Wi-Fi network that you want to connect to.

    All possible security types are defined in the cy_wcm_security_t structure in the cy_wcm.h file.

  3. Because this code example uses a self-signed SSL certificate, you need to generate the certificates required by the HTTPS server and client so that they can successfully establish a secure HTTPS connection. Follow the steps provided in a separate section that explains how to generate the certificates.

  4. Open the source/secure_keys.h file and do the following:

    1. Modify keySERVER_CERTIFICATE_PEM with the contents from the mysecurehttpserver.local.crt file generated in Step 3.
    2. Modify keySERVER_PRIVATE_KEY_PEM with the contents from the mysecurehttpserver.local.key file generated in Step 3.
    3. Modify keyCLIENT_ROOTCA_PEM with the contents from the rootCA.crt file generated in Step 3.

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

  6. Program the board using one of the following:

    Using Eclipse IDE for ModusToolbox™ software

    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

  7. After programming, the application starts automatically. Verify that the following logs appear on the serial terminal:

    Info: ===================================
Info: HTTPS Server
Info: ===================================

WLAN MAC Address : A0:C9:A0:3D:D3:6A
WLAN Firmware    : wl0: Jan 30 2020 21:41:53 version 7.45.98.95 (r724303 CY) FWID 01-5afc8c1e
WLAN CLM         : API: 12.2 Data: 9.10.39 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2020-01-30 21:30:05
WHD VERSION      : v1.90.2 : v1.90.2 : GCC 7.2 : 2020-04-13 02:49:57 -0500
Info: Wi-Fi initialization is successful
Info: Join to AP: WIFI_SSID
Info: Successfully joined Wi-Fi network WIFI_SSID
Info: Assigned IP address: 192.168.0.12
Info: HTTPS server has successfully started. The server is running at URL https://mysecurehttpserver.local:50007

  8. The client needs to install rootCA.crt to trust the HTTPS website and its own certificate mysecurehttpclient.pfx. The .pfx file bundles the client certificate and key in PKCS format.

    Do the following to install the certificates on the client machine. In this code example, the HTTPS server has two types of clients: one uses the cURL utility while the other uses a web browser.

    • cURL utility:

      • Ensure that the cURL utility has access to the rootCA.crt, mysecurehttpclient.crt, and mysecurehttpclient.key files generated in Step 3 of the operation section. cURL commands can be invoked from anywhere in the modus-shell. The command takes the argument such as --cacert, --cert, and --key, which indicates the file path to rootCA.crt, mysecurehttpclient.crt, and mysecurehttpclient.key respectively.

    • Web browser:

      • Mozilla Firefox:

        1. Select Options > Privacy & Security (Windows) or Preferences > Privacy & Security (macOS and Ubuntu).

        2. Find the Certificates section and then click View Certificates.

          The browser displays the Certificate Manager dialog.

        3. Click Import and select the rootCA.crt file generated in Step 3 of the operation section and click Open.

        4. Trust this certificate authority to identify websites and email users and click OK.

          The rootCA.crt is now installed.

        5. Similarly, import the client certificate mysecurehttpclient.pfx file, generated in Step 3 of the operation section, under Your Certificates on the Certificate Manager window. The certificate was generated with an empty password; therefore, leave it empty if it asks for a password during import.

      • Google Chrome and Internet Explorer on Windows:

        1. In the Run dialog (click Win key + R), type certmgr.msc and click OK.

          The Windows Certificate Manager application opens.

        2. Navigate to the Trusted Root Certification Authorities/Certificates folder.

        3. Go to Action > All Tasks > Import and click Next.

        4. Select the rootCA.crt file generated in Step 3 of the operation section. Make sure to change the file type to All Files to find the rootCA.crt file. Click Open.

        5. Select the certification store as Trusted Root Certification Authorities and click Finish.

        6. Click Yes to the security warning window to acknowledge that you trust rootCA.crt to allow its websites and email users.

          The rootCA.crt is now installed.

        7. Similarly, import the client certificate mysecurehttpclient.pfx file, generated in Step 3 of the operation section, under the Personal category.

      • Google Chrome (Ubuntu):

        1. Select Settings > Show Advanced Settings > HTTPS/SSL. Click Manage Certificates under the Security tab.

        2. In the Certificate Manager window, click Import under the Authorities tab.

        3. Select the rootCA.crt file generated in Step 3 of the operation section. Make sure to change the file type to All Files to find the rootCA.crt file. Click Open.

        4. Trust this certificate authority to identify websites and email users and click OK.

          The rootCA.crt is now installed.

        5. Similarly, import the client certificate mysecurehttpclient.pfx file, generated in Step 3 of the operation, under the Personal category.

      • Google Chrome (macOS):

        1. Open Finder > Applications > Utilities > Keychain Access.

        2. Select the System keychain.

        3. Open File > Import Items, and import the certificate file rootCA.crt, generated in Step 3 of the operation section, into the System keychain.

        4. Right-click the certificate and select Get Info.

          A certificate information window appears.

        5. Expand the Trust category and select Always Trust to trust this certificate authority.

        6. Similarly, import the client certificate mysecurehttpclient.pfx file, generated in Step 3 of the operation section, under MyCertificates category. The certificate was generated with an empty password; therefore, leave it empty if it asks for a password.

      Notes:

      • Browsers might need a restart after importing the certificate.

      • When importing the mysecurehttpclient.pfx file, the Chrome browser asks the user to set the CryptoAPI Private Key to protect the client certificate key from accessing it by the browser. The browser is given access to the client's private key only after entering the correct key and allowing access by the user.

  9. Ensure that your PC is connected to the same Wi-Fi access point that you have configured in Step 2.

  10. Enter https://mysecurehttpserver.local:50007 in the web browser to access the HTTPS server webpage.

Test the HTTPS server

Using a web browser:

  1. Enter the URL https://mysecurehttpserver.local:50007. This opens the HTML page; it will look as follows:

    Figure 1. HTTPS web page

  2. Click Get LED status to send an HTTPS GET command to the server running on the kit.

    The server returns the current LED status on the kit as a response. Note that entering the URL itself will send a GET command to the server to get the HTML page.

  3. Click Toggle LED to send an HTTPS POST command to the server running on the kit.

    The server acts on the command request and toggles the LED on the kit.

Using the cURL utility:

  1. Open modus-shell application ({ModusToolbox™ install directory}/tools_<version>/modus-shell/Cygwin.bat).

  2. Set the path to rootCA.crt, mysecurehttpclient.crt, and mysecurehttpclient.key in a variable:

    PATH_TO_ROOTCA="<Path to rootCA.crt file>"

    PATH_TO_CLIENT_CRT="<Path to mysecurehttpclient.crt file>"

    PATH_TO_CLIENT_KEY="<Path to mysecurehttpclient.key file>"

  3. Set the path to the HTTPS web page URL in a variable:

    HTTPS_SERVER_URL="https://mysecurehttpserver.local:50007"

    where mysecurehttpserver.local is the HTTPS server domain name; 50007 is the HTTPS port number defined in the secure_http_server.h file in the HTTPS_PORT macro.

  4. Use the following cURL commands to test HTTPS commands with the HTTPS server:

    1. HTTPS GET: Get the kit's LED status (ON or OFF).

      curl --cacert $PATH_TO_ROOTCA --cert $PATH_TO_CLIENT_CRT --key $PATH_TO_CLIENT_KEY -X GET $HTTPS_SERVER_URL --output -

    2. Verify that the HTTPS server responds with the following HTML output. This contains the LED status (ON or OFF) of the kit:

      <!DOCTYPE html><html><head><title>HTTPS Server Demo</title></head><body><h1>HTTPS Server Demo</h1><form method="get"><fieldset><legend>HTTPS GET</legend><input type="submit" value="Get LED status"/><input type="text" name="led_status" value="OFF" size="3" readonly/></br></br></fieldset></br></form><form method="post"><fieldset><legend>HTTPS POST</legend><input type="submit" name="toggle_led" value="Toggle LED"/></br></br></fieldset></br></form></body></html>

    3. HTTPS POST: Toggle the LED (ON or OFF) on the :

      curl --cacert $PATH_TO_ROOTCA --cert $PATH_TO_CLIENT_CRT --key $PATH_TO_CLIENT_KEY -X POST $HTTPS_SERVER_URL --output -

    4. Verify that the HTTPS server responds with the following HTML output. The response contains the LED status (ON or OFF) of the last GET request:

      <!DOCTYPE html><html><head><title>HTTPS Server Demo</title></head><body><h1>HTTPS Server Demo</h1><form method="get"><fieldset><legend>HTTPS GET</legend><input type="submit" value="Get LED status"/><input type="text" name="led_status" value="OFF" size="3" readonly/></br></br></fieldset></br></form><form method="post"><fieldset><legend>HTTPS POST</legend><input type="submit" name="toggle_led" value="Toggle LED"/></br></br></fieldset></br></form></body></html>

    5. HTTPS PUT: Register a new HTTP resource. The HTTPS server creates a new resource called myhellomessage:

      curl --cacert $PATH_TO_ROOTCA --cert $PATH_TO_CLIENT_CRT --key $PATH_TO_CLIENT_KEY -X PUT -d "/myhellomessage=Hello!" $HTTPS_SERVER_URL --output -

    6. Verify the newly created resource by sending an HTTPS GET request:

      curl --cacert $PATH_TO_ROOTCA --cert $PATH_TO_CLIENT_CRT --key $PATH_TO_CLIENT_KEY -X GET $HTTPS_SERVER_URL/myhellomessage --output -

    7. Verify that the HTTPS server responds with a 'Hello' text message:

      Hello!

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.

Known issues

An issue has been observed with the multicast domain name system (mDNS) when the device joins the home AP (D-Link DIR-816 and TP-Link Archer C20 APs). To work around this issue, connect the kit to a mobile hotspot if the device reports the following error when joining the AP.

Info: Wi-Fi initialization is successful
Info: Join to AP: WIFI_SSID
Function whd_wifi_unregister_multicast_address failed at line 2834 checkres = 101580800
Received buffer request ID: 42 (expectation: 42)
whd_cdc_send_ioctl is already timed out, drop the buffer

This issue will be addressed in a future update of this code example.

Design and implementation

Resources and settings

Table 1. Application resources

Resource Alias/object Purpose
UART (HAL) cy_retarget_io_uart_obj UART HAL object used by retarget-io for Debug UART port
GPIO (HAL) CYBSP_USER_LED User LED

This example uses the Arm® Cortex®-M4 (CM4) CPU of PSoC™ 6 MCU to start the HTTPS server task. At device reset, the default Cortex®-M0+ (CM0+) application enables the CM4 CPU and configures the CM0+ CPU to go to sleep.

In this example, the HTTPS server establishes a secure connection with a web browser or cURL client through an SSL handshake. During the SSL handshake, the server presents its SSL certificate for verification and verifies the incoming client identity. This example uses mDNS provided by the lwIP open-source TCP/IP network stack. mDNS helps in resolving the domain name of the HTTPS server to an IP address in the local network. This code example supports only IPv4 with mDNS.

You can define the maximum number of HTTPS page resources for the HTTPS server in the application Makefile, as shown below. The HTTPS server library maintains the database of pages based on this value.

DEFINES+=MAX_NUMBER_OF_HTTP_SERVER_RESOURCES=10

Note that if the MAX_NUMBER_OF_HTTP_SERVER_RESOURCES value is not defined in the application Makefile, the HTTPS server will set it to 10 by default. This code example does not define this parameter in the application Makefile; therefore, the application uses the default value of 10. This depends on the availability of memory on the MCU device.

Creating a self-signed SSL certificate

The HTTPS server demonstrated in this example uses a self-signed SSL certificate. This requires OpenSSL which is already preloaded in the ModusToolbox™ installation. A Self-signed SSL certificate means that there is no third-party certificate issuing authority, commonly referred to as CA, involved in the authentication of the server. Clients connecting to the server must have a root CA certificate to verify and trust the websites defined by the certificate. Only when the client trusts the website, it can establish a secure connection with the HTTPS server.

Do the following to generate a self-signed SSL certificate:

Generate an SSL certificate and private key

Run the following script to generate the self-signed SSL certificate and private key.

Before invoking the following command, modify the OPENSSL_SUBJECT_INFO macro in the generate_ssl_certs.sh file to match your local domain configuration such as Country, State, Locality, Organization, Organization Unit name, and Common Name. This macro is used by the openssl commands when generating the certificate.

./generate_ssl_certs.sh

This will produce the following files:

File Description
mysecurehttpserver.local.crt HTTPS server certificate
mysecurehttpserver.local.key HTTPS server private key
rootCA.crt HTTPS server rootCA certificate to trust the client
rootCA.key HTTPS server root key used for signing the certificate
mysecurehttpclient.crt HTTPS client certificate
mysecurehttpclient.key HTTPS client key
mysecurehttpclient.pfx Bundles the HTTPS client certificate and key in PKCS12 format

The HTTPS server should be configured to take mysecurehttpserver.local.crt as the certificate, mysecurehttpserver.local.key as the private key, and rootCA.crt as the rootCA certificate.

You can either convert the values to strings manually following the format shown in source/secure_keys.h or use the HTML utility available here to convert the certificates and keys from PEM format to C string format. You need to clone the repository from GitHub to use the utility.

The rootCA.crt and mysecurehttpclient.pfx should be installed on the web browser clients which are trying to communicate with the HTTPS server. With cURL, the rootCA.crt, mysecurehttpclient.crt, and mysecurehttpclient.key can be passed as command-line arguments.


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 psoc6-middleware – Links to all PSoC™ 6 MCU middleware
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.

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: CE230422 - HTTPS server

Version Description of change
1.0.0 New code example
2.0.0 Major update to support ModusToolbox™ v2.2
Updated the application flow to handle HTTPS PUT request differently
This version is not backward compatible with ModusToolbox™ v2.1
2.1.0 Updated to support FreeRTOS 10.3.1
2.2.0 Added support for the kit CY8CEVAL-062S2-LAI-4373M2
Adding fixes for mDNS errors
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 Added support for the kit CY8CKIT-064B0S2-4343W and CY8CEVAL-062S2-LAI-43439M2
4.2.0 Added support for KIT_XMC72_EVK_MUR_43439M2
Updated to support mbedtls v3.4.0 and ModusToolbox™ v3.1.
4.3.0 Added support for CY8CEVAL-062S2-CYW43022CUB

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