Support for M5StickC Plus2 - specifically the Sitronix ST7789V2 display #22599
Replies: 4 comments 22 replies
-
|
Could you share your boot logs with |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
:H,ST7789,240,240,16,SPI,1,,,,,,,*,40 |
Beta Was this translation helpful? Give feedback.
-
|
It's missing the final But moreover the first line is wrong: It is not allowed to have empty fields, it's either a number, -1 if unused, or |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @s-hadinger My display.ini is a 100% copy of https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/ST7789_display.ini The missing # was just a copy past error. The file on the M5StickC Plus 2 does actually include it just like the *. |
Beta Was this translation helpful? Give feedback.
-
|
I tested this and it does not work: |
Beta Was this translation helpful? Give feedback.
-
|
I made some minor progress I guess:
Here is the boot log: 00:00:00.002 HDW: ESP32-PICO-V3-02 v3.1 (PSRAM)
07:23:06.182 CMD: Display 07:28:15.716 RSL: RESULT = {"DisplayMode":2}
07:27:48.507 CMD: DisplayText 12345 07:28:15.638 CMD: DisplayMode 2
|
Beta Was this translation helpful? Give feedback.
-
|
You forgot CS on GPIO5. Hence the display chip does not receive any command |
Beta Was this translation helpful? Give feedback.
-
It's better to use an actual template with |
Beta Was this translation helpful? Give feedback.
-
My mistake indeed. Had it before though ... Now fixed:
|
Beta Was this translation helpful? Give feedback.
-
I am not sure what that means / how to do that? Sorry for my newbie status. |
Beta Was this translation helpful? Give feedback.
-
|
It means using "Configure Template" rather than "Configure Module", and then selecting |
Beta Was this translation helpful? Give feedback.
-
|
Hello @s-hadinger I fixed the missing SPI CS assigment on GPIO 5. |
Beta Was this translation helpful? Give feedback.
-
|
Any change? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, significant progress, but orientation and resolution probably still need attention.
|
Beta Was this translation helpful? Give feedback.
-
|
With regard to the display resolution and orientation I am still struggeling. I adjusted this file: https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/ST7789_display.ini This Tasmota developer created file obviously specifies the resoltion to be 240 x 240. Here: https://docs.m5stack.com/en/core/M5StickC%20PLUS2 it says: 1.14 inch, 135 x 240 Colorful TFT LCD, ST7789v2. And here: https://www.alldatasheet.co.kr/datasheet-pdf/pdf/1663349/SITRONIX/ST7789V2.html and here: https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf it says that at least the Sitronix ST7789V2 chip can do Display Resolution: 240RGB (H) x 320(V), Frame Memory Size: 240 x 320 x 18-bit = 1,382,400 bits, LCD Driver Output Circuits, Source Outputs: 240 RGB Channels, Gate Outputs: 320 Channels. I adjusted my display.ini this way: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @Jason2866 and @s-hadinger. I have tried the different resolution and also the DisplayRotate commands. The result is very different from what I see on other M5 devices like the Core2 or the Lilygo T-Display S3. In the latter two a white on blue Tasmota logo and display driver screen pops up during boot. Once everything is fully loaded, I can use display commands and also HASPmota. The display commands show green font on a black / very dark blue background. On the M5StickC Plus2 despite all the kind help you provided, the splash screen is yellow greyish, does not fill the entire screen, but leaves old analog tv style noise on one side and no display commands produce anything on the remaining white background, after the screen rotation is changed. Without rotation purple on white font is partially displayed but not properly centered. With rotation nothing is displayed on the white background. So I guess more code adaptations are required in the driver? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @Jason2866 and @s-hadinger. I have tried the different resolution and also the DisplayRotate commands. The result is very different from what I see on other M5 devices like the Core2 or the Lilygo T-Display S3. In the latter two a white on blue Tasmota logo and display driver screen pops up during boot. Once everything is fully loaded, I can use display commands and also HASPmota. The display commands show green font on a black / very dark blue background. On the M5StickC Plus2 despite all the kind help you provided, the splash screen is yellow greyish, does not fill the entire screen, but leaves old analog tv style noise on one side and no display commands produce anything on the remaining white background, after the screen rotation is changed. Without rotation purple on white font is partially displayed but not properly centered. With rotation nothing is displayed on the white background. So I guess more code adaptations are required in the driver? |
Beta Was this translation helpful? Give feedback.
-
|
Merry Christmas @s-hadinger and @Jason2866. Motivated by Theo's @arendst engagement in the other thread: #22702 I am hoping we can resolve this issue too. it seems we are close, but not quite there yet. Perhaps it helps to explain what my motivation behind this problem is, since you and others may wonder why on earth do I want to get a lightning sensor: https://tasmota.github.io/docs/AS3935/ to fully work with an M5StickC Plus 2: https://docs.m5stack.com/en/core/M5StickC%20PLUS2 with all of its buttons, LEDs, buzzer and the TFT display (ST7789v2 https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf)? Well, I am a hiker and outdoor enthusiast. Lightning is a real threat. The AS3935 Franklin Lightning Sensor™ chip https://www.sciosense.com/as3935-franklin-lightning-sensor-ic/ is affordable. It was originally developed in a "mountaineering country" - Austria - by AMS (https://ams-osram.com) now owned by the Dutch ScioScience corporation. The M5StickC Plus 2 is a nice hardware package that one can take on a hike. It has buttons to navigate, LEDs and a buzzer to signal alerts and a screen to show the essential data. With HASPmota: https://tasmota.github.io/docs/HASPmota/ I hope/believe I could adapt existing templates for my purpose and a portable, affordable lightning detector could be of interest to the community as well. And to show my commitment and gratitude, I could imagine to donate an M6StickC Plus2 to Theo @arendst or one pf his core development team members. Its Christmaw and perhaps a good time to say thank you for all the hours they put in for us. Let me know Theo @arendst, @s-hadinger, @Jason2866, if that helps / makes any sense. |
Beta Was this translation helpful? Give feedback.
-
|
Can you post pictures of the screen showing the display problems? It is hard to understand with words, a photo would be easier. |
Beta Was this translation helpful? Give feedback.
-
|
Will do ... |
Beta Was this translation helpful? Give feedback.
-
DO NOT DELETE ANY TEXT from this template! Otherwise the issue will be auto-closed.
-->
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
I would like to build a custom device with the AS3935 lightning sensor with the M5StickC Plus2 https://docs.m5stack.com/en/core/M5StickC%20PLUS2 and also like to use HASPmota: https://tasmota.github.io/docs/HASPmota/#gallery-of-widgets to display the data on the screen. For the M5StickC Plus 2 I created and installed a custom tasmota32-lvgl.bin compiled with GitPod. Then I selected the M5StickC template in via the autoconfig section in the tasmota web interface. Since the M5StickC (https://docs.m5stack.com/en/core/m5stickc) has a different GPIO arrangement and display (ST7735S) compared with the M5StickC Plus2 (https://docs.m5stack.com/en/core/M5StickC%20PLUS2) that uses this display ST7789v2 (https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/datasheet/unit/lcd/ST7789V2_SPEC_V1.0.pdf) and (https://github.com/nopnop2002/esp-idf-m5stickC-Plus) I changed the GPIO assignment accordingly in the configure template section of tasmota and also replaced the display.ini with this one: https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/ST7789_display.ini According to this page: https://tasmota.github.io/docs/Universal-Display-Driver/, the ST7789 display should be supported by the universal display driver. However, I only see a black display. Not even the back light can be activated. And of course HASPmota does not work either. I do realize that ST7789 may not be the same as ST7789V2. Can you please help me to correct the display.ini and/or any other settings that help me to get the display to work? Perhaps the universal display driver needs to be upgraded and/or a new template generated for the M5StickC Plus2 as well?
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255:19:59:08.172 CMD: Backlog Template; Module; GPIO 255
19:59:08.174 SRC: WebConsole from 192.168.178.45
19:59:08.175 CMD: Grp 0, Cmd 'BACKLOG', Idx 1, Len 26, Pld -99, Data 'Template; Module; GPIO 255'
19:59:08.199 SRC: Backlog
19:59:08.200 CMD: Grp 0, Cmd 'TEMPLATE', Idx 1, Len 0, Pld -99, Data ''
19:59:08.206 RSL: RESULT = {"NAME":"M5StickC Plus2","GPIO":[7840,0,480,0,0,768,1056,576,1024,736,800,704,0,0,1024,0,0,641,609,800,0,0,1,992,6210,0,0,0,640,608,7872,34,4672,32,0,33],"FLAG":0,"BASE":1}
19:59:08.420 SRC: Backlog
19:59:08.421 CMD: Grp 0, Cmd 'MODULE', Idx 1, Len 0, Pld -99, Data ''
19:59:08.422 RSL: RESULT = {"Module":{"0":"M5StickC Plus2"}}
19:59:08.670 SRC: Backlog
19:59:08.671 CMD: Grp 0, Cmd 'GPIO', Idx 1, Len 3, Pld 255, Data '255'
19:59:08.681 RSL: RESULT = {"GPIO0":{"7840":"I2S WS1"},"GPIO1":{"0":"None"},"GPIO2":{"480":"Buzzer"},"GPIO3":{"0":"None"},"GPIO4":{"0":"None"},"GPIO5":{"768":"SPI CS1"},"GPIO6":{"6210":"Option A3"},"GPIO7":{"0":"None"},"GPIO8":{"0":"None"},"GPIO9":{"1056":"IRsend1"},"GPIO10":{"576":"LedLink_i"},"GPIO11":{"0":"None"},"GPIO12":{"1024":"Display Rst"},"GPIO13":{"736":"SPI CLK1"},"GPIO14":{"800":"SPI DC1"},"GPIO15":{"704":"SPI MOSI1"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"},"GPIO18":{"1024":"Display Rst"},"GPIO19":{"0":"None"},"GPIO20":{"0":"None"},"GPIO21":{"641":"I2C SDA2"},"GPIO22":{"609":"I2C SCL2"},"GPIO23":{"800":"SPI DC1"},"GPIO24":{"0":"None"},"GPIO25":{"0":"None"},"GPIO26":{"0":"None"},"GPIO27":{"992":"Backlight"},"GPIO32":{"640":"I2C SDA1"},"GPIO33":{"608":"I2C SCL1"},"GPIO34":{"7872":"I2S DIN1"},"GPIO35":{"34":"Button3"},"GPIO36":{"4672":"AS3935"},"GPIO37":{"32":"Button1"},"GPIO38":{"0":"None"},"GPIO39":{"33":"Button2"}}
Backlog Rule1; Rule2; Rule3:Status0:weblogto 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
See above.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
Working display. Support by the universal display driver.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
Screen remains black. No backlight.
ADDITIONAL CONTEXT
Add any other context about the problem here.
N/A
(Please, remember to close the issue when the problem has been addressed)
Beta Was this translation helpful? Give feedback.
All reactions