This example demonstrates how to use the smart IO peripheral in PSoC™ 4 to invert the output of the serial communication block (SCB) SPI slave select signal. This method can be used for any of the SCB unidirectional signals to invert the signal polarity.
Provide feedback on this code example.
-
ModusToolbox™ v3.1 or later (tested with v3.1)
-
Board support package (BSP) minimum required version: 3.1.0
-
Programming language: C
-
Associated parts: PSoC™ 4000S, PSoC™ 4100S Plus, PSoC™ 4500S, PSoC™ 4100S Max
- 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™ 4100S Max Pioneer Kit (
CY8CKIT-041S-MAX) - Default value ofTARGET - PSoC™ 4100S Plus Prototyping Kit (
CY8CKIT-149) - PSoC™ 4000S CAPSENSE™ Prototyping Kit (
CY8CKIT-145-40XX) - PSoC™ 4500S Pioneer Kit (
CY8CKIT-045S)
This example uses the board's default configuration. See the kit guide to ensure that the board is configured correctly.
- For CY8CKIT-041S-MAX, CY8CKIT-149, and CY8CKIT-145-40XX connect SS0_Pin [P2.4] and SS1_Pin [P2.5] to an oscilloscope.
Note: These pins are connected to the user LEDs (LED8 and LED1) on CY8CKIT-145-40XX.
- For CY8CKIT-045S, connect SS0_Pin [P3.4] and SS1_Pin [P3.5] to an oscilloscope.
Note: Some of the PSoC™ 4 kits 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".
See the ModusToolbox™ tools package installation guide for information about installing and configuring the tools package.
This example requires no additional software or tools.
- The smart IO peripheral is a port-wide resource; you must define its port before it can be used.
Note: For kits CY8CKIT-041S-MAX, CY8CKIT-149, and CY8CKIT-145-40XX, the smart IO port is Port 2. For CY8CKIT-045S, the smart IO port is Port 3.
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 "mtb-example-psoc4-spi-slave-select-inversion-with-smartio" application with the desired name "SPISlaveInversionSmartIO" configured for the CY8CKIT-149 BSP into the specified working directory, C:/mtb_projects:
project-creator-cli --board-id CY8CKIT-149 --app-id mtb-example-psoc4-spi-slave-select-inversion-with-smartio --user-app-name SPISlaveInversionSmartIO --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 USB cable through the KitProg3 USB connector.
-
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).
In other IDEs
Follow the instructions in your preferred IDE.
Using CLI
From the terminal, execute the
make programcommand to build and program the application using the default toolchain to the default target. The default toolchain is specified in the application's Makefile but you can override this value manually:make program TOOLCHAIN=<toolchain>Example:
make program TOOLCHAIN=GCC_ARM -
-
After programming the project into the kit, and observe on the oscilloscope that the signal on SS0_Pin [P2.4] exhibits an active high behavior. Also observe that SS1_Pin [P2.5] exhibits an active low behavior and produces a signal that is of opposite polarity to SS0_Pin.
-
For CY8CKIT-045S, SS0_Pin is P3.4 and SS1_Pin is P3.5.
You can debug the example to step through the code.
In Eclipse IDE
Use the <Application Name> Debug (KitProg3_MiniProg4) configuration in the Quick Panel. For details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ user guide.
In other IDEs
Follow the instructions in your preferred IDE.
The SCB peripheral is configured as a SPI master with two slave select pin connections exposed as symbol terminals. The MOSI, MISO and SCLK pins are not used in this design. The slave select terminals are connected to chip4 and chip5 terminals of the smart IO peripheral. The slave select configurations are active low. The smart IO peripheral is configured to take the chip4 signal, invert it through LUT4 and then output to gpio4. It then takes the chip5 slave select signal and replicates it to gpio5 by using LUT6. The gpio4 and gpio5 terminals are connected to the SS0_Pin and SS1_Pin respectively.
The firmware for the peripheral is implemented in main.c and perform the following functions:
- Starts the smart IO peripheral
- Starts the SCB peripheral
- Selects the slave on ss1 sends sample data
- Selects the slave on ss2 sends sample data
This code example is designed for the specified ports on the stated devices. The design is portable to other PSoC™ 4 devices with smart IO, but it may require LUT reconfiguration due to the close relationship between the device port and the peripheral.
Note: SCB connections use a dedicated channel and cannot be routed to other GPIO pins using the smart IO peripheral. If an SCB connection is located on chip then it must connect to gpio4.
The smart IO peripheral is configured to route chip4 to gpio4 through LUT4, as shown in Figure 1. It is also configured to route chip5 to gpio5 through LUT5.
Figure 1. Smart IO routing configuration
Figure 2 shows the LUT configurations.The LUTs are configured in “combinatorial” mode. LUT4 is configured to invert the input signal, whereas LUT5 is configured to repeat the input signal. These settings are located in the individual LUT tabs in the configuration dialog.
Figure 2. Smart IO LUT configuration
Table 1. Application resources
| Resource | Alias/object | Purpose |
|---|---|---|
| SCB (SPI) | mSPI_HW | SPI master driver to communicate with the SPI slave |
| Smart I/O | SmartIO | Perform simple logic operations on peripheral and GPIO signals at the GPIO port |
| GPIO | SS0_Pin | To generate signals on oscilloscope |
| GPIO | SS1_Pin | To generate signals on oscilloscope |
| Resources | Links |
|---|---|
| Application notes | AN79953 – Getting started with PSoC™ 4 |
| Code examples | Using ModusToolbox™ on GitHub |
| Device documentation | PSoC™ 4 datasheets PSoC™ 4 technical reference manuals |
| Development kits | Select your kits from the Evaluation board finder page. |
| Libraries on GitHub | mtb-pdl-cat2 – PSoC™ 4 Peripheral Driver Library (PDL) mtb-hal-cat2 – Hardware Abstraction Layer (HAL) library |
| 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. |
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: CE236712 - PSoC™ 4 : SPI slave select inversion with smart IO
| Version | Description of change |
|---|---|
| 1.0.0 | New code example |
| 1.1.0 | Added support for CY8CKIT-045S and updated to support ModusToolbox™ v3.1. |
© 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 respective owners.