Ready .bin File Esp32-s3-devkitc-1 (psram)

[pedikexe]

I want to know the connection pins and what screen driver is used there, since I couldn't find it in the repository. File which from bruce installer

[pballada]

The ESP32-S3-DevKitC builds (esp32-s3-devkitc-1 and esp32-s3-devkitc-1-psram) come from the ESP-General target: boards/ESP-General/ESP-General.ini. That's why you couldn't find a screen driver. This build has no display: every TFT pin (TFT_CS, TFT_DC, TFT_RST, TFT_MOSI, TFT_SCLK, TFT_BL) is -1, and interface.cpp sets bruceConfig.startupApp = "WebUI". The board boots into the WebUI, and you control it from a phone or PC over Wi-Fi. The -psram variant is the same build plus BOARD_HAS_PSRAM and OPI memory, for the N16R8 modules.

Default pins in that build:

Function	GPIO
CC1101 (SPI)	SCK 12, MOSI 11, MISO 13, CS 10, GDO0 9 (GDO2 14 optional, commented out)
Shared SPI bus (NRF24 / W5500 use it too)	SCK 12, MOSI 11, MISO 13, SS 10
IR TX / RF TX ("Grove SDA")	8
IR RX / RF RX ("Grove SCL")	46
TX LED	40 (active high)
SD card	not configured (-1)
Buttons	not configured (SEL_BTN/UP_BTN/DW_BTN are commented out)

The NRF24 lines are in the file but commented out (CE 6, CSN 7 on the same SPI bus). FM_RSTPIN is 12, for the optional Si4713.

If you want a screen, SD card or buttons, build from source: set the TFT_* and SDCARD_* pins and -DSEL_BTN/-DUP_BTN/-DDW_BTN in that .ini, and choose the driver in the TFT_eSPI setup flags. Another option is to start from one of the S3 boards that already has a display, such as ES3C28P or elecrow_advance_s3, and copy its display section.

[nadeem9986]

That build has no screen driver and no display pins - every TFT pin is -1 in the config, it runs headless over WebUI/serial/USB. To use a screen you must edit boards/ESP-General/ESP-General.ini with a driver flag and your TFT pins, then compile yourself in PlatformIO. Pins it does use: RGB 48, UART 43/44, I2C 8/9, SPI 12/11/13/10, CC1101 CS10 GDO0 9, IR/433 TX8 RX46.

[nadeem9986]

That build has no screen driver and no display pins at all. The plain DevKitC has no screen, so the ready-made .bin doesn't wire one up. The installer .bin for this board is the esp32-s3-devkitc-1 env (or esp32-s3-devkitc-1-psram if you picked the PSRAM/N16R8 one), defined in boards/ESP-General/ESP-General.ini. In that env every display pin is set to -1: TFT_CS, TFT_DC, TFT_RST, TFT_MOSI, TFT_SCLK, TFT_BL, TOUCH_CS and BACKLIGHT are all -1, and the SD card pins are -1 too. There is also no driver define. For comparison, the CYD board envs set something like -DILI9341_2_DRIVER=1 or -DST7796_DRIVER=1 plus real TFT pin numbers. ESP-General has none of that, so this build is meant to run headless - you control it from the WebUI over WiFi or from serial, and the USB port works as HID.

The pins this build actually uses:

• RGB LED: GPIO 48
• UART: TX 43, RX 44
• I2C (Arduino default): SDA 8, SCL 9
• SPI bus: SCK 12, MOSI 11, MISO 13, SS 10
• CC1101 module: CS 10, GDO0 9, SCK 12, MOSI 11, MISO 13
• IR and 433MHz one-pin modules: TX on GPIO 8, RX on GPIO 46 by default (you can switch between these in the menu)

If you want a screen on a DevKitC you have to build the firmware yourself: clone the repo, edit boards/ESP-General/ESP-General.ini, add a driver flag like the CYD envs use and set the TFT_* pins to whatever you wired, then build with PlatformIO. The wiki wiring diagrams won't help here either - the only ESP32-S3 diagram there is for the DIY Smoochiee board, a custom PCB with its own display wiring.