Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct GPIO pins for T3-S3-Amoled Plus #87

Open
carbuthn opened this issue Jan 14, 2025 · 6 comments
Open

Correct GPIO pins for T3-S3-Amoled Plus #87

carbuthn opened this issue Jan 14, 2025 · 6 comments
Labels

Comments

@carbuthn
Copy link

I am having problems get the correct pins for the QSPI and Display. I set per the picture showing the pins but display remains blank.
spi:
id: quad_spi
type: quad
clk_pin: 47
data_pins: [18, 7, 48, 5]

i2c:
sda: 3
scl: 2

display:
cs_pin: 6
reset_pin: 17
enable_pin: 38

I am using ESPHome and have several of the Non-Plus versions that work correctly.

Do you have a list that shows the correct pins for the Amoled Plus?

@lewisxhe
Copy link
Contributor

Amoled Plus is an SPI interface, not QSPI.
image

@carbuthn
Copy link
Author

That is the picture that I mentioned, it does not work with either of the two T-display Amoled Pluses that I have. The description says that it uses a QSPI but the picture above does not say what the four data pins are. The picture is similar to the regular Amoled display (non-plus) and those work with the pins in my original post. I also tried setting the enable to pin 9 instead of 38 but that did not work.

@lewisxhe
Copy link
Contributor

amoled plus is a driver for the SPI interface, not QSPI. QSPI is only 1.91 amoled, not amoled plus.

esphome currently does not seem to have an adapter for amoled plus

@carbuthn
Copy link
Author

Thanks I will change the code that I was using to see if I can get it to work with the SPI Interface.

It may help to change the description page that currently says QSPI for the Amoled plus.

Image

@lewisxhe
Copy link
Contributor

Thanks, I will report this to sales

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants