Replies: 2 comments
-
With a "local install" one can circumvent this by:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't see why esphome can't just include the esphome:
platformio_options:
board: myboard
esp32:
board: esp32dev Maybe a PR would be good. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The problem to solve
I stubled accross the problem, that there are many different ESP32-Modules available, but some combinations do not lead to an already defined board. In my application, I used some ESP32-WROOM-32D with 8MB flash and 520 KB of RAM, which could be easily added as a new board to PlatformIO itself, but adding it to the PlatformIO within ESPhome is not possible.
Why it is not possible/easy for ESPhome users?
At first, the board JSON (in my example for ESP32) usually lies within the
<ADDON_CONTAINER_HOME>/cache/platformio/platforms/espressif32/boards
, which (I believe) gets overwritten with every ESPhome update.Secondly, each board is also listed within the
esphome/components/esp32/boards.py
Python file and this can not be custom-changed.Suggestion
My suggestion would be, to introduce a folder structure e.g. for ESP32. It could be config/esphome/.custom_boards/esp32/ where all your custom JSON board config files can go. When starting to build (installing the node), the board is added to the BOARDS-Array for ESP32 and the custom board file is copied over to the boards-cache dir.
This would also render the (little bit dirty and inclomplete) platformio_options variable in core config useless.
Beta Was this translation helpful? Give feedback.
All reactions