This example demonstrates the use of a SPI resource of the PMG1 MCU in slave mode. The SPI slave is configured to receive command packets from an SPI master. The slave's LED is activated depending on the command packet received from the master.
This code example needs a SPI master for operation. The SPI master is configured to send packets to SPI slave that controls the slave user LED. A second PMG1 kit is recommended for testing this code example.
Provide feedback on this code example.
- ModusToolbox™ software v3.0 or later (tested with v3.0)
- Board support package (BSP) minimum required version: 3.0.0
- Programming language: C
- Associated parts: All EZ-PD™ PMG1 MCU parts
- GNU Arm® Embedded Compiler v10.3.1 (
GCC_ARM) - Default value ofTOOLCHAIN - Arm® Compiler v6.13 (
ARM) - IAR C/C++ Compiler v8.42.2 (
IAR)
- EZ-PD™ PMG1-S0 prototyping kit (
PMG1-CY7110) - Default value ofTARGET - EZ-PD™ PMG1-S1 prototyping kit (
PMG1-CY7111) - EZ-PD™ PMG1-S2 prototyping kit (
PMG1-CY7112) - EZ-PD™ PMG1-S3 prototyping kit (
PMG1-CY7113)
This code examples uses two kits: one kit as slave device listed in Supported Kits and another kit as master device from the code example CE233902 - PMG1 SPI master Supported-kits
This example uses the board's default configuration. See the kit user guide to ensure that the board is configured correctly.
- Use jumper wires to establish a connection between the master and the slave. The pin assignments for the master and slave devices for the different supported kits are listed in Table 1.
Table 1. Pin identification for SPI slave and master kit
| Development kit | MOSI | MISO | SCLK | CS | Ground |
|---|---|---|---|---|---|
| PMG1-S0 | P1[2] / J6.10 | P1[1] / J7.12 | P1[3] / J6.9 | P1[0] / J7.11 | GND / J6.14 |
| PMG1-S1 | P5[0] / J7.7 | P5[1] / J7.6 | P3[0] / J7.11 | P2[2] / J7.15 | GND / J6.17 |
| PMG1-S2 | P2[5] / J7.5 | P0[1] / J7.6 | P2[6] / J7.8 | P0[0] / J7.7 | GND / J6.17 |
| PMG1-S3 | P4[1] / J7.6 | P2[4] / J6.14 | P4[0] / J7.7 | P2[1] / J6.16 | GND / J6.18 |
Table 2. Signal connections between master and slave kits
| Master | Slave |
|---|---|
| MOSI | MOSI |
| MISO | MISO |
| SCLK | SCLK |
| CS | CS |
| GND | GND |
- If UART DEBUG PRINT messages are enabled, UART connection are needed. Pin connections for UART is as shown in the below table. For the following revisions of the PMG1 prototyping kits, connect the UART Tx and UART Rx lines from the PMG1 kit to J3.8 and J3.10 on KitProg3 respectively to establish a UART connection between KitProg3 and the PMG1 device.
Table 3. Pin connections for UART
| PMG1 kit | UART Tx | UART Rx |
|---|---|---|
| PMG1-CY7110 | --- | --- |
| PMG1-CY7111 (revision 2 or lower) | J6.10 to J3.8 | J6.9 to J3.10 |
| PMG1-CY7112 (revision 2 or lower) | J6.10 to J3.8 | J6.9 to J3.10 |
| PMG1-CY7113 (revision 3 or lower) | J6.10 to J3.8 | J6.9 to J3.10 |
Notes:
-
All prototyping kits with a higher revision have UART lines internally connected. Therefore, external wiring is not required.
-
UART is disabled for PMG1-S0 kit in this code example because both the kit UART and the kit SPI uses the same SCB 1 block on the PMG1-S0 kit.
-
For more information on UART DEBUG PRINT please, refer compile-time configuration.
This example requires no additional software or tools.
Create the project and open it using one of the following:
In Eclipse IDE for ModusToolbox™ software
-
Click the New Application link in the Quick Panel (or, use File > New > ModusToolbox™ Application). This launches the Project Creator tool.
-
Pick a kit supported by the code example from the list shown in the Project Creator - Choose Board Support Package (BSP) dialog.
When you select a supported kit, the example is reconfigured automatically to work with the kit. To work with a different supported kit later, use the Library Manager to choose the BSP for the supported kit. You can use the Library Manager to select or update the BSP and firmware libraries used in this application. To access the Library Manager, click the link from the Quick Panel.
You can also just start the application creation process again and select a different kit.
If you want to use the application 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.
-
In the Project Creator - Select Application dialog, choose the example by enabling the checkbox.
-
(Optional) Change the suggested New Application Name.
-
The Application(s) Root Path defaults to the Eclipse workspace which is usually the desired location for the application. If you want to store the application in a different location, you can change the Application(s) Root Path value. Applications that share libraries should be in the same root path.
-
Click Create to complete the application creation process.
For more details, see the Eclipse IDE for ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mt_ide_user_guide.pdf).
In command-line interface (CLI)
ModusToolbox™ software provides the Project Creator as both a GUI tool and the command line tool, "project-creator-cli". The 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™ software 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™ software installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ software 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 "project-creator-cli" tool has the following arguments:
| Argument | Description | Required/optional |
|---|---|---|
--board-id |
Defined in the <id> field of the BSP manifest |
Required |
--app-id |
Defined in the <id> 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 |
The following example clones the "SPI slave" application with the desired name "MySPISlave" configured for the PMG1-CY7110 BSP into the specified working directory, C:/mtb_projects:
project-creator-cli --board-id PMG1-CY7110 --app-id mtb-example-pmg1-spi-slave --user-app-name MySPISlave --target-dir "C:/mtb_projects"
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™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mtb_user_guide.pdf).
To work with a different supported kit later, use the Library Manager to choose the BSP for the supported kit. You can invoke the Library Manager GUI tool from the terminal using make library-manager command or use the Library Manager CLI tool "library-manager-cli" to change the BSP.
The "library-manager-cli" tool has the following arguments:
| Argument | Description | Required/optional |
|---|---|---|
--add-bsp-name |
Name of the BSP that should be added to the application | Required |
--set-active-bsp |
Name of the BSP that should be as active BSP for the application | Required |
--add-bsp-version |
Specify the version of the BSP that should be added to the application if you do not wish to use the latest from manifest | Optional |
--add-bsp-location |
Specify the location of the BSP (local/shared) if you prefer to add the BSP in a shared path | Optional |
Following example adds the PMG1-CY7110 BSP to the already created application and makes it the active BSP for the app:
~/ModusToolbox/tools_3.0/library-manager/library-manager-cli --project "C:/mtb_projects/MySPIslave" --add-bsp-name PMG1-CY7110--add-bsp-version "latest-v3.X" --add-bsp-location "local"
~/ModusToolbox/tools_3.0/library-manager/library-manager-cli --project "C:/mtb_projects/MySPIslave" --set-active-bsp APP_PMG1-CY7110
In third-party IDEs
Use one of the following options:
-
Use the standalone Project Creator tool:
-
Launch Project Creator from the Windows Start menu or from {ModusToolbox™ software install directory}/tools_{version}/project-creator/project-creator.exe.
-
In the initial Choose Board Support Package screen, select the BSP, and click Next.
-
In the Select Application screen, select the appropriate IDE from the Target IDE drop-down menu.
-
Click Create and follow the instructions printed in the bottom pane to import or open the exported project in the respective IDE.
-
-
Use command-line interface (CLI):
-
Follow the instructions from the In command-line interface (CLI) section to create the application.
-
Export the application to a supported IDE using the
make <ide>command. -
Follow the instructions displayed in the terminal to create or import the application as an IDE project.
-
For a list of supported IDEs and more details, see the "Exporting to IDEs" section of the ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mtb_user_guide.pdf).
-
Ensure that the steps listed in the Hardware setup section are completed.
-
Ensure that the jumper shunt on power selection jumper (J5) is placed at position 2-3 to enable programming.
-
Connect the board to your PC using the USB cable through the KitProg3 USB Type-C port (J1).
-
Program the board using one of the following:
Using Eclipse IDE for ModusToolbox™ software
-
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 default toolchain and target are specified in the application's Makefile but you can override those values manually:make program TOOLCHAIN=<toolchain>Example:
make program TOOLCHAIN=GCC_ARM -
-
After programming the kit, disconnect the USB cable and change the position on power selection jumper (J5) to 1-2 to power the kit through the PMG1 USB PD sink port (J10).
-
Connect and program the master kit. See the CE233902 - PMG1 MCU: SPI master code example.
-
Power the slave kit first using a USB cable through the PMG1 USB PD sink port (J10). After this, power the master kit in the same way.
-
Confirm that the slave and the master kit's user LEDs blink at approximately 1 Hz.
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. Ensure that the board is connected to your PC using the USB cable through the KitProg3 USB Type-C port (J1) and the jumper shunt on power selection jumper (J5) is placed at position 1-2.
See the "Debug mode" section in the kit user guide for debugging the application on the CY7110 prototyping kit. For more details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ software user guide.
The program follows the logic shown in the next flowchart:
Figure 1. program flowchart
To implement the SPI data transfer on the SCB hardware block, the SPI APIs are used. The SPI is initialized with the following settings:
| SPI settings | Value |
|---|---|
| Name | sSPI |
| Mode | Slave |
| Sub Mode | Motorola |
| SCLK Mode | CPHA = 0, CPOL = 0 |
| Data rate | 1000 |
| Oversample | 16 |
| Bit order | MSB First |
| RX Data Width | 8 |
| TX Data Width | 8 |
| RX FIFO Level | 7 |
| TX FIFO Level | 7 |
Figure 2. SPI configuration
The master sends the command to control the status of the LED every 1 second. The command has a StartOfPacket (SOP) followed by the LED status and an EndOfPacket (EOP). This command is decoded by the slave and sets the LED status only if the SOP and EOP and received correctly.
| SoP | LED status | EoP |
|---|---|---|
| 0x01 | 0x00 or 0x01 | 0x17 |
The slave sends the status packet as reply to the previous command. The command has a StartOfPacket (SOP) followed by the LED status and an EndOfPacket (EOP). This command is decoded by the master and sets the LED status only if the SOP and EOP and received correctly.
| SoP | LED status | EoP |
|---|---|---|
| 0x01 | 0x00 or 0x01 | 0x17 |
The EZ-PD™ PMG1 MCU SPI slave application functionality can be customized through a set of compile-time parameter that can be turned ON/OFF through the main.c file.
| Macro name | Description | Allowed values |
|---|---|---|
DEBUG_PRINT |
Debug print macro to enable UART print For S0 - Debug print will be always zero as SCB UART is not available |
1u to enable 0u to disable |
In this code example, the PMG1 SCB block is configured as a SPI master. The master sends a packet to the slave with a command to turn ON or turn OFF the user LED at an interval of 1 second. The packet consists of a start byte, a command byte, and an end byte. The start and end bytes are checked, and if the bytes are correct, the USER LED is controlled as per the command byte.
After this, the slave sends a status packet to the master with the current LED status. The master activates its LED depending on the status received. Therefore the master's LED blinks at the same rate as the slave's.
Table 3. Application resources
| Resource | Alias/object | Purpose |
|---|---|---|
| SCB (SPI) (PDL) | mSPI_HW | SPI slave driver to communicate with the SPI master |
| GPIO (PDL) | CYBSP_USER_LED | User LED |
| Resources | Links |
|---|---|
| Application notes | AN232553 – Getting started with EZ-PD™ PMG1 MCU on ModusToolbox™ software AN232565 – EZ-PD™ PMG1 hardware design guidelines and checklist |
| Code examples | Using ModusToolbox™ software on GitHub |
| Device documentation | EZ-PD™ PMG1 MCU datasheets |
| Development kits | Select your kits from the Evaluation Board Finder page. |
| Libraries on GitHub | mtb-pdl-cat2 – Peripheral driver library (PDL) and docs |
| Tools | Eclipse IDE for ModusToolbox™ software ModusToolbox™ software 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 & Bluetooth® combo 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: CE233903 – EZ-PD™ PMG1 MCU: SPI slave
| Version | Description of change |
|---|---|
| 1.0.0 | New code example |
| 2.0.0 | Major update to support ModusToolbox™ v3.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.
© Cypress Semiconductor Corporation, 2021-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, WICED, 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 cypress.com. Other names and brands may be claimed as property of their respective owners.