tft display is white in stock

So, I have a purpose built pcb with the teensy 4.0 footprint (little did I know the financial implications this would have...I"ve been through >�60 worth of teensy 4.0).

My PCB board size is about 100mm-80mm (all hand soldered with a hot air tool, soldering iron, heat bed not to blow my own trumpet, but I am very good at pcb assembly by hand + I find it therapeutic).

So after half a days soldering, I fire up the board and excellent, the ILI9341 is running at a clock speed of 100mhz (not scoped), lightning fast! Dropped the speed to a more reasonable 20mhz and left overnight for a board test (i always do this, as i have lipos connected etc and like to see if there are any heat issues etc after a 24h run). Found no issues the next morning, graphics test still running so powered off the device.

No changes made, powered up on the third day, and nothing but a white screen on the ILI9341? So i say, must have blew the t4 some how. Hot air removed the t4, on goes the new one and again a few runs later and i get a white screen again? Checked all my pin assignments, voltages and they are all good.

I came to the conclusion that as I was forcing the T4 to be powered of of 3v3 as per (https://forum.pjrc.com/threads/64468...V-power-supply) this was somehow messing with the SPI communication. I canned the T4 and designed and built a T4-SAMD51 clone.

I picked up the project again today and de-soldered my SAMD51 T4 clone pcb as I need speed! The T4 would have been perfect, so tried a few code changes, got the screen running in the setup function (static text etc), but as soon as it enters the loop(), you guessed it....white screen. Its as if the t4 is too fast on spi or something, but I have changed the clock speeds down to 5mhz and yield the same results...

To confirm, I had the T4 intermittently working on both the adafruit ili9341 library and the optimised ili9341_t3. I"ve been through 3 T4s and I have 5 different ILI934 displays. (all give the same results, pull ups, no pullups, removed sd circuitry, ran the T4 at 5v I"ve tried it all!)

The game will compile and work, I can see it working on the serial monitor.  The issue is the screen stay white.  I can load examples codes and the display screen works perfectly.

testdrawtext("Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur adipiscing ante sed nibh tincidunt feugiat. Maecenas enim massa, fringilla sed malesuada et, malesuada sit amet turpis. Sed porttitor neque ut ante pretium vitae malesuada nunc bibendum. Nullam aliquet ultrices massa eu hendrerit. Ut sed nisi lorem. In vestibulum purus a tortor imperdiet posuere. ", ST77XX_WHITE);

Please don"t mark this question as duplicated because I looked at the other guy he/she was using different guide.. the one I"m using is posted by the company I purchased the TFT from.

I tried the 8-Bit wiring next. (I don"t know if I that was supposed to work, after I set the SPI mode jumpers)... Anyway, I tried it, but I only get a blank screen and in the serial monitor there"s always this line in the message:

I seem to have a similar problem. (Newbe alert!) I have a new Raspberry Pi B+, V 1.2, and a 2.8" Capacitive Touch Screen Panel. Have worked with the supplied NOOBS 8GB card and found much of the GPIO workable using the HDMI connection. I have closed the solder bridge for the GPIO #18 dimming. However, I have been unable to get an image or text on the Touch Screen Panel. It does, however, light up. I have used the "easy_start" instructions (for the Capacitive Touch Screen) and have tried to modify my existing OS kernel with the "detailed instructions." At one point I was able to dim and brighten the screen. However, I"m now in the position of having the boot hang. This now happens with whatever card I try to set the system up with. The last instruction being "i2c-core: driver [ft6x06_ts] using legacy resume method". I"ve re-soldered the headers without a change in behavior. Any suggestions about how to proceed?

I am having similar problem with a 2.8" TFT LCD with Cap Touch Breakout Board w/MicroSD Socket (https://www.adafruit.com/product/2090). Tried reflowing the pins and different jumper wires/breadboard locations. Also tried soldering the three locations on the back to see if SPI mode works. Same white screen with SPI. Finally after some searching online, I found this post. The following picture was taken after re-opening the three locations, to show the 8-bit mode wiring that I did. I am using the stock graphicstest example sketch. Serial monitor always shows unknown LCD driver chip: 0. Does this mean mine is also a bad copy?

Ah. The "ears" aren"t pushed in all the way on the connector. Gently pull the left one out, and then push the cable into the connector. Push in both ears to secure the cable. See this FAQ for a picture of how it should look

I have a new 2.8" capacitive touch screen, Adafruit part#2423. I have a freshly-downloaded debian-wheezy installed on an SD card. I connected the display, but just white screen. When I attempt to follow the instructions at https://learn.adafruit.com/adafruit-2-8 ... sy-install, and run "curl -SLs https://apt.adafruit.com/add | sudo bash

sudo apt-get install -y adafruit-pitft-helper" (in a shell on a separate HDMI monitor) I get this response "/usr/bin/sudo: /usr/bin/sudo: cannot execute binary file". I have read http://forums.adafruit.com/viewtopic.ph ... ve+TFT+LCD but I don"t see this listed. I am very new to this, though I have been using Unix (and programming in C) off and on since 1978.

If one resets power cable to the Arduino about 30 times, eventually it starts showing what it is supposed to show (I tried the stock sample and occasionally could actually see all the image transitions that sample is supposed to show). But after an hour or two it goes again into this white state mode.

- what could help is removing and then inserting USB/power cable to the Arduino instead. If done 10+ times in a row occasionally it turns display into usable mode when it actually shows what it is supposed to show.

I doubt this would be of any use. As I said, the sample occasionally works (usually after multiple power off/on cycles to the arduino board). That means that the code works and that pins are set correctly.

If it turns out the current display is bad, we can replace it. But it sounds like you are after a refund because it"s smaller than you wanted. Since you"ve soldered on headers and used it, it"s not that simple. That"s why I pointed to the return policy.

There may be some compatibility issues with hardware SPI and your clone board. As another check, you could try switching to software SPI (comment out hw line, uncomment sw line):

Also if you can, post a better photo showing your soldering. It looks OK, but the resolution is just border line enough to not be able to tell for sure.

I need to use this display for image output from SD card. The wording in the guide implies that hardware SPI should be used in this scenario: https://learn.adafruit.com/2-2-tft-disp ... fx-library :

"Wire up the TFT according to the high-speed SPI diagram above. Test that your wiring is correct by uploading the graphics test sketch with the high speed SPI line uncommented and the flexible-low-speed wiring commented."

Also I found out that if I reset the display via the rst pin and then reset the arduino (without powering it down) the display works for some time via the hardware SPI. But it doesn"t make it through the whole set of graphicstests. On some graphic transition it again switches into the just-white-screen-state.

Today I spoke with an experienced colleague of mine who is also into arduino stuff and he suggested that there may be some timing issue in the SPI driver. Some timing gets wrong and the SPI protocol gets broken.

Software SPI won"t be as fast as hardware SPI, so the slowness is expected. This was just a way of testing the display using a different approach. And it worked, so we know the display is OK. Now the question is why hardware SPI does not seem to work.

Today I spoke with an experienced colleague of mine who is also into arduino stuff and he suggested that there may be some timing issue in the SPI driver. Some timing gets wrong and the SPI protocol gets broken.

Possible. But this has all been tested and is known to work. Do you have access to another UNO board? Preferably a genuine one - that"s what we know works. Swapping that out would be the next easiest thing to check.

[EDIT] Wanted to make sure nothing has changed with any of the software parts (library, Arduino IDE, etc). I just set up one of those displays here with an Arduino UNO and the wiring for hardware SPI from the guide. The graphicstest example is running fine for me, so this should still work per the guide.

1) Connect the faulty 2.2 display to Mega over hardware SPI. The same kind of symtomps. It showed the complete grahicstest but at the very end the display again entered into all-white state. Display reset via rst pin can revive it for a few seconds but then it goes all-white again on a graphic transition.

2) Connect the new 3.5 display to Mega over hardware SPI. No issues so far. The grahicstest is shown in full. I"ve tried to reset arduino several times and each time display shows the grahicstest just fine.

