search

Bodmer / TFT_eSPI

Arduino and PlatformIO IDE compatible TFT library optimised for the Raspberry Pi Pico (RP2040), STM32, ESP8266 and ESP32 that supports different driver chips
Other
3.63k stars 1.05k forks source link

ILI9341 Screen is only working with disabled Chip Select #283

Closed tobimai closed 5 years ago

tobimai commented 5 years ago

Hi,

I have this ILI9341 Display from Banggood and it works perfectly as long as I don't use ChipSelect by commenting out thedefine TFT_CS 5 line. And connecting CS to GND.

The problem is, that I want to use CS to be able to also use Touch. But when I use CS the Display just stays blank/white.

I tried multiple Pins and Multiple Cables and multiple SPI Frequencies, nothing works. I also looked at the CS signal with an Oscilloscope and it's definitly doing something (seems like going low for a short time), I can't see more as it's an rather old analogue Oscilloscope.

When I enable CS in the lib and connect CS to GND, the display also stays blank.

I use an ESP32 DOIT v1 Devkit and Platformio for the programming.

Here is the UserSetup.h and Here is the main.cpp file wich is just the example slightly modified.

Bodmer commented 5 years ago

Post a picture of your setup. Is the touch contoller chip wired to the ESP32 for these tests, if so was the touch controller chip select driven high so there is no SPI bus conflict. How are you powering the display?

These may sound like irrelevant questions but something is wrong with the setup, allocating a pin to the chip select but then not using it should not affect the behavior of the display.

tobimai commented 5 years ago

Post a picture of your setup. Is the touch contoller chip wired to the ESP32 for these tests, if so was the touch controller chip select driven high so there is no SPI bus conflict. How are you powering the display?

These may sound like irrelevant questions but something is wrong with the setup, allocating a pin to the chip select but then not using it should not affect the behavior of the display.

I tested it on more pins and discovered, that CS only works on some Pins. Currently it works fine on 32 and 35.

Could it have something to do with the settings of the internal pullUp-Resistors?

