This code example demonstrates the UART transmit and receive operation on PMG1-S3 device using DMA. The application uses a serial terminal to read data and echoes what is received. The UART is configured to do both transmit and receive operations.
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: EZ-PD™ PMG1 S3 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-S3 prototyping kit (
PMG1-CY7113) - Default value ofTARGET
For kit version older than CY7113 board revision 3 or lower, connect J6.10 to J3.8 and J6.9 to J3.10 to establish a UART connection between KitProg3 and the PMG1 device. See the kit user guide to ensure that the board is configured correctly. Prototyping kits with a higher revision have UART lines internally connected. Therefore, external wiring is not required.
Note: If UART DEBUG PRINT messages are enabled, UART connection are needed. Please view compile-time configuration for more information.
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.
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 "SCB UART transmit and receive with DMA" application with the desired name "MyScbUartDma" configured for the PMG1-CY7113 BSP into the specified working directory, C:/mtb_projects:
project-creator-cli --board-id PMG1-CY7113 --app-id mtb-example-pmg1-uart-transmit-receive-dma --user-app-name MyScbUartDma --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 |
The following example adds the PMG1-CY7113 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/MyMyScbUartDma" --add-bsp-name PMG1-CY7113--add-bsp-version "latest-v3.X" --add-bsp-location "local"
~/ModusToolbox/tools_3.0/library-manager/library-manager-cli --project "C:/mtb_projects/MyMyScbUartDma" --set-active-bsp APP_PMG1-CY7113
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 the 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 connector. This cable is used for programming the PMG1 device and as a USB-UART bridge to the PC during operation.
-
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 the power selection jumper (J5) to 1-2 to power the kit through the USBPD port.
-
Connect the USB cable back to the KitProg3 USB connector.
-
Open a terminal program and select the KitProg3 COM port. Set the serial port parameters to 8N1 and 115200 baud.
-
Connect the USBPD port to a USB-C power adapter or your PC using a USB Type-C cable to power the kit.
-
The application starts automatically. Confirm that "<CE Title>" is displayed on the UART terminal.
-
Start typing to see the echo on the terminal:
Figure 1. Sample output
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 connector and the jumper shunt on the 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.
Figure 2 shows the firmware flowchart for the design.
Figure 2. Firmware flowchart
SCB4 is initialized as UART to receive and send data to a terminal emulator. To implement the UART data transfer on the SCB hardware block, the UART Peripheral Driver Library (PDL) APIs are used. The UART is initialized with the following settings:
- Baud rate: 115200
- Data width: 8 bits
- Parity: None
- Stop bit: 1
- The clock input of the block is connected to a 48-MHz PERI-derived clock
Figure 3. UART configuration
Figure 4. UART configuration (continued)
The application uses DMA to handle the data received in the UART Rx FIFO. Two DMA channels (DMAC Channel 0 and DMAC Channel 1) are used to handle the data in receive and transmit directions respectively. Two SRAM buffers are alternately used on the receive side to hold the data received from the UART terminal. These buffers are called "ping-pong buffers" and are mainly used to provide the time for pulling the data out of either buffer.
Each DMA Channel has one or more channel descriptor structures which are normally located in the RAM. These descriptors include source and destination addresses for the channel as well as the information on the data count, data transfer width, trigger type, etc. For more information on DMAC block configuration and usage, see mtb-pdl-cat2 DMAC documentation.
PMG1-S3 has 16 DMA channels. To configure or enable these DMA channels, click Device Configurator 3.0 under Tools in the Quick Panel and click on DMA tab as shown in the following figure:
Figure 5. DMA configuration
The RxDma (DMAC Channel 0) resource handles the data transfer in the receive direction. RxDma has two descriptors in the chain; these are configured such that the source alternates between the ping-pong buffers in the receive direction. RxDma channel and 2 descriptors (ping-pong) are configured as follows:
Figure 6. RxDma channel configuration
The TxDma (DMAC Channel 1) resource is used to handle the data in the transmit direction. TxDma has only one descriptor; the source address for this channel is alternated between ping-pong buffers upon reception of each byte of data to transmit back the correct value. TxDma channel is configured as follows:
Figure 7. TxDma channel configuration
The data received from the serial terminal is echoed back to the serial terminal.
Figure 8. Buffering
The EZ-PD™ PMG1 MCU SCB UART transmit and receive with DMA application functionality can be customized through the 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 | 1u to enable 0u to disable |
Table 1. Application resources
| Resource | Alias/object | Purpose |
|---|---|---|
| SCB(UART)(PDL) | KIT_UART | UART object used for Debug UART port |
| DMA (PDL) | RxDma | Data transfer |
| DMA (PDL) | TxDma | Data transfer |
| File | Purpose |
|---|---|
| source/UartDma.h | Defines function prototypes and macros to configure DMA channels and handle transfers |
| source/UartDma.c | Implements functions to configure DMA channels and handle transfers |
| 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: CE233719 – EZ-PD™ PMG1 MCU: SCB UART transmit and receive with DMA
| 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, 2022-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.