new buildenv for esp32s3dev_16MB_PSRAM_opi dev board (LilyGo T7-S3)

[raymondhardy]

Adds new esp32s3dev_16MB_PSRAM_opi dev board to work with Lily Go T7_s3 ESP32-S3-WROOM-1-N16R8

[blazoncek]

@raymondhardy thank you for the environment. However I do have some concerns.

@softhack007 & @Aircoookie I am not happy with the growth of platformio.ini file and inclusion of every possible dev board with different RAM/flash configuration there is.
I propose we move all but those included in release cycle into platformio_override.ini.sample. That way each and every person can have only their environments included without cluttering global platformio.ini.

[softhack007]

@blazoncek You're right, I think we need a new concept for al these "slightly different" boards. Especially with -S3/-S2/-C3 support added (and -C6 might join next year), collecting all possible buildenvs in platformio.ini is very hard to maintain.

In the special case of this PR, the extends keyword could be used to make the real differences more obvious:

[env:esp32s3dev_16MB_PSRAM_opi]
extends = env:esp32s3dev_8MB_PSRAM_opi
board_build.partitions = tools/WLED_ESP32_16MB.csv
board_upload.flash_size = 16MB

Not sure what to do in the general case though ... its clear we cannot go on collecting buildenvs directly in platformio.ini. The good old times when esp32 4MB was all that matters are in the past - the future is more variants (classic, -S3, -S2, -C3, ...), more flash sizes (2MB, 4MB, 8MB, 16MB, ...) and more access modes (dio, qio, qio_qspi, qio_opi, opi_opi, ...) that are not compatible with each other.

Maybe platformio.ini should only provide the basic configs and consider major differences (like major chip/CPU variants, PSRAM, USB_CDC or HW Serial, different platform versions). Then specific boards would be added in another file.

See also:

• User Boards Config Database or platformio_userboards.ini #2953

[softhack007]

see details below.

In general, a maintainer decision is needed (as stated by @blazoncek) on how to collect board buildenvs in general. This clarification seems necessary before any approval can be made.

[raymondhardy]

ecision is needed (as stated by @blazoncek) on how to collect board buildenvs in general. This clarification seems necessary before any approval can be made.

Sounds good. Just wanted to state that i did a new build with these changes and it works for the board! (I tested it with another board i had without any code on it)