st7735 fails to initialize on Arduino Mega 2560

Question

st7735 fails to initialize on Arduino Mega 2560

amyspark opened this issue 5 years ago · comments

Describe the bug
The library refuses to run on Arduino Mega 2560, it fails to initialize at all when using a ST7735-based TFT controller.

To Reproduce
Employ any of the provided examples. Point rstPin to pin 8, cesPin to pin 10, and dcPin to pin 9 in the relevant st7735_128x160_spi_init call, and wire SCK to 52 and SDA to 51.

Expected behavior
I expected anything (even garbage) to appear on the screen.

Screenshots
I don't have any, as the bug doesn't output any information.

Please complete the following information:

library version: 39f5f3f
LCD display type: ST7735, 1.8'', 160x120 black tab
OS [e.g. linux, windows]: MacOS High Sierra 10.13.6/Windows 7
Platform [e.g. Atmega328p, esp32, etc.]: Atmega2560
IDE if using some: Arduino 1.8.9

Additional context
I've been able to reproduce this as far as 1.6.0 (first release to support st7735).
The Adafruit ST7735 examples also work with exactly the same wiring.

Aleksei · Answer 1 · Sun May 12 2019 07:21:33 GMT+0800 (China Standard Time)

Hello,

Did you try this display with other mcu and ssd1306 library? Could you please check it with Arduino nano, if you have one.
First, I need to understand if the issue relates to Atmega2560 only. I have some st7735 (128x160, don't know the manufacturer exactly), and it works with Arduino Nano and Esp32 Dev boards.
For now, I can only compare to Adafruit source code, and try to understand, what works differently.

Aleksei · Answer 2 · Sun May 12 2019 07:56:33 GMT+0800 (China Standard Time)

Please, check 1.7_dev branch.
Let me know if something changed.

Amyspark · Answer 3 · Sun May 12 2019 08:00:35 GMT+0800 (China Standard Time)

Nothing with 1.7_dev.

As for other MCUs-- my only other is an Arduino Uno (which is still AVR). I should have a STM32 blue pill in a few weeks, I could try then.

Aleksei · Answer 4 · Sun May 12 2019 14:21:41 GMT+0800 (China Standard Time)

What about other spi displays? Do you have monochrome ssd1306 spi oled? Are there any issues with it (in other words, is the issue st7735 only related)?
Could you please, comment out CONFIG_AVR_SPI_ENABLE in UserSettings.h and try again?
Please, check latest commit to 1.7_dev (don't forget to keep CONFIG_AVR_SPI_ENABLE disabled). This branch contains the same initialization sequence as Adafruit code with minimal difference.
Could you pull CS LED pin to ground to have display always activated.

If something of above works for you, I would like to ask you to help with debugging.

Amyspark · Answer 5 · Sun May 12 2019 21:19:07 GMT+0800 (China Standard Time)

I don't have any other screen modules (yet, same as with the blue pill).
No output with any of the options.
No output with any of the options, although I did see in the pull that you changed the initialization code, but for the ILI9163. (Which, by the way, I should get along the blue pill.)
No output with any of the options.

Aleksei · Answer 6 · Mon May 13 2019 06:42:29 GMT+0800 (China Standard Time)

Here are my comments
2. Commenting out CONFIG_AVR_SPI_ENABLE disables internal SPI implementation in ssd1306 library, and makes it to use standard Arduino SPI implementation.
3. Actually il9163 and st7735 is the same controller, s_oled128x160_initData structure, which was modified, is used to initialize st7735 in 128x160 mode. When someone sales such display, you can see often both controllers mentioned "1.8 Inch 128X160 ILI9163/ST7735 TFT LCD Module With PCB Baseboard SPI Serial Port".
Thank you for the help. I will try to reproduce the problem on my setup.

Aleksei · Answer 7 · Mon May 13 2019 21:54:26 GMT+0800 (China Standard Time)

Please, check latest changes. At least on my st7735 128x160 led display, both Adafruit_ST7735 and ssd1306 (1.7_dev) works (with Arduino Nano).

Aleksei · Answer 8 · Thu May 16 2019 07:30:04 GMT+0800 (China Standard Time)

@amyspark Hello
Are there any updates?

Amyspark · Answer 9 · Sat May 18 2019 01:42:46 GMT+0800 (China Standard Time)

Hey @lexus2k , I've been busy this week. I'll be able to test again in the weekend.

(As for testing in other mcu's -- I think they'll arrive by the end of the month.)

Aleksei · Answer 10 · Fri May 24 2019 08:43:52 GMT+0800 (China Standard Time)

@amyspark

Thank you. Hope to see feedback soon.

Amyspark · Answer 11 · Sat May 25 2019 04:58:49 GMT+0800 (China Standard Time)

Hey @lexus2k, it works now! I had to disable CONFIG_AVR_SPI_ENABLE and use Arduino's SPI implementation.

EDIT, in case my earlier comment wasn't clear: the proposed fix works if (and only if) I do not use the provided SPI implementation, and stick to Arduino's. Previous commits do not work in Arduino Mega.

Aleksei · Answer 12 · Sat May 25 2019 10:56:52 GMT+0800 (China Standard Time)

Thank you very much. I appreciate your help.
I will prepare official fix soon

Aleksei · Answer 13 · Sat May 25 2019 17:17:39 GMT+0800 (China Standard Time)

It seems that I fixed built-in SPI issue for Atmega2560. But by default, I switch library to use Arduino's SPI implementation by default, since I don't have Atmega2560 by hand. You can check internal SPI implementation by commenting out CONFIG_PLATFORM_SPI_AVAILABLE.

Amyspark · Answer 14 · Sun May 26 2019 03:11:34 GMT+0800 (China Standard Time)

@lexus2k, I can confirm your SPI implementation works now (uncommented CONFIG_AVR_SPI_AVAILABLE and kept UserSettings.h as is). Thanks for the fix!

Aleksei · Answer 15 · Sun May 26 2019 10:21:19 GMT+0800 (China Standard Time)

ok. Thank you.