The Wire library seems to have some significant overhead in its drivers, looking at places like here and more importantly the I2C write functions and sub-calls like this, so 62 microseconds overhead between I2C transmissions doesn’t seem that absurd…Įven tClock(1000000) ( docs) won’t help much if the inter-write times are so big. I thought that this could be an issue that could be caused by task switching from FreeRTOS (I’m running this code on the Setup function) but lowering the freertos scheduler frequency didnt help. Is this an inherent problem with the Wire library? Should I use the original ESP I2C library? I’ve hooked up my scope and captured some screenshots to made it easier to show what’s happening:
I2CWriteByte(addr, i2cAddrbuffer, i2cCMDbuffer) I2cAddrbuffer = IS31F元741addrmap Īnd then sending the data over to the I2C bus using the wire library: for(int i = 0 i I’m interfacing an LED matrix using a matrix driver that communicates over I2C. I’ve been building a project using PlatformIO and the ESP32 on a custom board.
0 kommentar(er)
