-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
Support ESP32-2432S024R " Resistive Touch USB Type-C Only #660
Comments
We don't have this device to setup the touchscreen and screen, so it's difficult to do things blindly.. Do you have repository examples of codes that work for this display? So we can get information and implement it? |
Thanks for, no there isn't. But there is firmware (marauder) that supports my board: https://github.com/Fr4nkFletcher/ESP32-Marauder-Cheap-Yellow-Display |
i think this one would work : https://github.com/rzeldent/esp32-smartdisplay-demo |
I think this one will also work |
I have a beta version installed for CYD-2432S024c, and CYD-2432W28. But all had two problems. More precisely: the touchscreen does not work, and the animations do not work correctly (I mean the bruce animation) |
Different board, different touch pins/drive
If you're running the Launcher Version, it doesn't have the animation |
yes, I understand |
will it be possible to support CYD-2432S024r? |
Touch function and battery level indicator is working well on this firmware. https://github.com/Spooks4576/Ghost_ESP |
I sent a patch for it now, will be available in about 15 minutes to install Battery level indicator for these CYD boards rely on a separate device connected to the GPIO.. we (Bruce devs) prefere to use these GPIO for RF, RFID, GPS and more interesting stuff than showing a percentage of battery on screen.. so, if it comes for us to decide to add or not, the answer is "its not gonna happen".. |
Installed a beta released CYD-2432S024R firmware now with bruce.computer/flasher. The touch function does not working yet. :-( |
The touchscreen doesn't work. But I can send you the logs, maybe they will help in some way. rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) |
Touchscreen in this device shares the same SPI bus with tft.. it needs other approach.. I'll try something later |
The ghost ESP is working. Can you implement that setups into your firmware? https://github.com/Spooks4576/Ghost_ESP 471816975_9439605289394928_6048434060619588823_n.mp4 |
Ghost uses lvgl and esp-idf for his project.. his libs doesn't work on our environment.. there's an easy way out for this problem.. I'll try it out in a few hours |
Thank you for yor effort. |
ok, thanks for supporting this device. I have a question. Should I send you the logs during testing? |
It is a good practice, as I don't have this device |
I would test it too but the flex tape that connects the touch screen to the esp has a little cut and it doesn't work unfortunately. |
Can you try installin the Beta from my repo?? Flasher is here https://bmorcelli.github.io/Bruce/flasher |
there are problems with loading here is a screenshot: I'll send the logs now |
ndler Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (12101) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (17101) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (17101) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED ets Jul 29 2019 12:21:46 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (7088) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (12088) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (12088) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (17088) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (17088) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (22088) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (22088) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (27088) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (27088) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (32088) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E32B6:0x3FFC1BBC |<-CORRUPTED E (32088) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED |
ok, updated again... you can try again in https://bmorcelli.github.io/Bruce/flasher |
|
logs: E (12103) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E329E:0x3FFC1BBC |<-CORRUPTED E (12103) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED ets Jul 29 2019 12:21:46 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) Backtrace: 0x401E329E:0x3FFC1BBC |<-CORRUPTED E (7109) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (12109) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E329E:0x3FFC1BBC |<-CORRUPTED E (12109) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED E (17109) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: Backtrace: 0x401E329E:0x3FFC1BBC |<-CORRUPTED E (17109) task_wdt: Print CPU 1 backtrace Backtrace: 0x400849E5:0x3FFC23EC |<-CORRUPTED |
I tried a last trick, feeding the watchdog.. you can try again |
nothing has changed, it hangs on loading. But when pressing "reset" the inscription can be complete or vice versa. |
could you check the firmware? |
I tried using the touch driver from TFT_eSPI, but didn't work.. I will make changes on our cyd touch lib to use the shared bus when I have time |
New try on https://bmorcelli.github.io/Bruce/flasher |
I installed the latest version. The screen color is inverted. |
just relaod the page |
touchscreen doesn't work, evrerything is loading. I send logs: ets Jul 29 2019 12:21:46 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) |
Can you add support of ESP32-2432S024R with capacitive touch? Touch controller is CST820 |
I believe this one is already ported in this option "CYD-2432W328C(inv_colors)_and_CYD-2432S024C" |
New try on https://bmorcelli.github.io/Bruce/flasher I need Serial Logs when touching screen.. |
|
I hope this gave you something, because when you press the touchscreen, nothing is written in the logs. |
Nice... now I am very comfident that it will work: try on https://bmorcelli.github.io/Bruce/flasher (Beta Release) |
Tested this version, and looks like working not bad. Need more time for explore stability |
touchscreen doesn't work still the same |
New Commit on https://bmorcelli.github.io/Bruce/flasher (Beta Release) |
no boot |
I love these logs.. Pushed one more commit, feeding the watchdog.. hope it works |
ok i send logs |
the problem persists |
New Commit on https://bmorcelli.github.io/Bruce/flasher (Beta Release) Now I fully disabled the watchdog (or tried to) Waiting for logs |
Ok, I'll test it when I'm home. |
|
Good day! My name is Ruslan, and I'm writing from Ukraine. Recently, I encountered a problem with the firmware for the CYD-2432S024R (Type-C). The standard CYD-2432S028 firmware was installed on it, but there was no image. However, the CYD-2432W328C firmware displayed the image, but the touch screen didn't work.
I tried installing all the firmware versions from the official website, but nothing worked. The display itself is functional, as I've used it before. I also confirmed its operability with the Marauder firmware, where everything works fine.
I hope you can add support for this board. Many users on forums and Discord channels have reported similar issues with this board.
The text was updated successfully, but these errors were encountered: