This repository contains examples and demos for PSoC 6 MCU family of devices, a single chip solution for the emerging IoT devices. PSoC 6 MCU bridges the gap between expensive, power hungry application processors and low‑performance microcontrollers (MCUs). The ultra‑low‑power, dual-core architecture of PSoC 6 MCU offers the processing performance needed by IoT devices, eliminating the tradeoffs between power and performance.
Cypress provides a wealth of data at www.cypress.com to help you select the right PSoC device and effectively integrate it into your design. Visit our PSoC 6 MCU webpage to explore more about PSoC 6 MCU family of device. Feel free to explore through the code example source files and let us innovate together!
This repository contains reference for developing PSoC 6 MCU designs using RTOS. The projects use FreeRTOS platform for developing the design. You can visit the FreeRTOS webpage to learn the concepts of RTOS.
If you are new to developing projects with PSoC 6 MCU, we recommend you to refer the PSoC 6 Getting Started GitHub page which can help you familiarize with device features and guides you to create a simple PSoC 6 design with PSoC Creator IDE. For other block specific design please visit the following GitHub Pages:
You can use these block level examples to guide you through the development of a system-level design using PSoC 6 MCU. All the code examples in this repository comes with well documented design guidelines to help you understand the design and how to develop it. The code examples and their associated documentation are in the Code Example folder in the repository.
To use the code examples in this repository, please download and install PSoC Creator
Note Please refer to the code example documentation for selecting the appropriate kit for testing the project
This code example demonstrates how to create a user-interface solution using an E-INK display with a CapSense slider and buttons. E-INK displays consume no power for image retention. Together with PSoC 6 MCU’s CapSense touch sensing, an EINK display can be used to create user interfaces that have “always-on” functionality.
This code example demonstrates connectivity between the PSoC 6 MCU with Bluetooth Low Energy (BLE) and CySmart BLE host emulation tool or mobile device running the CySmart mobile application, to transfer CapSense® proximity sensing information.
This code example demonstrates interfacing PSoC 6 MCU with BLE Connectivity (PSoC 6 MCU) with a thermistor circuit to read temperature information and sending the temperature data as BLE HTS indications to a mobile device running CySmart mobile application. In addition, PSoC 6 MCU’s real time clock (RTC) generates alarms (interrupts) at every minute to show temperature information on the E-INK display when BLE is not connected.
This code example demonstrates the ability of PSoC 6 MCU with BLE Connectivity (PSoC 6 MCU) to function as a BLE beacon using the Broadcaster role, which transmits Eddystone fames. Eddystone is an open-source BLE beacon profile released by Google. This project broadcasts core Eddystone frame types—Eddystone UID, Eddystone URL, and Eddystone TLM.
This code example demonstrates interfacing PSoC 6 MCU with an RGB LED with color and intensity control and touch buttons based on mutual capacitance (CSX), and touch-slider-based on self-capacitance (CSD). This code example also shows connectivity between the PSoC 6 BLE (acting as a Peripheral and GATT Server) and a PC running the CySmart BLE Host Emulation tool or a mobile device running the CySmart mobile application (acting as a Central and GATT Client). Custom BLE services are used for CapSense touch sensing and LED control.
This code example demonstrates accurate time keeping with the RTC of PSoC 6 MCU with BLE Connectivity (PSoC 6 MCU), which also generates alarms (interrupts) at every one minute to show time information on an E-INK display. In addition, a BLE CTS is used to synchronize time and date with a current time server such as an iPhone.
This example configures and reads data from a BMI160 motion sensor using PSoC 6 MCU. The example uses the BMI160 motion sensor to detect and count steps from activities such as walking or running, emulating the functionality of a pedometer. The motion sensor’s accelerometer data is also read and converted to indicate the orientation of the sensor with respect to the ground. The step count and orientation information is displayed on the E-INK display.
PSoC 6 bridges the gap between expensive, power hungry application processors and low‑performance microcontrollers (MCUs). The ultra‑low‑power PSoC 6 MCU architecture offers the processing performance needed by IoT devices, eliminating the tradeoffs between power and performance. The PSoC 6 MCU contains a dual‑core architecture, with both cores on a single chip. It has an Arm® Cortex®‑M4 for high‑performance tasks, and an Arm® Cortex®‑M0+ for low-power tasks, and with security built-in, your IoT system is protected. To learn more on the device, please visit our PSoC 6 MCU webpage.
Device datasheets list the features and electrical specifications of PSoC 6 families of devices: PSoC 6 MCU Datasheets
Application notes are available on the Cypress website to assist you with designing your PSoC application: A list of PSoC 6 MCU ANs
PSoC Creator utilizes "components" as interfaces to functional Hardware (HW). Each component in PSoC Creator has an associated datasheet that describes the functionality, APIs, and electrical specifications for the HW. You can access component datasheets in PSoC Creator by right-clicking a component on the schematic page or by going through the component library listing. You can also access component datasheets from the Cypress website: PSoC 6 Component Datasheets
The TRM provides detailed descriptions of the internal architecture of PSoC 6 devices:PSoC 6 MCU TRMs
Need support for your design and development questions? Check out the Cypress Developer Community 3.0.
Interact with technical experts in the embedded design community and receive answers verified by Cypress' very best applications engineers. You'll also have access to robust technical documentation, active conversation threads, and rich multimedia content.
You can also use the following support resources if you need quick assistance: