Display --> Rule3 --> "Not enough space" #22644

Nisbo · 2024-12-14T10:44:42Z

Nisbo
Dec 14, 2024

Hello,

I have a NodeMCU ESP-32s V1.1 and a GC9A01 Display from here:
https://de.aliexpress.com/item/1005006100703230.html?

Version: tasmota32-display.bin [Tasmota 14.4.0 (release-display)](https://bit.ly/tasmota)

I try to activate Rule3
with the Display settings from here:
https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/GC9A01_display.ini

Rule3 :H,GC9A01,240,240,16,SPI,*,*,*,*,*,*,*,*,40 :S,2,1,0,1,80,80 :I EF,0 EB,1,14 FE,0 EF,0 EB,1,14 84,1,40 85,1,FF 86,1,FF 87,1,FF 88,1,0A 89,1,21 8A,1,00 8B,1,80 8C,1,01 8D,1,01 8E,1,FF 8F,1,FF B6,2,00,20 3A,1,05 90,4,08,08,08,08 BD,1,06 BC,1,00 FF,3,60,01,04 C3,1,13 C4,1,13 C9,1,22 BE,1,11 E1,2,10,0E DF,3,21,0c,02 F0,6,45,09,08,08,26,2A F1,6,43,70,72,36,37,6F F2,6,45,09,08,08,26,2A F3,6,43,70,72,36,37,6F ED,2,1B,0B AE,1,77 CD,1,63 70,9,07,07,04,0E,0F,09,07,08,03 E8,1,34 62,0C,18,0D,71,ED,70,70,18,0F,71,EF,70,70 63,0C,18,11,71,F1,70,70,18,13,71,F3,70,70 64,7,28,29,F1,01,F1,00,07 66,0A,3C,00,CD,67,45,45,10,00,00,00 67,0A,00,3C,00,00,00,01,54,10,32,98 74,7,10,85,80,00,00,4E,00 98,2,3e,07 35,0 21,0 11,80 29,14 :o,28 :O,29 :A,2A,2B,2C,01 :R,36 :0,C0,00,00,00 :1,A0,00,00,01 :2,00,00,00,02 :3,60,00,00,03 :D,51 #

But I get Not enough space
This are 814 chars and AFAIK there are 1000 chars allowed.

I already tried Rule3 '' to reset the rule and afterwards the code above again but same message.
I never created any rules by my own.

However Rule3 ? returns

11:27:20.841 CMD: Rule3 ?
11:27:20.847 MQT: stat/tasmota_9FE400/RESULT = {"Rule3":{"State":"OFF","Once":"OFF","StopOnError":"OFF","Length":0,"Free":511,"Rules":""}}

Does "Free":511 mean there are only 511 chars possible instead of 1000 chars ?

Dont know if it is related, I get this running the Display command

09:46:20.925 CMD: Display
09:46:20.931 MQT: stat/tasmota_9FE400/RESULT = {"Display":{"Model":17,"Type":0,"Width":0,"Height":0,"Mode":2,"Dimmer":50,"Size":1,"Font":1,"Rotate":0,"Invert":0,"Refresh":2,"Cols":[16,8],"Rows":2}}

There is no width/height. I assume this is related to the missing Rule3 setting

This is my configuration

I also tried SPI instead of SSPI settings.

I don't want to compile my own Firmware, so I can not enable scripting to test other options from here:
https://tasmota.github.io/docs/Universal-Display-Driver/#step-5-configure-the-displayini-descriptor-file

I tried the display.ini option but dont know if this was correct.
I created a new file with the name display.ini under Tool --> Manage File System and put the content inside this file but still nothing to see on the display with "DisplayText Test" or "Display Dimmer"

Any idea how to solve the issue ?

PS: there is also an IR Receiver attached to the ESP

sfromis · 2024-12-14T11:02:00Z

sfromis
Dec 14, 2024

The display.ini strategy is what I'd recommend, and just forgetting about the Rule3 path when you already have a file system available.

However your words "put the content inside this file" does not indicate what exactly you did, as small differences can break stuff. Your basic steps of creating the file looks ok, but the content is important, including how you put it there, as some tools will not work well with copy/paste messing with line breaks. And you should not make it one long line in the file.

BTW. There is no concept of "1000 chars allowed" for the rule sets, indeed it is actually 511 chars max, but with compression this will accommodate rule sets of 1000 chars or more with normal rules. However, the display descriptor text has very little repetition, and will not compress much.

When the setup works, you should get boot time messages like this when you have Weblog 3 activated for details:

00:00:00.045 DSP: File descriptor used
00:00:01.652 DSP: ILI9341 initialized

0 replies

Nisbo · 2024-12-14T11:17:11Z

Nisbo
Dec 14, 2024
Author

I went to
https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/GC9A01_display.ini
and used the button "Copy RAW file"

I went to the display.ini

and hit CTRL+V
saved it and rebooted the ESP

I did a reboot and got this

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.016 UFS: FlashFS mounted with 300 kB free
00:00:00.025 CFG: Loaded from File, Count 57
00:00:00.026 FRC: Some settings have been reset (4)
00:00:00.029 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.037 Project tasmota - IR Bridge Version 14.4.0(release-display)-3_1_0(2024-12-11T09:22:00)
00:00:01.000 WIF: Connecting to AP1 XXXXXXXXXX in mode HT40 as tasmota-9FE400-1024...
00:00:02.739 RSL: RESULT = {"Time":"1970-01-01T00:00:02","IrReceived":{"Protocol":"UNKNOWN","Bits":23,"Hash":"0x210A31E8"}}
00:00:03.537 WIF: Connected
00:00:03.792 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115

with Weblog 3 I get this after a reboot

00:00:00.043 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.044 TYA: Active=0
00:00:00.047 DSP: No valid descriptor found
00:00:00.051 SRC: Restart
00:00:00.052 Project tasmota - IR Bridge Version 14.4.0(release-display)-3_1_0(2024-12-11T09:22:00)
00:00:00.253 WIF: Attempting connection...
00:00:01.000 WIF: Connecting to AP1 xxxxxx in mode HT40 as tasmota-9FE400-1024...
00:00:01.075 WIF: IPv4 192.168.178.115, mask 255.255.255.0, gateway 192.168.178.1
00:00:02.850 IRR: RawLen 6, Overflow 0, Bits 3, Value 0x22AE7A29, Decode -1
00:00:02.852 RSL: RESULT = {"Time":"1970-01-01T00:00:02","IrReceived":{"Protocol":"UNKNOWN","Bits":3,"Hash":"0x22AE7A29"}}
00:00:02.950 IRR: RawLen 6, Overflow 0, Bits 3, Value 0xFEAC02E5, Decode -1
00:00:02.952 RSL: RESULT = {"Time":"1970-01-01T00:00:02","IrReceived":{"Protocol":"UNKNOWN","Bits":3,"Hash":"0xFEAC02E5"}}
00:00:03.412 WIF: IPv6 Local fe80::26dc:c3ff:fe9f:e400%st1
00:00:03.500 WIF: Connected
00:00:03.755 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115
00:00:04.032 RTC: UTC 2024-12-14T11:14:37Z, DST 2024-03-31T02:00:00, STD 2024-10-27T03:00:00
12:14:37.000 RTC: Synced by NTP

1 reply

sfromis Dec 14, 2024

First restart, I see a really bad message there.
00:00:00.026 FRC: Some settings have been reset (4)
Tasmota was detecting a boot loop, and scaled back features until able to boot without crashing.

Second restart, another bad message:
00:00:00.047 DSP: No valid descriptor found
Can't see what happened, but here's a way of avoiding the potential copy/paste pitfalls:

tasmota.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')

However, the descriptor is based on you having hardware SPI configured, not sure why you were even messing around with software SPI, or what your current template is.

Nisbo · 2024-12-14T12:20:07Z

Nisbo
Dec 14, 2024
Author

However, the descriptor is based on you having hardware SPI configured, not sure why you were even messing around with software SPI, or what your current template is.

Not sure what you mean, the SSPI settings ? I just tried this because I found this via google that all examples where using SSPI instead of SPI.
This are the current settings:

I deleted the old display.ini file, rebooted the ESP and ran this command inside the console

tasmota.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')

result:

13:00:53.734 CMD: tasmota.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')
13:00:53.736 SRC: WebConsole from 192.168.178.69
13:00:53.738 CMD: Grp 0, Cmd 'TASMOTA', Idx 1, Len 127, Pld -99, Data '.urlfetch('https://github.com/arendst/Tasmota/raw/refs/heads/development/tasmota/displaydesc/GC9A01_display.ini','display.ini')'
13:00:53.744 MQT: stat/tasmota_9FE400/RESULT = {"Command":"Unknown","Input":"TASMOTA .urlfetch('https://github.com/arendst/Tasmota/raw/refs/"}

but no new display.ini file was created (also checked hidden files)

I power cycled the ESP and now I get this log

00:00:00.002 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.011 UFS: FlashFS mounted with 304 kB free
00:00:00.019 CFG: Loaded from File, Count 63
00:00:00.029 QPC: Count 1
00:00:00.030 CFG: CR 413/699, Busy 0
00:00:00.032 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.033 TYA: Active=0
00:00:00.052 CFG: No '*.autoconf' file found
00:00:00.054 BRY: Berry initialized, RAM used 3136 bytes
00:00:00.060 BRY: No 'preinit.be'
00:00:00.063 DSP: No valid descriptor found
00:00:00.068 SRC: Restart
00:00:00.071 Project tasmota - IR Bridge Version 14.4.0(release-display)-3_1_0(2024-12-11T09:22:00)
00:00:00.084 BRY: No 'autoexec.be'
00:00:00.273 WIF: Attempting connection...
00:00:01.001 WIF: Connecting to AP1 XXXXX in mode HT40 as tasmota-9FE400-1024...
00:00:01.080 WIF: IPv4 192.168.178.115, mask 255.255.255.0, gateway 192.168.178.1
00:00:03.445 WIF: IPv6 Local fe80::26dc:c3ff:fe9f:e400%st1
00:00:03.524 WIF: Connected
00:00:03.730 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115
00:00:04.125 RTC: UTC 2024-12-14T12:16:11Z, DST 2024-03-31T02:00:00, STD 2024-10-27T03:00:00
13:16:11.000 RTC: Synced by NTP

1 reply

sfromis Dec 14, 2024

What I posted was not a Tasmota command, but a Berry function call, which you can run in the Berry REPL console. You can also issue short snippets of Berry code (like that function call) from the regular Tasmota console by prefixing it with the command Br.

Nisbo · 2024-12-14T15:27:07Z

Nisbo
Dec 14, 2024
Author

Now the file was created but still
00:00:00.044 DSP: No valid descriptor found

0 replies

Nisbo · 2024-12-17T23:39:28Z

Nisbo
Dec 17, 2024
Author

Some days later, the problem is still there.

What I did in between, erased the device and installed latest 14.4.1 display release. This time the IR Receiver is not enabled. Apart from this, the GPIO settings are the same.

If I boot with Option A3 enabled and without display.ini, the boot is fine without errors

00:00:00.002 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.026 UFS: FlashFS mounted with 304 kB free
00:00:00.042 CFG: Loaded from File, Count 23
00:00:00.050 QPC: Count 1
00:00:00.053 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.084 BRY: Berry initialized, RAM used 3136 bytes
00:00:00.102 Project tasmota - Tasmota Version 14.4.1(release-display)-3_1_0(2024-12-15T13:32:56)
00:00:01.000 WIF: Connecting to AP1 NissanNet 2,4GHz Channel 6 BSSId 18:E8:29:94:E0:09 in mode HT40 as tasmota-9FE400-1024...
00:00:03.475 WIF: Connected
00:00:03.681 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115
00:23:05.656 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"14.4.1(release-display)","FallbackTopic":"cmnd/DVES_9FE400_fb/","GroupTopic":"cmnd/tasmotas/"}}
00:23:05.669 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-9FE400-1024","IPAddress":"192.168.178.115","IP6Global":"","IP6Local":"fe80::26dc:c3ff:fe9f:e400%st1"}}
00:23:05.681 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":12}}
00:23:05.693 RSL: RESULT = {"POWER":"ON"}
00:23:05.694 RSL: POWER = ON
00:23:07.958 QPC: Reset
00:23:09.940 RSL: STATE = {"Time":"2024-12-18T00:23:09","Uptime":"0T00:00:09","UptimeSec":9,"Heap":167,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":33},"POWER":"ON","Wifi":{"AP":1,"SSId":"NissanNet 2,4GHz","BSSId":"18:E8:29:94:E0:09","Channel":6,"Mode":"HT40","RSSI":68,"Signal":-66,"LinkCount":1,"Downtime":"0T00:00:04"}}

If I boot with Option A3 enabled and with display.ini, the boot produce errors / reboots

00:32:02.215 APP: Restarting
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:268
ho 0 tail 12 room 4
load:0x40078000,len:13168
load:0x40080400,len:4
load:0x40080404,len:2928
entry 0x4008055c

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.034 UFS: FlashFS mounted with 300 kB free
00:00:00.054 CFG: Loaded from File, Count 25
00:00:00.062 QPC: Count 1
00:00:00.065 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.102 BRY: Berry initialized, RAM used 3136 bytes
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x400913f0  PS      : 0x00060633  A0      : 0x801d0163  A1      : 0x3ffb1df0  
A2      : 0xb83f804c  A3      : 0xffffffff  A4      : 0x00060620  A5      : 0x00060623  
A6      : 0x07ffffff  A7      : 0x0000abab  A8      : 0x80091fce  A9      : 0x3ffb1de0  
A10     : 0x00000003  A11     : 0x00060623  A12     : 0x00060620  A13     : 0xbaad5678  
A14     : 0x0ccccccc  A15     : 0x3ffae87c  SAR     : 0x00000001  EXCCAUSE: 0x0000001c  
EXCVADDR: 0xb83f804c  LBEG    : 0x401062fc  LEND    : 0x40106512  LCOUNT  : 0x000000fe  


Backtrace: 0x400913ed:0x3ffb1df0 0x401d0160:0x3ffb1e10 0x4014308e:0x3ffb1e50 0x401312d0:0x3ffb1e70 0x40105fff:0x3ffb1ea0 0x4010723d:0x3ffb2010 0x4010a3d1:0x3ffb2050 0x400f4fea:0x3ffb2070 0x4010ab3d:0x3ffb2130 0x400dd998:0x3ffb2150 0x400d7f60:0x3ffb2170 0x40136852:0x3ffb2290




ELF file SHA256: 2dfe4a0cb

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:268
ho 0 tail 12 room 4
load:0x40078000,len:13168
load:0x40080400,len:4
load:0x40080404,len:2928
entry 0x4008055c

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.034 UFS: FlashFS mounted with 300 kB free
00:00:00.054 CFG: Loaded from File, Count 25
00:00:00.056 FRC: Some settings have been reset (2)
00:00:00.059 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.096 BRY: Berry initialized, RAM used 3136 bytes
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x400913f0  PS      : 0x00060633  A0      : 0x801d0163  A1      : 0x3ffb1df0  
A2      : 0xb83f804c  A3      : 0xffffffff  A4      : 0x00060620  A5      : 0x00060623  
A6      : 0x07ffffff  A7      : 0x0000abab  A8      : 0x80091fce  A9      : 0x3ffb1de0  
A10     : 0x00000003  A11     : 0x00060623  A12     : 0x00060620  A13     : 0xbaad5678  
A14     : 0x0ccccccc  A15     : 0x3ffae87c  SAR     : 0x00000001  EXCCAUSE: 0x0000001c  
EXCVADDR: 0xb83f804c  LBEG    : 0x401062fc  LEND    : 0x40106512  LCOUNT  : 0x000000fe  


Backtrace: 0x400913ed:0x3ffb1df0 0x401d0160:0x3ffb1e10 0x4014308e:0x3ffb1e50 0x401312d0:0x3ffb1e70 0x40105fff:0x3ffb1ea0 0x4010723d:0x3ffb2010 0x4010a3d1:0x3ffb2050 0x400f4fea:0x3ffb2070 0x4010ab3d:0x3ffb2130 0x400dd998:0x3ffb2150 0x400d7f60:0x3ffb2170 0x40136852:0x3ffb2290




ELF file SHA256: 2dfe4a0cb

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:268
ho 0 tail 12 room 4
load:0x40078000,len:13168
load:0x40080400,len:4
load:0x40080404,len:2928
entry 0x4008055c

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.034 UFS: FlashFS mounted with 300 kB free
00:00:00.054 CFG: Loaded from File, Count 25
00:00:00.056 FRC: Some settings have been reset (3)
00:00:00.059 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.096 BRY: Berry initialized, RAM used 3136 bytes
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x400913f0  PS      : 0x00060633  A0      : 0x801d0163  A1      : 0x3ffb1df0  
A2      : 0xb83f804c  A3      : 0xffffffff  A4      : 0x00060620  A5      : 0x00060623  
A6      : 0x07ffffff  A7      : 0x0000abab  A8      : 0x80091fce  A9      : 0x3ffb1de0  
A10     : 0x00000003  A11     : 0x00060623  A12     : 0x00060620  A13     : 0xbaad5678  
A14     : 0x0ccccccc  A15     : 0x3ffae87c  SAR     : 0x00000001  EXCCAUSE: 0x0000001c  
EXCVADDR: 0xb83f804c  LBEG    : 0x401062fc  LEND    : 0x40106512  LCOUNT  : 0x000000fe  


Backtrace: 0x400913ed:0x3ffb1df0 0x401d0160:0x3ffb1e10 0x4014308e:0x3ffb1e50 0x401312d0:0x3ffb1e70 0x40105fff:0x3ffb1ea0 0x4010723d:0x3ffb2010 0x4010a3d1:0x3ffb2050 0x400f4fea:0x3ffb2070 0x4010ab3d:0x3ffb2130 0x400dd998:0x3ffb2150 0x400d7f60:0x3ffb2170 0x40136852:0x3ffb2290




ELF file SHA256: 2dfe4a0cb

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:268
ho 0 tail 12 room 4
load:0x40078000,len:13168
load:0x40080400,len:4
load:0x40080404,len:2928
entry 0x4008055c

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.034 UFS: FlashFS mounted with 300 kB free
00:00:00.054 CFG: Loaded from File, Count 25
00:00:00.056 FRC: Some settings have been reset (4)
00:00:00.059 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.066 Project tasmota - Tasmota Version 14.4.1(release-display)-3_1_0(2024-12-15T13:32:56)
00:00:01.000 WIF: Connecting to AP1 NissanNet 2,4GHz Channel 6 BSSId 18:E8:29:94:E0:09 in mode HT40 as tasmota-9FE400-1024...
00:00:03.438 WIF: Connected
00:00:03.693 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115
00:32:08.703 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"14.4.1(release-display)","FallbackTopic":"cmnd/DVES_9FE400_fb/","GroupTopic":"cmnd/tasmotas/"}}
00:32:08.716 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-9FE400-1024","IPAddress":"192.168.178.115","IP6Global":"","IP6Local":"fe80::26dc:c3ff:fe9f:e400%st1"}}
00:32:08.730 RSL: INFO3 = {"Info3":{"RestartReason":{"Exception":28,"Reason":"LoadProhibited","EPC":"400913f0","EXCVADDR":"b83f804c","CallChain":["400913ed","401d0160","4014308e","401312d0","40105fff","4010723d","4010a3d1","400f4fea","4010ab3d","400dd998","400d7f60","40136852"]},"BootCount":13}}
00:32:08.752 RSL: RESULT = {"POWER":"ON"}
00:32:08.763 RSL: POWER = ON
00:32:10.949 QPC: Reset
00:32:12.948 RSL: STATE = {"Time":"2024-12-18T00:32:12","Uptime":"0T00:00:09","UptimeSec":9,"Heap":173,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"POWER":"ON","Wifi":{"AP":1,"SSId":"NissanNet 2,4GHz","BSSId":"18:E8:29:94:E0:09","Channel":6,"Mode":"HT40","RSSI":70,"Signal":-65,"LinkCount":1,"Downtime":"0T00:00:04"}}

