Has anyone been able to get the TFT LCD Breakout 1.8in 128x160 to work in the last few years. It is still being sold by Sparkfun but the comments have ended in 2020. I’ve confirmed wiring, no luck with AI writing even the simplest sketch to test it or getting any of the examples to work. I’m guessing that the libraries and boards are no longer compatible with this unit but no one has noted that out. If someone has been able to get it to work, what version of the libraries and board have you been using. Any help would be appreciated. ty.
Do you have all 3 of the Hyperdisplay libraries? TFT LCD Breakout 1.8in 128x160 Hookup Guide - SparkFun Learn
I definitely had that working a few years ago…I might have been using Arduino 1.8x *legacy) at the time, it might be worth downloading that version (along with re-downloading the hyperdisplay libraries, relevant board packages, etc) as a 2nd install and try it from there (I keep 2 versions installed at all times for this reason! new Arduino and 1.8x)
If the above doesn’t help I can try and find mine and give it a go
One thing to double check is that the signal lines on the “Arduino” boards are correct. E.g. newer boards may have the same physical foot print, but pins have been remapped by the board variant files to provide somewhat different functions.
Example, I battled a problem with a TFT that worked fine when plugged into a Arduino R3 or a Sparkfun Redboard R3 equivalent - but would not work on an Adafruit Metro M4. The Adafruit only supports the Native SPI hardware lines on the ICSP connector. If you are using the “SPI connections” on the traditional D8-D12 (? or what ever), you need to use the software SPI library and it can be marginal.
Most of the SPI TFT chipsets can provide status information from the TFT controller back to the MCU – but only if the TFT board maker actually connects that MISO line to the outside world. Adafruit on some of their boards – do not hook up the SPI line - even though they are on the connector!!! That results in a status of 0x00 always being returned when querying the TFT controller. We get used to thinking of 0x00 as being okay, but it can also mean - no-response on the MISO line.
The AI libraries might not understand which board variant you are using - it might provide code for an older board.
I should have mentioned that it’s connected to Thing Plus - ESP32 WROOM (USB-C). Yes, on all three libraries. I did try earlier versions of the library. while no error codes, I’m still inclined to believe it’s a compatibility issue between the older generation board and ESP32 WROOM. Thank you for responding
D.H. Good point on trying board compatibility. I’ll try a simple sketch with a Arduino Uno R3 or maybe earlier. Thank you for responding.
Most of the libraries - even old – will still work with the newer boards, however you may need to make some adjustments for the speed of the SPI transmissions. Some of the newer boards try clocking out at closer to 16MHz and older shields can have issues (mostly SD cards).
Also check to see which edge of the clock line the SPI device uses. Some of the newer boards and chipsets have different modes that you can select for when it looks (or sends) data. MISO is often on the trailing edge and MOSI on the leading edge of the SCK
I’ll look into adjust the speed of the SPI and which edge of the clock line the SPI device uses. two good suggestions. The latter isn’t something I’ve looked into before. Thank you
Curious – did changing speed of the SPI or the edge (triggering) make a difference for you?