- 2.8“ Display with QVGA resolution (320×240)
- 2 Finger Capacitive touch panel
- Powerful PIC32MZ Microcontroller
- Design a beautiful UI with only a few lines of code using libraries for Arduino IDE and Xilinx SDK
- Easily draw images with binary transparency from files stored on microSD
- Drop stylish buttons and check their status at will using intuitive function calls
- For use with Arduino, chipKIT and Arty platforms
- 6-pin Pmod port with SPI interface
The Pmod MTDS is retired and no longer for sale.
The Digilent Pmod MTDS (Revision A) is a gorgeous 2.8“ touchscreen display with a powerful on-board microcontroller that performs graphics processing tasks. The display is a capacitive touchscreen with QVGA resolution (320×240) and 2 finger multi-touch support.
The most compelling aspect of the Pmod MTDS is the programming experience provided by its Multi-Touch Display System (MTDS) Firmware and the associated libraries. These allow you to design sleek, stylish user interfaces very quickly and with very little code. The timing dependent tasks are handled by the firmware, so integrating the display into existing projects is also a snap. Some of the key functionality provided by the libraries include the ability to draw basic shapes and text, draw images stored on microSD with binary transparency, draw buttons and easily check if they have been pressed, and check the status and location of the user's two fingers. The libraries are supported in Arduino IDE and Xilinx SDK, and have been tested with Ardiuno, chipKIT and Arty host boards.
Example Projects and Libraries
- Digilent Pmod IPs are only supported in Vivado and Xilinx SDK versions 2019.1 and earlier.
This product is in the process of being retired and will be sold as is until it is out of stock. To this end, software support for this product is limited to the materials provided by Digilent. There are no plans to update any existing Vivado and SDK/Vitis projects or Arduino/Digilent Core projects beyond the version they are provided in. Changes to the Xilinx toolchain between SDK and Vitis mean that the software libraries do not work as-is in Vitis and may require significant refactoring in order to get them to compile.