To your questions: When Testing, the Touch chip was disconnected and I am Powering the board from my Laptop (1.5A USB Port, shouldn't be a problem)

Sorry that I didn't reply earlier, GitHub didn't send a notification for some reason.

Bodmer commented 5 years ago

GPIO 35 is input only so will not be able to drive the CS line. GPIO32 can be used and since it works I would keep using that pin. I cannot replicate the issue with GPIO 5 using the Arduino environment, perhaps there is an issue with the library and the PlatformIO environment?

FLYINGSC0T commented 5 years ago

Hi Bodmer. Thanks for a great library!! I have a problem getting Lora to work with an ILI9341 display on a TTGO T-Beam. If I comment out tft.begin() Lora works but if I enable it Lora does not work. The pin connections that I have set up in user setup .h file for the display are:

define TFT_MISO 22 // Changed to 22 as GPIO 19 is used by Lora MISO on T-Beam

define TFT_MOSI 25 // Changed to 25 as GPIO 23 is used ny Lora MOSI on T-Beam

define TFT_SCLK 21 // Changed to 21 as GPIO 18 is used by Lora CS on T-Beam

define TFT_CS 13

define TFT_DC 2

define TFT_RST 4

Any idea where the confliction is ? I have checked the GPIO's used by the T-Beam for the Lora module and I am sure they don't conflict but I can't find the problem.

BTW the display works perfectly using the above settings on an ESP32 Dev. board only that I can't get Lora and the display to work with the T-Beam.

Thanks in advance for any help.

George

achillhasler commented 5 years ago

Hi George, ESP32 have 2 usable SPI interface. (VSPI and HSPI) If you include a variable SPI is defined whitch is used by the librarys. If you dont create a new variable for the other SPI bus all librarys have to share the same bus (meens same connection for MOSI, MISO and SCK). Bud each dervice must have a own CS. try:

define TFT_MISO 19

define TFT_MOSI 23

define TFT_SCLK 18

ciao Achill

Bodmer commented 5 years ago

Hi George, as Achill has said the Lora device and library use the VSPI interface in the ESP32, so if the TFT_eSPI libray moves the VSPI pins MOSI, MISO and SCK then the Lora function will stop working. The TFT CS and DC pins must be on unused pins.

I may add the option to select either HSPI or VSPI at a future date.

FLYINGSC0T commented 5 years ago

Hi Achill,

Thanks for your reply.

The problem is that the T-Beam Lora uses the GPIO pins as follows:

MOSI 27 MISO 19 SCK 5 CS 18 RST 23

It looks like the library is moving the pins causing Lora to not work (?).

The GPIO pins I had set up for the display were:

define TFT_MISO 22 // Changed to 22 as GPIO 19 is used by Lora MISO on T-Beam

define TFT_MOSI 25 // Changed to 25 as GPIO 23 is used by Lora MOSI on T-Beam

define TFT_SCLK 21 // Changed to 21 as GPIO 18 is used by Lora CS on T-Beam

define TFT_CS 13

define TFT_DC 2

define TFT_RST 4

So, you mention that I could create a new variable for SPI to utilize the TFT_eSPI library.

How to I do that and which pins would you recommend to use specifically for the T-Beam ?

Maybe a stupid question, but can I pass as parameters SCK, MISO, MOSI, CS in the call to tft.begin() because I only call tft.begin() with no parameters.

As the T-Beam is relatively new there is not a lot of information on the internet and I would really like to get this problem sorted.

Thanks again in advance for help you can offer.

Regards,

George

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: achillhasler notifications@github.com Sent: Friday, January 18, 2019 9:34:47 AM To: Bodmer/TFT_eSPI Cc: FLYINGSC0T; Comment Subject: Re: [Bodmer/TFT_eSPI] ILI9341 Screen is only working with disabled Chip Select (#283)

Hi George, ESP32 have 2 usable SPI interface. (VSPI and HSPI) If you include a variable SPI is defined whitch is used by the librarys. If you dont create a new variable for the other SPI bus all librarys have to share the same bus (meens same connection for MOSI, MISO and SCK). Bud each dervice must have a own CS. try:

define TFT_MISO 19

define TFT_MOSI 23

define TFT_SCLK 18

ciao Achill

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-455467023, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YfoVEPmLfEe7eqp345-qsqonK_nEks5vEYcngaJpZM4Z8lHJ.

FLYINGSC0T commented 5 years ago

Hi again Achill,

This is the code I’m using:

include

include

include

include "TFT_eSPI.h"

// Define the LoRa module GPIO pins

define LoRa_SCK 5 // GPIO5 -- SX1278's SCK

define LoRa_MISO 19 // GPIO19 -- SX1278's MISO

define LoRa_MOSI 27 // GPIO27 -- SX1278's MOSI

define LoRa_NSS 18 // GPIO18 -- SX1278's CS

define LoRa_RST 23 // GPIO14 -- SX1278's RESET

define LoRa_DI0 26 // GPIO26 -- SX1278's IRQ(Interrupt Request)

define Lora_BAND 868E6 // Frequency

unsigned int counter = 0;

// Define an instance of the TFT - uses hardware SPI TFT_eSPI tft = TFT_eSPI();

String rssi = "RSSI --"; String packSize = "--"; String packet ;

void setup() { Serial.begin(115200);

tft.begin();

while (!Serial); Serial.println(); Serial.println("LoRa Sender Test");

SPI.begin(LoRa_SCK, LoRa_MISO, LoRa_MOSI, LoRa_NSS);

LoRa.setPins(LoRa_NSS, LoRa_RST, LoRa_DI0);

if (!LoRa.begin(Lora_BAND)) { Serial.println("Starting LoRa failed !!"); while (1); } Serial.println("Init OK !!");

delay(1500); }

void loop() { Serial.print("Sending packet : "); Serial.println(String(counter));

Serial.println(String(counter));

// Send packet LoRa.beginPacket(); LoRa.print("hello "); LoRa.print(counter); LoRa.endPacket();

counter++;

delay(1000); // wait for a second }

Regards,

George

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: achillhasler notifications@github.com Sent: Friday, January 18, 2019 9:34:47 AM To: Bodmer/TFT_eSPI Cc: FLYINGSC0T; Comment Subject: Re: [Bodmer/TFT_eSPI] ILI9341 Screen is only working with disabled Chip Select (#283)

Hi George, ESP32 have 2 usable SPI interface. (VSPI and HSPI) If you include a variable SPI is defined whitch is used by the librarys. If you dont create a new variable for the other SPI bus all librarys have to share the same bus (meens same connection for MOSI, MISO and SCK). Bud each dervice must have a own CS. try:

define TFT_MISO 19

define TFT_MOSI 23

define TFT_SCLK 18

ciao Achill

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-455467023, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YfoVEPmLfEe7eqp345-qsqonK_nEks5vEYcngaJpZM4Z8lHJ.

Bodmer commented 5 years ago

The key is to use the same pins for MISO, MOSI and SCK:

#define TFT_MISO 19 // Does not need to be conected to TFT unless reading from display
#define TFT_MOSI 27
#define TFT_SCLK  5
#define TFT_CS      13
#define TFT_DC       2
#define TFT_RST      4
FLYINGSC0T commented 5 years ago

Hi Bodmer,

... on a normal ESP32 dev board that would be OK but the T-Beam doesn’t have pinout connections for 19, 27 and 5 !!

Thank you to reply.

Regards,

George

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Bodmer notifications@github.com Sent: Friday, January 18, 2019 6:15:49 PM To: Bodmer/TFT_eSPI Cc: FLYINGSC0T; Comment Subject: Re: [Bodmer/TFT_eSPI] ILI9341 Screen is only working with disabled Chip Select (#283)

The key is to use the same pins for MISO, MOSI and SCK:

define TFT_MISO 19 // Does not need to be conected to TFT unless reading from display

define TFT_MOSI 27

define TFT_SCLK 5

define TFT_CS 13

define TFT_DC 2

define TFT_RST 4

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-455620997, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YdOBEvXeAoR4XK3zyVvt2v06ohhLks5vEgFFgaJpZM4Z8lHJ.

Bodmer commented 5 years ago

Ok, in that case the only clean option is to add HSPI support which should be simple to do. I am extra busy at the moment but should be able to update the library within the next 10 days.

FLYINGSC0T commented 5 years ago

Ok that’s great Bodmer !!

Not sure what HSPI is but I’ll look forward to an update.

Have a good weekend.

Regards,

George

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Bodmer notifications@github.com Sent: Friday, January 18, 2019 6:33:10 PM To: Bodmer/TFT_eSPI Cc: FLYINGSC0T; Comment Subject: Re: [Bodmer/TFT_eSPI] ILI9341 Screen is only working with disabled Chip Select (#283)

Ok, in that case the only clean option is to add HSPI support which should be simple to do. I am extra busy at the moment but should be able to update the library within the next 10 days.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-455626528, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YT57xqqMhMYYSOfEbFpx5dWOT9FIks5vEgVWgaJpZM4Z8lHJ.

achillhasler commented 5 years ago

Hi George, have you tryed to share the spi-bus? spi_share The lane near processor is a sd-card, away the tft. Both has connction to Ground, MISO, MOSI and SCK other are separate You see MOSI (D23) brown cable MISO (D19) violet cable SCK (D18) green cable

on the jpg you see SD-Card use additional (D5) SS and 3.3V LCD use additional 5V (red cable), D4, RX2 (D16), TX2 (D17), RX0 (D3)

The SD-Card needs no configuation because this are the default pins for VSPI.

The User_setup.h for the shown picture is

define TFT_MISO 19

define TFT_MOSI 23

define TFT_SCLK 18

define TFT_CS 3 // Chip select control pin

define TFT_DC 4 // Data Command control pin

define TFT_RST 17 // Reset pin

define TOUCH_CS 16 // Chip select pin (T_CS) of touch screen (if you have a touchscreen)

nice Weekend

Bodmer commented 5 years ago

@achill, the problem for flyingscot is that his LoraWAN board does not make the required pins available to allow sharing, so the clean solution is to use the HSPI port which can be mapped to easily accessible pins.

Bodmer commented 5 years ago

This site has good info and links for the T-Beam board: http://tinymicros.com/wiki/TTGO_T-Beam

FLYINGSC0T commented 5 years ago

Thanks for the additional info Bodmer.

Regards, George aka FlyingScot

Sent from my iPhone

On 19 Jan 2019, at 12:35, Bodmer notifications@github.com<mailto:notifications@github.com> wrote:

This site has good info and links for the T-Beam board: http://tinymicros.com/wiki/TTGO_T-Beam

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-455772413, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_Yf6dBFtlHBM52WvoJhIpPFXW9lhHks5vEwLlgaJpZM4Z8lHJ.

FLYINGSC0T commented 5 years ago

Hi Achill,

Just to clarify, the board I’m using is a TTGO T-Beam and the pins you mention are not broken out on the board.

Thanks,

Have a good weekend also.

George

Sent from my iPhone

On 19 Jan 2019, at 10:28, achillhasler notifications@github.com<mailto:notifications@github.com> wrote:

Hi George, have you tryed to share the spi-bus? [spi_share]https://user-images.githubusercontent.com/46683972/51424547-a4e28680-1bcf-11e9-9c61-24dcf7238290.jpg The lane near processor is a sd-card, away the tft. Both has connction to Ground, MISO, MOSI and SCK other are separate You see MOSI (D23) brown cable MISO (D19) violet cable SCK (D18) green cable

on the jpg you see SD-Card use additional (D5) SS and 3.3V LCD use additional 5V (red cable), D4, RX2 (D16), TX2 (D17), RX0 (D3)

The SD-Card needs no configuation because this are the default pins for VSPI.

The User_setup.h for the shown picture is

define TFT_MISO 19

define TFT_MOSI 23

define TFT_SCLK 18

define TFT_CS 3 // Chip select control pin

define TFT_DC 4 // Data Command control pin

define TFT_RST 17 // Reset pin

define TOUCH_CS 16 // Chip select pin (T_CS) of touch screen (if you have a touchscreen)

nice Weekend

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-455764037, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YeMNduIrLEyHE5sPJhF_QwItS6Ebks5vEuUtgaJpZM4Z8lHJ.

Bodmer commented 5 years ago

@tobimai

Your issue has got hijacked but I am still monitoring this thread if you wish to add more, or please start a new issue.

FLYINGSC0T commented 5 years ago

Hi,

Sorry but I don’t understand when you say my issue has got “hijacked”.

Please explain.

George

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Bodmer notifications@github.com Sent: Tuesday, January 22, 2019 7:49:10 PM To: Bodmer/TFT_eSPI Cc: FLYINGSC0T; Comment Subject: Re: [Bodmer/TFT_eSPI] ILI9341 Screen is only working with disabled Chip Select (#283)

@tobimaihttps://github.com/tobimai

Your issue has got hijacked but I am still monitoring this thread if you wish to add more, or please start a new issue.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-456516973, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YZ5IFpRuhlNLuTzmDqzqzi97ZHfBks5vF10mgaJpZM4Z8lHJ.

Bodmer commented 5 years ago

Hi George,

I just meant that it got used to discuss other possible changes to the library unrelated to your problem!

FLYINGSC0T commented 5 years ago

Hi Bodmer,

Ok no problem then.

I’ve another question - is it possible to connect a USB port to an ESP32 (T-Beam)? I want to connect a USB software defined radio SDR to receive ADS-B transmissions from aircraft.

Thanks again.

Regards, George

Sent from my iPhone

On 22 Jan 2019, at 20:03, Bodmer notifications@github.com<mailto:notifications@github.com> wrote:

Hi George,

I just meant that it got used to discuss other possible changes to the library unrelated to your problem!

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-456522043, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YTjoQRPikKpanx1MsFu3VZYKe7ZQks5vF2BkgaJpZM4Z8lHJ.

Bodmer commented 5 years ago

The T-Beam beahves as a device. I don't think you can use it as a host as it would need software to drive your SDR. You will probably find a Raspberry Pi will interface with the SDR.

FLYINGSC0T commented 5 years ago

Ok. In fact I’ve already implemented SDR’s on a Raspi.

However, I have found that Olimexhttps://www.olimex.com/Products/IoT/ESP32/ESP32-PRO/open-source-hardware has produced an ESP32-Pro board with an ESP32 + USB port.

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Bodmer notifications@github.com Sent: Tuesday, January 22, 2019 8:18:08 PM To: Bodmer/TFT_eSPI Cc: FLYINGSC0T; Comment Subject: Re: [Bodmer/TFT_eSPI] ILI9341 Screen is only working with disabled Chip Select (#283)

The T-Beam beahves as a device. I don't think you can use it as a host as ith would need software to drive your SDR. You will probably find a Raspberry Pi will interface with the SDR.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Bodmer/TFT_eSPI/issues/283#issuecomment-456527267, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlJ_YSfujL0_joilMP_L61t5wm_veRGrks5vF2PwgaJpZM4Z8lHJ.

FLYINGSC0T commented 5 years ago

Hi Bodmer,

Any progress on the implementation of HSPI for the T-Beam ?

Regards.

Ede2016 commented 4 years ago

Maybe this was answered already. I use exactly the same display from Banggood with this code including CS pin and it works fine. https://github.com/espressif/esp-idf/tree/master/examples/peripherals/spi_master