I"m glad as well. All the samples worked. Although the sample that draws image from SD card sometimes says that it can"t read the file. I"ve swapped the order of TFT and SD card initialization and it seems that stabilized things. Hopefully it would be stable from now on.

Really weird that it works with software SPI but not hardware. I"ve left my Uno setup running with hardware SPI since my post above, and it"s still running without issue. So it also doesn"t seem related to length of time running. Not sure what it could be. Maybe the clone board"s hardware SPI is running at unsupported clock rate? But the other display works, so dunno.

Let"s replace it. Send an email to support@adafruit.com with a link to this thread and your order number and they can get you a replacement 2.2" TFT display.

I have a problem with my Arduino LCD Screen (https://www.arduino.cc/en/Main/GTFT) i recently bought when i put power on my arduino the screen becomes white and that is it ...

I have already seen this topic (Arduino 1.77" SPI TFT Blank White Screen Only - Displays - Arduino Forum) and tried some of the suggestions made over there.

RMG1JHBW–Tokyo, Japan. 17th May, 2016. An exhibitor operates a robot during the press event for the Educational IT Solutions Expo (EDIX) at Tokyo Fashion Town (TFT) Hall on May 17, 2016, Tokyo, Japan. EDIX is Japan"s largest industry trade show attracting top IT service providers, electronic manufacturers and content providers seeking opportunity to expand in Japanese education field. The exhibition is held at Tokyo Big Sight from May 18 to 20. Credit: Rodrigo Reyes Marin/AFLO/Alamy Live News

RF2D74NJB–Vector TV led screen isolated background. Red, yellow, blue color modern stylish lcd panel. Computer monitor display mockup set. Blank television grap

RF2D74NMD–Vector TV led screen isolated background. Red, yellow, blue color modern stylish lcd panel. Computer monitor display mockup set. Blank television grap

I am using Pi Zero WH with Raspbian Stretch, but am using the same screen. I found the GPIO pins layout here https://raspberrypi.stackexchange.com/q ... ypi-zero-w & connected my display with dupont wires.

I read that the setup method Nathan Chantrell has on his site is outdated, so I used the "system" settings guide here. https://www.sudomod.com/forum/viewtopic.php?t=2312

The display controllers for the display are ILI9340. In the guide, I followed "sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:25,dc:24,led:18 speed=16000000 bgr=1".

I read using ILI9341 should still work, because there should not be much changes? Should I try using "sudo modprobe fbtft_device custom name=fb_ili9340 gpios=reset:25,dc:24,led:18 speed=16000000 bgr=1"?