carbuthn
March 20, 2024, 3:20pm
43
@clydebarrow , Hi the display was working good with the external components that you wrote, but when I went to update the display with the new release the yaml file will not validate. I replaced the spi section to match the new documentation.
spi:
id: quad_spi
clk_pin: 47
data_pins:
- 18
- 7
- 48
- 5
It appears the new documentation for the T3 Amoled should be the same as the T4 display, which compiles.
spi:
id: quad_spi
type: quad
clk_pin: 47
data_pins: [18, 7, 48, 5]
Great work by the way, Thanks
1 Like
I just got a T-Display-S3 unit. The pre-flashed code worked when I plugged the device in, so I know the hardware and display works.
Following the guide above no longer seems to work.
Would anyone be so kind as to upload a complete yaml file somewhere that works with the latest versions of everything?
Would LOVE to get this device working.
In the logs I can see the following warning emitted every second:
Component display took a long time for an operation (295 ms).
I have uploaded my sample code here, including the full log file:
carbuthn
May 20, 2024, 11:06am
45
The display that you show on github (from Amazon) is not an Amoled display. The Amoled display has the buttons on the sides.
The code I listed is still working on the display I have with the change made to the spi shown above your post.
For the non-AMOLED T-Display S3 see this PR:
esphome:dev ← clydebarrow:i8080
opened 09:37AM - 15 Apr 24 UTC
# What does this implement/fix?
## Types of changes
Add a new bus para… llel type - `i80` - used for interfacing LCD display controllers. This is used in a similar way to the `spi` component, and is utilised by the `ili9xxx` display driver, enabling support for the Seeed [W32-SC01-Plus](https://www.seeedstudio.com/WT32-3-5-Inch-Display-p-5542.html) and the [LilyGo T-Display S3](https://www.lilygo.cc/products/t-display-s3?variant=42589373268149).
The changes have been tested on the above as well as numerous SPI interfaced displays previously supported by `ili9xxx` to ensure that nothing has been broken in the process.
- [ ] Bugfix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Other
**Related issue or feature (if applicable):** fixes
- https://github.com/esphome/feature-requests/issues/2387
- https://github.com/esphome/feature-requests/issues/901
-
**Pull request in [esphome-docs](https://github.com/esphome/esphome-docs) with documentation (if applicable):** esphome/esphome-docs#3761
## Test Environment
- [x] ESP32
- [x] ESP32 IDF
- [ ] ESP8266
- [x] RP2040
- [ ] BK72xx
- [ ] RTL87xx
## Example entry for `config.yaml`:
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR. Furthermore, for new integrations, it gives an impression of how
the configuration would look like.
Note: Remove this section if this PR does not have an example entry.
-->
```yaml
# Example config.yaml
i80:
dc_pin: 7
wr_pin: 8
rd_pin: 9
data_pins:
- 39
- 40
- 41
- 42
-
ignore_strapping_warning: true
number: 45
-
ignore_strapping_warning: true
number: 46
- 47
- 48
display:
- platform: ili9xxx
bus_type: i80
cs_pin: 6
reset_pin: 5
model: st7789v
```
## Checklist:
- [x] The code change is tested and works locally.
- [x] Tests have been added to verify that the new code works (under `tests/` folder).
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated in [esphome-docs](https://github.com/esphome/esphome-docs).
1 Like
