Usermods TTGO-T-Display does not compile #4375
Comments
|
@spiff72 FYI if you are the author of this |
|
It looks like TFT_eSPI verison 2.5.33 is the last one that does not have a compile error with our WLED default framework. lib_deps =
${esp32.lib_deps}
TFT_eSPI @ 2.5.33 ;; this is the last version that compiles with the WLED default framework - newer versions require platform = espressif32 @ ^6.3.2 |
softhack007
added
workaround
|
@softhack007 Yeah 2.5.33 seems to compile fine for the TTGO-T-Display usermod . I did not have a display at the moment to test though [ EDIT : compile still fail with 2.5.33] |
|
I'm not sure I am much help here. I haven't compiled this in a while as I haven't had a need, but I just tried with a fresh download and I am having trouble just getting the stock platformio.ini file to not error out on me. "No option 'build_flags_esp32' in section "common". I think some PlatformIO stuff has changed since the last time I tried to use it. |
|
It is fine , seems to NOT compile as listed above , I will be working on re-basing the other usermod from here But in the current TTGO-T-Display the TFT_eSPI version 2.5.33 reference should be in the board environment selected and not |
Makes sense. I think I resolved my platformio.ini file issue - it was due to my platformio_overrides.ini file having an error. I'm a bit confused by the fact that it can't find the WiFi.h library (required in my usermod.cpp file). Has the name of this changed causing this issue? I also can't figure out why there's no section in the platformio.ini for determining a specific board to compile for. My instructions in the readme.md for the usermod direct you to comment out the "default_envs" line (which lists every env), and to uncomment the in the single binaries section: "default_envs = esp32dev" |
|
@softhack007 I mixed up old build info but even using TFT_eSPI version 2.5.33 the compile still fails https://github.com/dosipod/WLED_15/actions/runs/12358075274/job/34487771233
I will edit the post above to indicate that , @spiff72 might be your can still look at fixing that |
|
I"m stumped here - I can't even get WLED to compile "stock" without my usermod. I'm also still not clear whether I am doing the compilation specifically for esp32dev correctly. I tried deleting everything in the default_envs line in platformio.ini except for esp32dev, and it appeared to install a much older version of espressif32 (3.5 instead of the already installed 6.9.0). Clicking the "build" icon at the bottom does nothing, so I tried picking a different env from the bottom status bar in VS Code and picked esp32dev. It then attempts to compile but errors out with some wled_server errors. `Processing esp32dev (board: esp32dev; platform: [email protected]; framework: arduino)Verbose mode can be enabled via
compilation terminated. Environment Status Duration esp32dev FAILED 00:00:28.495
|
|
I got mine to compile (finally). I had some housekeeping to do - including getting npm installed. This might be restating what was already mentioned above, but I had to do the following:
The above allowed me to compile successfully, but I can't confirm the resulting file works because I don't have a TTGO board handy. It may have also been necessary to NOT have powershell terminals open in VS Code when compiling - I swear that was causing me issues too - if I had command prompt "terminals" open it was fine. I also couldn't run the npm install command from powershell terminals - I had to use command prompt. |
|
@spiff72 maybe it's a good time that I get you a bit up-to-date about how to compile WLED - a few things have changed since the last 3 years. It's quite late in Germany where I live, so just a few hints for now. I can give you more info tomorrow.
|
|
Thanks! I will do some more digging in the next few days as I get some more time. It seems that a lot has changed, indeed - libraries have changed, procedures have changed, etc! There was a method to grab the currentMilliamps in there before, but that may have gone away, too. I used this to display the current draw on the T-Display screen as it was running… |
|
@spiff72 We do not actually use this or other usermods but testing just part of 15 confidences compile verification as we have seen few usermods that was not tested on latest and would fail mainly due to libraries .At the moment I do not also have the HW to test functionality so the focus as the title of this post is just compile testing Once you are okay with the current changes please post your github repo with the changes so we or others could PR it but it would be best if a full test with the HW is done prior to PR which is not possible from our side now but I have ordered some and hopefully would be there soon as we have another usermod here https://github.com/Victoare/WLED_TTGO-TDisplay-output we would also like to fix PR |
What happened?
When trying to compile https://github.com/Aircoookie/WLED/tree/main/usermods/TTGO-T-Display [On github] you would get errors
I recall facing the same error with other usermods and it was related to below
Bodmer/TFT_eSPI#3048
Other usermods compile fine on older source
To Reproduce Bug
Uncomment the TFT_eSPI line within the [common] section as mentioned in the usermod readme
Expected Behavior
No compile error
Install Method
Self-Compiled
What version of WLED?
0.15.0 (build 2412100)
Which microcontroller/board are you seeing the problem on?
ESP32
Relevant log/trace output
Anything else?
Take it easy
Code of Conduct
The text was updated successfully, but these errors were encountered: