-
Notifications
You must be signed in to change notification settings - Fork 9
Troubleshooting
Szybet edited this page Oct 2, 2024
·
15 revisions
- If you try compiling on windows and you uncounter problems like "file not found" execute this in the terminal inside of the container:
find . -type f -exec dos2unix {} \;
(maybe you will need to install this command viasudo apt-get install dos2unix
) - Similar, if you encounter the problem "permissions not found" or smth like that, try this:
find . -type f -name "*.sh" -exec chmod +x {} \;
- Have you installed docker desktop at some point? If
docker context ls
shows 2 entries, something is wrong, executingdocker context use default
may fix it. - Credentials / login problem fix: https://stackoverflow.com/questions/65896681/exec-docker-credential-desktop-exe-executable-file-not-found-in-path
- For errors related to network, virtual interfaces, because you probably messed up your network setup, look here: https://stackoverflow.com/a/40524603/22437723
- Set your dns to 1.1.1.1
- If you moved from one firmware to mine, consider erasing the flash fully first
- If your firmware crashed, try retrieving the coredump. I have a tool for that in
resources/tools/other/tasks/taskerEsp.sh
- If you want to catch odd behavior, try to replicate it with logs enabled. Enable DEBUG option and PUT_LOGS_TO_SERIAL, PUT_LOGS_TO_FS to your will. you can retrieve logs from littlefs using the resource task.
- With DEBUG on, Some options optimised for speed and only PUT_LOGS_TO_FS on you can achieve good performance while still getting logs for later, if the issue is hard to catch
- Somehow imagemagick is too old. That's weird, Contact me.
- Your littlefs filesystem is corrupted / not uploaded / failed to mount. What have you done?... Follow the wiki again, you probably skipped one step, or look at the logs when generating resources.
(Grey color, kind of)
You are very unlucky, well anyway uncomment It's turned on at default now, try to disable it then? This is an experimental fix, while I tested it many times, still, as this whole firmware, do it for your own risk-D SCREEN_PARTIAL_GREY_WORKAROUND=1
in platformio.ini
.