IN Brief:
- Penny Pixel technology is designed to let lower-cost MCUs drive high-resolution active-matrix TFT displays without a separate high-end display controller.
- Powertip contributes display manufacturing while TARA Systems provides its Embedded Wizard GUI development framework.
- The combined architecture targets richer embedded HMIs without requiring a substantially more complex MPU and external-memory design.
Penny Pixel, Powertip and TARA Systems have combined their display-driving, TFT manufacturing and embedded GUI technologies in a validated architecture intended to let lower-cost microcontrollers support higher-resolution graphical interfaces without the usual combination of a separate display controller and external framebuffer memory.
The partnership addresses a familiar embedded-design problem. Basic segmented or passive-matrix displays place relatively modest demands on processing and memory, but moving to a colour active-matrix TFT increases the amount of pixel data that has to be stored, updated and transferred. The graphics subsystem can then dictate processor and memory selection even when the rest of the application does not require that level of computing performance.
Penny Pixel’s architecture is intended to reduce that penalty. Powertip describes the technology as allowing comparatively low-cost MCUs to drive high-resolution active-matrix TFT panels without the dedicated controllers and external framebuffers normally associated with more demanding graphical interfaces.
Powertip contributes the display platform and manufacturing capability, while TARA Systems provides Embedded Wizard, its embedded GUI framework. The software is designed to generate memory-efficient graphical interfaces across a range of processors and supports layouts, themes, fonts, animation and user interaction without requiring developers to build the complete graphics stack themselves.
Bringing the display architecture and GUI toolchain together matters because interface performance depends on more than panel resolution. Developers have to manage rendering, input events, animation, fonts and application logic while ensuring that screen updates remain responsive and do not create visible tearing or other artefacts.
External memory can become a substantial overhead in lower-cost designs. It adds components to the bill of materials, occupies PCB area and introduces higher-speed routing, power and electromagnetic-compatibility considerations. Moving from a microcontroller to a larger application processor can also bring a different software environment and a more complicated boot and memory architecture.
Those costs are justified where the display is central to the product, but they are less attractive in industrial controls, instrumentation and appliances where the core application may still consist of relatively modest sensing, communications and control functions. In those systems, richer graphics are often desirable without allowing the display subsystem to dominate the electronics.
The new combination is therefore positioned between basic embedded displays and full application-processor graphics systems. It gives designers another point on the cost and performance curve, particularly where the interface needs more resolution or visual complexity than a simple MCU arrangement would normally support.
There are still practical limits. Resolution, colour depth, frame rate, animation complexity and image content all influence processing and memory bandwidth. Some interfaces will continue to require a dedicated graphics engine or more capable MPU, particularly where video, complex transitions or large image assets are involved.
Software portability provides another consideration. Embedded Wizard supports multiple display resolutions and processor environments, allowing manufacturers to reuse interface logic across product families. That can reduce redevelopment effort where several devices share the same user experience but use different screens or controllers.
The three-company arrangement now spans panel manufacturing, the display-driving architecture and the GUI development environment. Its commercial usefulness will depend on the precise MCU, resolution and performance combinations offered in production systems, but it addresses a genuine design constraint: user interfaces continue to become more sophisticated while many embedded applications still do not justify the cost and complexity of a full application-processor architecture.
