You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using u8g2_esp32_hal to interface with an I2C OLED device, and whenever the OLED screen is not connected the program aborts, causing a restart. The reason this happens is because ESP_ERROR_CHECK macros are used in several places, which simply abort the thread if they fail. I'm wondering if instead of using ESP_ERROR_CHECK, the relevant functions could print a message and return an error code that users could handle themselves.
Alternatively, maybe provide a function that can test the I2C connection without aborting?
This line is the one that generally causes the abort for me:
I'm using u8g2_esp32_hal to interface with an I2C OLED device, and whenever the OLED screen is not connected the program aborts, causing a restart. The reason this happens is because ESP_ERROR_CHECK macros are used in several places, which simply abort the thread if they fail. I'm wondering if instead of using ESP_ERROR_CHECK, the relevant functions could print a message and return an error code that users could handle themselves.
Alternatively, maybe provide a function that can test the I2C connection without aborting?
This line is the one that generally causes the abort for me:
esp32-snippets/hardware/displays/U8G2/u8g2_esp32_hal.c
Line 159 in fe3d318
The text was updated successfully, but these errors were encountered: