TFT 3.2 inch touchscreen display + Arduino Due with no sheild

Hi there,

Lastly I have been trying to drive the 3.2 inch display below with an arduino due.

Display: 3.2inch 16BIT Module ILI9341 SKU:MRB3205 - LCD wiki

The display is considered an ILI9341 display with an XPT2046 touchscreen. It has a 16-bit parallel pin interface and some other pins like SPI ones, but I don't understand if they drive a specific function of it or both a function of the display and the touchscreen. (2x17 total pins)

I tried to use the display with the ILI9341 as well as the GFX library by adafruit and try the demo graphic, but all I eventually got was just a white screen.

Can somebody help me so I wire the display correctly and use the correct drivers and code to drive the display?

Arduino Due with a HiLetgo 240X320 Resolution 2.8" SPI TFT LCD Display Touch Panel ILI9341
worked OK using Adafruit_ILI9341 library the pin settings

// Arduino Due connections
#define TFT_CS    10
#define TFT_DC    8
#define TFT_MOSI  MOSI
#define TFT_CLK   SCK
#define TFT_RST   9
#define TFT_MISO  MISO

EDIT: remember the SPI connections goto the ICSP header

Your problem is not unexpected, and your wiring may be the root cause. Since hardware and design is involved, it’s crucial to provide an accurate, annotated schematic of your circuit as it is currently wired. Please note that Fritzing diagrams are not considered proper schematics; they are wiring diagrams and are often not helpful for troubleshooting.

What to Include:

  1. Annotated Schematic: Show all connections, including power, ground, and power sources. This helps us understand how your circuit is set up and identify any potential issues.
  2. Technical Information Links: Provide links to technical documentation for each hardware device used in your setup. Avoid links to sales sites like Amazon, as they usually lack the necessary technical details. We need complete specifications to help you effectively.
  3. Additional Information Needed: If the above details are incorrect, more information is required. Tell us what hardware and software you are using, the format of any data (like map data), and how your system determines its position. For example, if your project involves a robot, describe how it navigates and what computers are involved.
  4. Bill of Materials:
    5.A schematic provides a visual representation of the electrical connections and components in a circuit, showing how they interact and function together, while a Bill of Materials (BOM) is simply a list of components with part numbers and quantities needed for assembly. Unlike a BOM, a schematic illustrates the design’s logic and allows for troubleshooting and understanding circuit behavior. A BOM is useful for sourcing parts but doesn’t convey how they connect or operate in the circuit, which is critical information for understanding and working with electronics.

Why This Matters:

We have no way of knowing the specifics of your setup unless you provide that information. Clear and detailed descriptions enable us to offer the most accurate help possible. Without these details, it’s difficult to diagnose and solve the issues you're experiencing.

We need the following:

  • Annotated Schematic: Clearly show all connections, including power, ground, and power sources. This will help us understand your circuit setup and identify potential issues.

  • Technical Information Links: Provide links to technical documentation for each hardware component in your setup. Avoid links to sales sites like Amazon, as they often lack the detailed specifications we need to assist you effectively.

Give yourself an early Christmas present and pick up these resources, along with the Arduino Cookbook:

reading the TFT display documentation referenced in post 1
try connecting the Due to the display so

// Arduino Due connections
#define TFT_CS    10	to display T_CS	Touch screen IC chip select control pin
#define TFT_DC    8	    to display RS data/control
#define TFT_MOSI  MOSI	to display MOSI	Touch screen SPI bus data output pin
#define TFT_CLK   SCK	to display CLK	Touch screen SPI bus clock control pin
#define TFT_RST   9	    to display CS LCD reset control pin
#define TFT_MISO  MISO	to display MISO	Touch screen SPI bus data input pin

and try examples from adafruit TFT library

Here is a picture of the display:


I have tried the following connections:

Display | Arduino due

T_CS > digital pin 8
CLK > SCK ( From the SPI pins )
PEN > digital pin 6
F_CS > digital pin 7
MISO > MISO ( From the SPI pins )
MOSI > MOSI ( From the SPI pins )
NC > -
GNDs > GND
VDDs > 3.3v (connected to a breadboard rail)
BL > 3.3v (connected to a breadboard rail)
DB15 - DB0 > digital pins 22 - 37
RST > digital pin 4
WR > digital pin 5
RD > digital pin 9
CS > digital pin 11
RS > digital pin 12

@horace Unfortunately, the wiring you showed doesn't work with the TFT library.
Moreover, this library refers to some other wire connections such as analog ones, or the 8-bit bus ones to digital pins.

I also forgot to mention that this screen has the ability to switch between 16-bit and 8-bit interface. Should I also try it with 8-bit interface or try to use another library?

Please let me know if you have found out anything about the specific display. Thanks

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.