I hope you're all doing good.
On the question - I start with a small 2" tft display (that also was making me mad , but David helped me and the problem was figure out) but first of all it was too small and second - its touchscreen was the worst I ever seen. I'm using Arduino Mega 2560.
So I decide to upgrade a bit and found buydisplay.com and everything was looking very good. I bought that exact screen with shield : https://www.buydisplay.com/default/arduino-3-5-tft-lcd-touch-shield-serial-spi-example-for-mega-due
As it comes with preconfigured libraries I decide to buy it. The price also was very reasonable , beside that it was tripled from all import taxes , agents and so. It still was not that a problem because I want my project done!
Even on the website is written that it is SPI prepared the screen came configured for 16 bit. I decide to test it with the libraries and the examples on the page. When I connect it and try to upload the sketch the arduino is just stuck. After some test with cables I figure out that the reset pin from the display is blocking the arduino so it was removed. Uploading now running good.
As I want the display to work via SPI I decide to make the necessary changes on the back of it and also on the shield and to run it again. I upload again the sketch from the examples and guess - the same flickering white screen.
After loooong research in the web I found the Ucglib. With that library I succesfully ran the display on HW and SW SPI.
As I want to use the UTFT library , because I'm much familiar with I'll appreciate any help figuring out that problem.
Attached is a short video with the display runing UTFT library and the flickering I'm talking about and also the cube from the Ucglib.
Even nobody took a part , I'll report what was wrong. In act of the most highest level of stupidity of my side , I downloaded the wrong sheet - sheet for 3.2" instead 3.5". The controller for 3.2 is ILI9341 , for 3.5 ILI9488. So after downloading appropriate libraries I had some colours on the screen. At that moment I'm running it with david_prentice library over HW SPI.n
Now I have two questions.
The shield at this time is providing the SPI through pins 7,9 and 10 on my Arduino Mega. All the recommendations around are to use the dedicated pins for SPI. Is that fatal for the performance of the screen?
David this is directly to you. I have some problems with the screen. I can see some fillScreen colours , but all the rest is as i single line on the one end of the screen. My I rely on your help to fix that problems and if yes what I should report here to help you out.
Seriously. Please correct the title of the thread. It does not inspire confidence when typos are not corrected.
And explain exactly which display, shield, configuration you have set.
All the EastRising products have model numbers, documents and schematics.
So you can say ER12345 shield has jumpers: J1, J3, J4, ... open, J2, J5, J6, J7, ... short.
ER56789 display is plugged into ER12345 shield plugged into a Mega7654 Arduino.
And which library you are using. Which example.
First time Posters do not realise the importance of providing accurate information.
You have made several posts. You should know by now.
Please take my excuses again David. I post a video in the first post soI decide that the information in it is enought , thats why I did not exaplain again.
Anyway , on the question:
The shiled is ER-AS_ILI9341
The display is ER-TFTM035-6
The shiled is attached to Arduino mEga 2560.
At the the shiled closed are the hardware spi and 3/4 SPI jumpers.
At the TFT closed are J1,J2,J3 , R1-R10,R19,R21-R28=0. This is the configuration for 4 wire SPI according the .pdf from the website.
At the moment I'm running the ILI9488_kbv library. When the graphictest_kbv is uploaded I can see blue , green and red on the whole screen. After that everything is hapening on a single line on the short side of the screen.
This is what the serial is saying:
Serial took 0ms to start
ID = 0x1408
When ST7735_readreg is uploaded :
(PINS: #define TFT_MOSI 3 #define TFT_SCK 2 #define TFT_SS 9 #define TFT_DC 7 //DC=7 for HX8347 #define TFT_RESET 10
With some tests I can see the the reg and blue are swaped. I manage to fix that changing the serial_kbv. #if defined(NINEBITS)
uint8_t b = color >> 8, g = (color >> 3), r = color << 3;
while (n-- > 0) {
WriteDat8(r);
WriteDat8(g);
WriteDat8(b);
This way the colors are correct.
There are jumpers (solder-bridges) on ER-TFTM035-6. I have J1, J2, J3, J7, J9, J10, J11 closed.
This provides regular 4-wire SPI i.e. MOSI, MISO, DC, SCK.
There are jumpers on ER-As-ILI9341. There are many options. I do not have an ER-AS-ILI9341 shield.
The ILI9488 LCD-SDO pin does not 3-state properly. ILI9341 LCD-SDO does go Hi-Z when LCD-CS is not selected.
From the shield schematic R3 seems to "reduce" the SDO loading. However it does impair the SPI read performance.
Yes, you can configure the ILI9488 to be bi-directional. It is a lot easier to use regular MOSI, MISO.
You can also configure the ILI9488 to use any interface via the IM# jumpers.
The EastRising boards can do anything that you want. But you need to know what you are doing. Some combinations will not work with your 5V GPIO.
David , are you sure that the whole of my post is visible for you. I explain pretty clear which jumpers are soldered and why they are according the .pdf.
May be you're just not in a good mood today Thank you for your time!
Thank you for your time!