mirror of
https://github.com/OpenEPaperLink/OpenEPaperLink.git
synced 2026-03-21 00:04:28 +01:00
[GH-ISSUE #65] Feature request: OTA with own, custom .bin #2791
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bartbh on GitHub (Jun 15, 2023).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/65
Is it possible to upload a custom firmware (with different pinout) to the esp32 flasher via OTA? Either by uploading it directly or via url.
The current update feature works very well, but only when using the pre-defined pinout. Or maybe storing the pin layout in a different location so it doesn't get overwritten?
@nlimper commented on GitHub (Jun 15, 2023):
Just for my information, what’s your reason for using a different pinout? We have precompiled environments for esp32, esp32-s2 and esp32-s3. Does your hardware differ from those?
@jjwbruijn commented on GitHub (Jun 15, 2023):
The pinout is fixed, or baked in to the code, at compile time. Making it flexible would require a lot of extra clock cycles for every pin change, so that's not a great idea. Building an extra OTA method will costs extra space, which we don't have a lot of.
As @nlimper stated, there already are a bunch of supported environments, I would kindly suggest to change your pin mapping to match one of the existing environments and go from there, or make your own version with custom URL OTA support
@jonasniesner commented on GitHub (Jun 16, 2023):
If you think there is a valid reason to use a different pinout, you can create a PIO config for it and it can be included in the CI/CD pipeline
@bartbh commented on GitHub (Jun 21, 2023):
Currently I'm using a breadboard to connect the esp32-s2 with a tag. So only the outer pins are availble for me to use.
I'll look into making my own version with custom pinout and ota url.