ESP32 I2C takes wrong pins

Libraries
1

So i want to use I2C with my WT32-SC01 Plus. When i use the Wire.begin(SDA_PIN,SCL_PIN, freq); it just always uses IO10 as SCL and any other as SDA, didn’t figure out which one yet. Since i need it on IO10 for SCL and IO11 for SDA i need to be able to adjust the pins.
My platformio.ini looks like this:

[env:WT32-SC01-PLUS]
platform = espressif32
board = um_tinys3
framework = arduino
upload_speed = 921600
monitor_speed = 115200
; upload_port = COM7
board_build.partitions = max_app_8MB.csv
;board_build.partitions = no_ota.csv
build_flags = 
	-DARDUINO_USB_CDC_ON_BOOT
	-DLV_CONF_INCLUDE_SIMPLE
	-DLV_COMP_CONF_INCLUDE_SIMPLE
	-DLV_LVGL_H_INCLUDE_SIMPLE
	-DBOARD_HAS_PSRAM
	;-DDEBUG_TOUCH
	-mfix-esp32-psram-cache-issue
	-I src/ui/
	-I src/
lib_deps = 
	SPI
	lovyan03/LovyanGFX@^0.4.18
	lvgl/lvgl@^8.3.2
	TCA9534
	Wire
	DS3231
	EspSoftwareSerial
	mengguang/atsha204_i2c@^1.0.1

Has anyone experienced such a problem before/can anyone help?

2

Have you tried an absolute minimal project and code like the I2C Scanner with only the Wire.begin() call adapted to your Wire.begin(SDA_PIN,SCL_PIN, freq); and see if it can find any devices? The needed platformio.ini should just be

[env:WT32-SC01-PLUS]
platform = espressif32
board = um_tinys3
framework = arduino
3

Yes i tried it once, it worked fine and did again just now.

4

Then the conclusion is that the base code works just fine but something messes it up in your more complex project. Maybe another Wire.begin() with different arguments. Without seeing the code, or using a debug probe, that’s impossible to say.

5

Ohh that brings me to the idea that my lvgl part with the touchscreen library could use I2C too… Thanks!