If I boot with Option A3 disabled and with display.ini, the boot is fine without errors

00:35:43.219 APP: Restarting
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:268
ho 0 tail 12 room 4
load:0x40078000,len:13168
load:0x40080400,len:4
load:0x40080404,len:2928
entry 0x4008055c

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.008 UFS: FlashFS mounted with 300 kB free
00:00:00.015 CFG: Loaded from File, Count 27
00:00:00.023 QPC: Count 1
00:00:00.026 SPI: Bus1 using GPIO18(CLK) and GPIO23(MOSI)
00:00:00.048 BRY: Berry initialized, RAM used 3136 bytes
00:00:00.057 Project tasmota - Tasmota Version 14.4.1(release-display)-3_1_0(2024-12-15T13:32:56)
00:00:01.000 WIF: Connecting to AP1 NissanNet 2,4GHz Channel 6 BSSId 18:E8:29:94:E0:09 in mode HT40 as tasmota-9FE400-1024...
00:00:03.538 WIF: Connected
00:00:03.794 HTP: Web server active on tasmota-9FE400-1024 with IP address 192.168.178.115
00:35:47.706 RSL: INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"14.4.1(release-display)","FallbackTopic":"cmnd/DVES_9FE400_fb/","GroupTopic":"cmnd/tasmotas/"}}
00:35:47.719 RSL: INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-9FE400-1024","IPAddress":"192.168.178.115","IP6Global":"","IP6Local":"fe80::26dc:c3ff:fe9f:e400%st1"}}
00:35:47.731 RSL: INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":14}}
00:35:49.976 QPC: Reset
00:35:51.975 RSL: STATE = {"Time":"2024-12-18T00:35:51","Uptime":"0T00:00:09","UptimeSec":9,"Heap":168,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":0,"Berry":{"HeapUsed":3,"Objects":33},"Wifi":{"AP":1,"SSId":"NissanNet 2,4GHz","BSSId":"18:E8:29:94:E0:09","Channel":6,"Mode":"HT40","RSSI":70,"Signal":-65,"LinkCount":1,"Downtime":"0T00:00:04"}}

So I assume there is something wrong with the GC9A01_display.ini
https://github.com/arendst/Tasmota/blob/development/tasmota/displaydesc/GC9A01_display.ini
or with the universal driver itself. Or did I miss to configure something ?

1 reply

arendst Dec 18, 2024
Maintainer

What happens if you execute command ‘displaymodel 17’ first before enabling Option A3?

Nisbo · 2024-12-18T06:40:14Z

Nisbo
Dec 18, 2024
Author

It returns 0

07:36:10.838 CMD: displaymodel 17
07:36:10.845 MQT: stat/tasmota_9FE400/RESULT = {"DisplayModel":0}

0 replies

Nisbo · 2024-12-18T08:31:34Z

Nisbo
Dec 18, 2024
Author

The display is ... lets call it ... "working"
At least it is on and I can see a little bit.

The trick was to modify the display.ini file.

the original 1st line is

:H,GC9A01,240,240,16,SPI,*,*,*,*,*,*,*,*,40

I had to change it to

:H,GC9A01,240,240,16,SPI,1,*,*,*,*,*,*,*,40

to enable Hardware SPI.

After Restart I get this lucky log

09:21:10.301 APP: Restarting
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:268
ho 0 tail 12 room 4
load:0x40078000,len:13168
load:0x40080400,len:4
load:0x40080404,len:2928
entry 0x4008055c

00:00:00.001 HDW: ESP32-D0WD-V3 v3.1 
00:00:00.045 UFS: FlashFS mounted with 300 kB free
00:00:00.064 CFG: Loaded from File, Count 73
00:00:00.072 QPC: Count 1
00:00:00.075 SPI: Bus1 using GPIO14(CLK) and GPIO15(MOSI)
00:00:00.117 BRY: Berry initialized, RAM used 3136 bytes
00:00:00.796 DSP: GC9A01 initialized
00:00:00.804 Project tasmota - Tasmota Version 14.4.1(release-display)-3_1_0(2024-12-15T13:32:56)

Btw I changed the GIPOs in between for testing

After this DisplayMode 2

09:23:35.201 CMD: DisplayMode 2
09:23:35.483 MQT: stat/tasmota_9FE400/RESULT = {"DisplayMode":2}
09:23:39.028 CMD: display
09:23:39.035 MQT: stat/tasmota_9FE400/RESULT = {"Display":{"Model":17,"Type":0,"Width":240,"Height":240,"Mode":2,"Dimmer":50,"Size":1,"Font":1,"Rotate":0,"Invert":0,"Refresh":2,"Cols":[16,8],"Rows":2}}

to enable the Text Mode and after this
DisplayText dsgfsdgdsgsdfgsdfghsfdgd
to show something

09:25:16.417 CMD: DisplayText dsgfsdgdsgsdfgsdfghsfdgd
09:25:16.423 MQT: stat/tasmota_9FE400/RESULT = {"DisplayText":"dsgfsdgdsgsdfgsdfghsfdgd"}

and now there is the "But-Part" ^^
I can see something but only on the very top of the display and DisplayDimmer is not working
DisplayDimmer 10
or any other numbers turn on the display with the same brightness. With DisplayDimmer 0 I can turn it off. At least this is working. ^^

Any ideas ?

EDIT: OK, found a documentation
https://github.com/tasmota/docs-7.1/blob/master/Displays.md#examples
for positioning the text, so please disregard this question

For the search function, try this
DisplayMode 0

DisplayText [x85y95h130v30h-130v-30s2p7x90y100]37.25 C

However, its still not possible to change the brightness

0 replies

Nisbo · 2024-12-18T11:37:58Z

Nisbo
Dec 18, 2024
Author

Another strange thing is that some colors are wrong

DisplayText [z][Bi0Ci1][Ci7s4x50y80t][Ci17s2x70y140T]

Bi0 and Ci1 are working but the time should be yellow and die Date should be orange. Some other colors are correct.
I also tried the 5 digit code for orange C64768 with the same wrong output

Its a little bit hard to see but the time is light blue and the date is light green instead of yellow and orange.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Display --> Rule3 --> "Not enough space" #22644

{{title}}

Replies: 8 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Display --> Rule3 --> "Not enough space" #22644

Nisbo Dec 14, 2024

Replies: 8 comments · 3 replies

sfromis Dec 14, 2024

Nisbo Dec 14, 2024 Author

sfromis Dec 14, 2024

Nisbo Dec 14, 2024 Author

sfromis Dec 14, 2024

Nisbo Dec 14, 2024 Author

Nisbo Dec 17, 2024 Author

arendst Dec 18, 2024 Maintainer

Nisbo Dec 18, 2024 Author

Nisbo Dec 18, 2024 Author

Nisbo Dec 18, 2024 Author

Nisbo
Dec 14, 2024

Replies: 8 comments 3 replies

sfromis
Dec 14, 2024

Nisbo
Dec 14, 2024
Author

Nisbo
Dec 14, 2024
Author

Nisbo
Dec 14, 2024
Author

Nisbo
Dec 17, 2024
Author

arendst Dec 18, 2024
Maintainer

Nisbo
Dec 18, 2024
Author

Nisbo
Dec 18, 2024
Author

Nisbo
Dec 18, 2024
Author