a2nr
/
velxio
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat(espidf): fijar CONFIG_ARDUINO_VARIANT en la plantilla de sdkconfig 

Sin esta linea la variante se queda en el nombre del chip, asi que TODA placa
compila como dev-kit generico y variants/<VARIANTE>/pins_arduino.h nunca entra
en el include path: los nombres propios de la placa (D0..D10 en una XIAO, la
serigrafia de las M5) sencillamente no existen. Justo los sketches que la gente
copia de la wiki del fabricante.

El helper que deriva la variante del FQBN leyendo boards.txt ya estaba; faltaba
la plantilla que la consume. Sigue pendiente rellenar 'arduinoVariant' en
normalized para que surta efecto (ver F7.6 en velxio-prod).
This commit is contained in:
David Montero Crespo 2026-07-27 16:36:00 +02:00
parent 119aa5982e
commit f318b06116
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
backend/app/services/esp-idf-template/sdkconfig.defaults.in
View File

@ -63,6 +63,14 @@ CONFIG_AUTOSTART_ARDUINO=n
# Which core Arduino's setup/loop and event task run on. Both default to
# core 1 (matches Arduino IDE) but the user can pin them independently.
# Which board variant Arduino builds against. This is what puts
# variants/<VARIANT>/pins_arduino.h on the include path, and therefore what
# makes the board's own pin names (D0..D10 on a XIAO, the M5 silk names, ...)
# exist at all. Left at its default it is just the chip name, so every board
# compiles as a generic dev-kit and any sketch copied from a vendor's wiki
# fails on its very first pin macro.
CONFIG_ARDUINO_VARIANT="${ARDUINO_VARIANT}"
CONFIG_ARDUINO_RUNNING_CORE=${ARDUINO_RUNNING_CORE}
CONFIG_ARDUINO_EVENT_RUNNING_CORE=${ARDUINO_EVENT_RUNNING_CORE}