Problem with P123 after custom build
Moderators: grovkillen, Stuntteam, TD-er
Problem with P123 after custom build
Hi Guys
I tried to flash a new custom build today (so as to get an up to date P097 on my test ESP32)
I had 2 devices configured:
a TFT (P116) and a I2C touch screen (P123).
Both were working fine on my previous FW version but when I flashed latest the device started behaving erratically.
I thought it might be a problem with P123 so I tried to delete it but the bottom half (including the Delete button) of the I2C touch screen device config page does not load so I cant delete it.
I can revert to previous FW and it works fine so I wondered if there had been anything done to P123 recently which may be causing my problem or if I could have done something wrong in my custom build ?
Thx
I tried to flash a new custom build today (so as to get an up to date P097 on my test ESP32)
I had 2 devices configured:
a TFT (P116) and a I2C touch screen (P123).
Both were working fine on my previous FW version but when I flashed latest the device started behaving erratically.
I thought it might be a problem with P123 so I tried to delete it but the bottom half (including the Delete button) of the I2C touch screen device config page does not load so I cant delete it.
I can revert to previous FW and it works fine so I wondered if there had been anything done to P123 recently which may be causing my problem or if I could have done something wrong in my custom build ?
Thx
Re: Problem with P123 after custom build
Can you try using a different browser? There is a report of erratic behavior when using Chrome.
/Ton (PayPal.me)
Re: Problem with P123 after custom build
Also a tip so you don't need to delete a task...
On the tools page, you can enter some commands.
To disable a task:
With N being the task index you want to disable.
With "save" as command you will save the disabled state to flash so it will not start next time at boot.
If a task behaves erratic, this is often a good way to test as "taskenable" and "taskdisable" just enable/disable it in memory.
So what I frequently do (while developing) is that I save settings with the task disabled and then give the command to enable it.
When things start crashing, I just need to reboot and the "enabled" state was not saved so it will not start that task.
On the tools page, you can enter some commands.
To disable a task:
Code: Select all
taskdisable,N
With "save" as command you will save the disabled state to flash so it will not start next time at boot.
If a task behaves erratic, this is often a good way to test as "taskenable" and "taskdisable" just enable/disable it in memory.
So what I frequently do (while developing) is that I save settings with the task disabled and then give the command to enable it.
When things start crashing, I just need to reboot and the "enabled" state was not saved so it will not start that task.
Re: Problem with P123 after custom build
ath, TD-er
Thanks for tips and suggestions ..
Unfortunately, neither helped.
I have spent several hours flashing various custom build combinations and I now have a long list of combinations (which I wont bore you with) that Ive tried, including blank 16M, to clear flash first but I keep comming back to the same point where the device enters a reboot loop or freezes when I try to edit the I2C touch task ...
I have created custom builds that work with all plugins that I require however I cannot get a (stable) custom build if it includes P123 I2C Touch.
BTW - If I load the ESP32 Max build the touch screen does works fine and doesnt cause a problem however P97 is an old version without "wake from deepsleep " option which is a function I specifically wanted.
I've tried hard to rule out user error but I have no other ideas so,for now, I think I'll just use the Max build (without P97 Deepsleep wake up) and see if anyone else experiences the same problem with a custom build using P123.
I'm happy to try any further testing you suggest however I cant shake off the feeling that something has changed in P123 since the Christmas 2024 release ?
Thanks for tips and suggestions ..
Unfortunately, neither helped.
I have spent several hours flashing various custom build combinations and I now have a long list of combinations (which I wont bore you with) that Ive tried, including blank 16M, to clear flash first but I keep comming back to the same point where the device enters a reboot loop or freezes when I try to edit the I2C touch task ...
I have created custom builds that work with all plugins that I require however I cannot get a (stable) custom build if it includes P123 I2C Touch.
BTW - If I load the ESP32 Max build the touch screen does works fine and doesnt cause a problem however P97 is an old version without "wake from deepsleep " option which is a function I specifically wanted.
I've tried hard to rule out user error but I have no other ideas so,for now, I think I'll just use the Max build (without P97 Deepsleep wake up) and see if anyone else experiences the same problem with a custom build using P123.
I'm happy to try any further testing you suggest however I cant shake off the feeling that something has changed in P123 since the Christmas 2024 release ?
Re: Problem with P123 after custom build
This testing, was it done using an ESP32 or an ESP8266? (I'm guessing an ESP32, but want to be sure)
/Ton (PayPal.me)
Re: Problem with P123 after custom build
WT32-SC01 V3.3 16M flash
Re: Problem with P123 after custom build
We've done an investigation, and still searching for a specific cause and then a solution.
Tested on a WT32 SC01, like you use.
There's something funky going on in the loading and parsing of settings of P123 (and probably a couple of other plugins that use the same method) that seems somehow related to the ESP32 hardware version in use. No conclusions yet, just suspicions.
Please don't spend much time investigating this, as because of above issue, while loading the settings, the ESP is crashing and rebooting, that's why you see only half of the settings page.
Tested on a WT32 SC01, like you use.
There's something funky going on in the loading and parsing of settings of P123 (and probably a couple of other plugins that use the same method) that seems somehow related to the ESP32 hardware version in use. No conclusions yet, just suspicions.
Please don't spend much time investigating this, as because of above issue, while loading the settings, the ESP is crashing and rebooting, that's why you see only half of the settings page.
/Ton (PayPal.me)
Re: Problem with P123 after custom build
As ever - I appreciate your (and TD-ers) help
Re: Problem with P123 after custom build
You could try one of these builds, which hopefully fixes your crashes.
https://github.com/letscontrolit/ESPEas ... 3147077146
https://github.com/letscontrolit/ESPEas ... 3147077146
Re: Problem with P123 after custom build
ThxTD-er wrote: ↑05 Feb 2025, 09:51 You could try one of these builds, which hopefully fixes your crashes.
https://github.com/letscontrolit/ESPEas ... 3147077146
I tried "Bin-ESP32-max_ESP32_16M8M_LittleFS_ETH-20250204_PR_5245_13147077146" but unfortunately got the same problem.
Re: Problem with P123 after custom build
OK, thanks for reporting.
This means we still got work to do.
I am not able to reproduce the crash, but Ton was able to, so that's why we consider the possibility is may have to do with some very specific ESP32 silicon revision as Ton was using the same board as you have and the reported CPU revision for that board was rev. 1.00
This means we still got work to do.
I am not able to reproduce the crash, but Ton was able to, so that's why we consider the possibility is may have to do with some very specific ESP32 silicon revision as Ton was using the same board as you have and the reported CPU revision for that board was rev. 1.00
Re: Problem with P123 after custom build
Found the bug... it is a bug in Arduino code.
See: https://github.com/espressif/arduino-esp32/issues/10938
We can make a work-around tomorrow and have to check other places where it might occur.
See: https://github.com/espressif/arduino-esp32/issues/10938
We can make a work-around tomorrow and have to check other places where it might occur.
Who is online
Users browsing this forum: No registered users and 1 guest