For engineers developing connected equipment and other embedded control systems, the PSOC 6 MCU brings processing, programmable logic, analog resources and communications into one device platform. The CY8C62x6/7 family pairs a 150-MHz Arm Cortex-M4F with a 100-MHz Cortex-M0+, alongside configurable peripherals and security mechanisms. Its combination of resources can help teams assess how much system functionality may be integrated into an MCU, while making power, timing and protection requirements explicit design considerations.
PSOC 6 MCU architecture: two cores, shared resources
The dual-core subsystem assigns different strengths to each processor. The Cortex-M4F is the main high-throughput core, with floating-point support, a memory protection unit and a maximum operating frequency of 150 MHz. The Cortex-M0+ can run at up to 100 MHz and supports system-level functions, including protected boot and device security responsibilities. The cores can communicate through hardware inter-processor communication channels, which can also help coordinate access to shared resources.
This arrangement offers a way to separate application processing from selected system functions, but the division of work must be planned in firmware. Both processors share access to memory and peripherals, so engineers should consider synchronization, ownership and protection when designing the software architecture. The device also includes two DMA controllers, each with 16 channels, for transferring data between memory and peripherals without requiring the CPU to manage every transfer.
Memory and external serial access
The family provides up to 1 MB of application flash, 288 KB of SRAM, 32 KB of auxiliary flash and 32 KB of supervisory flash. Application flash supports read-while-write operation, and each CPU has an 8-KB flash cache. The auxiliary flash may be used for EEPROM emulation; supervisory flash stores device-level information such as boot code and trim values. SRAM retention can be controlled in 32-KB blocks for Deep Sleep operation, giving designers a way to balance retained application state against power requirements.
A Serial Memory Interface (SMIF) supports external QSPI memory and execute-in-place operation. Its listed capabilities include on-the-fly encryption and decryption, a 4-KB cache, and single, dual, quad, dual-quad and octal interfaces. The specified throughput is up to 640 Mbps. These options are relevant when evaluating external memory needs, but the appropriate configuration depends on the application’s code, data and interface requirements.
Programmable logic and integrated peripherals
Rather than relying only on fixed-function peripherals, PSOC 6 includes 12 universal digital blocks (UDBs). Each has eight macrocells and an 8-bit data path. They can be configured as digital primitives or programmed using Verilog; the platform’s component library also uses UDBs to implement functions such as communication interfaces and waveform generation. Two Smart I/O ports provide Boolean operations on GPIO signals and remain available in Deep Sleep.
Fixed-function resources cover many common control and connectivity tasks:
- Timing: 32 timer/counter/PWM blocks support edge, center-aligned and pseudo-random modes, with comparator-based kill-signal triggering.
- Serial communication: Nine configurable Serial Communication Blocks provide SPI, I2C or UART options; one Deep Sleep block supports SPI or I2C. USB full-speed host and device functionality is also listed.
- External memory: The SMIF supports serial flash interfaces, including execute-in-place access.
- Human-machine interfaces and audio: The MCU includes segment LCD drive for up to 99 segments and eight commons, two PDM channels and an I2S channel with TDM mode.
For an integrator, the design value is flexibility, not an assumption that every peripheral can be used simultaneously in every pin assignment or power configuration. Pin multiplexing, clocking, peripheral availability and the selected package all need to be checked during hardware planning.
Analog, sensing and signal handling
The programmable analog subsystem includes a 12-bit, 1-Msps SAR ADC with differential and single-ended modes, a 16-channel sequencer and result averaging. It also provides a 12-bit voltage-mode DAC, two opamps, two low-power comparators and an on-chip temperature sensor connected to the ADC. These resources can support signal acquisition and conditioning functions within an embedded design, subject to the device’s electrical specifications and the needs of the external sensor circuitry.
CAPSENSE supports self- and mutual-capacitance sensing, proximity detection and automatic hardware tuning. That capability may be useful where a design calls for capacitive user input, but it should be evaluated against the operating environment and interface requirements. The MCU also offers up to 100 programmable GPIOs, including six overvoltage-tolerant pins; actual availability depends on package and pin configuration.
Power management and embedded security
The operating supply range is 1.7 to 3.6 V. Designers can select 0.9-V or 1.1-V core operation: the lower-voltage ultra-low-power mode limits clock speeds, while low-power mode supports higher performance without those same speed limitations. The device provides six power modes, including Deep Sleep and Hibernate. The stated Deep Sleep current is 7 µA with 64 KB of SRAM retained; system-level consumption will depend on configuration and active resources. An on-chip SIMO buck converter and a backup domain with a real-time clock support the platform’s power-management options.
Security features span boot, execution and access control. ROM Boot checks the flash boot code and configures protection; Flash Boot validates the application before launching it. The architecture also supports protected execution, up to eight protection contexts, disabling debug and test access paths, and hardware acceleration for cryptographic operations and hashing. A true random number generator is included. These mechanisms provide building blocks for a secured design, but they do not replace application-specific security architecture, key management or lifecycle planning.
What to evaluate before selecting the MCU
When considering the PSOC 6 MCU for an embedded control project, review the complete system rather than the feature list alone. Confirm CPU workload and core coordination, memory capacity, pin and package constraints, analog performance requirements, peripheral conflicts, clock targets and power-mode transitions. Security needs should also be mapped to boot behavior, debug policy and the intended use of flash and eFuse resources.
In practical terms, the CY8C62x6/7 combines processing, configurable digital hardware, analog functions and communications with multiple power and protection options. That breadth can support varied embedded architectures, while placing responsibility on the design team to verify configuration details against the specific application. Reference manuals, electrical specifications and package documentation remain essential inputs to component selection and implementation.