mythbuster5
commented
1 week ago No it shouldn't be this case It looks that i2c_isr_receive_handler function tries to write some data to user read/write buffer (data member of i2c_operation_t) which is not assigned to i2c operation of type I2C_LL_CMD_STOP, but I could be wrong. Umm, could you please try that in the latest master, setting .scl_wait_us = 0, with larger value like 20*1000, and see if there is anything wrong.
Secondly, what about slowing down scl frequency
As for QMC5883 is the exclusive sensor that causes this error, interesting and I'm going to got one for further debugging.
Andrew-Exeter
Answers checklist.
IDF version.
v5.2.2-639-g43098fc4de, v5.3-383-g0bbd728196, v5.4-dev-2596-g6e5414b6c4
Espressif SoC revision.
ESP32-D0WDQ6 (revision v1.0)
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
NodeMCU-ESP32 ESP32 DEVKITV1
Power Supply used.
USB
What is the expected behavior?
i2c_master_transmit_receivefunction should return error code on i2c transaction failure.What is the actual behavior?
StoreProhibitedexception is thrown by accessing to null ptr in functioni2c_ll_read_rxfifo.Steps to reproduce.
main/main.candmain/CMakeLists.txtfiles.void app_main(void) { i2c_master_bus_config_t i2c_mst_config = { .i2c_port = I2C_NUM_1, .sda_io_num = GPIO_NUM_19, .scl_io_num = GPIO_NUM_18, .clk_source = I2C_CLK_SRC_DEFAULT, .glitch_ignore_cnt = 7, .intr_priority = 0, .trans_queue_depth = 0, .flags = { .enable_internal_pullup = true, } };
i2c_master_bus_handle_t bus = NULL; if (i2c_new_master_bus(&i2c_mst_config, &bus) == ESP_OK) { printf("bus installed\n");
}
while (true) { vTaskDelay(1000/portTICK_PERIOD_MS); } }
idf_component_register(SRCS "main.c" INCLUDE_DIRS "." PRIV_REQUIRES driver)
More Information.
My project crashed time by time and always with same exception/backtrace. To exclude posibilities that problem is related to other project specific code or configuration I created new project as described in "Steps to reproduce" section, but with same behavior. Clean installations of esp-idf and tools didn't help. (I tried versions v5.2, v5.3, master) I tried
/examples/peripherals/i2c/i2c_toolsexample too. During i2c device register reading ("i2cget" command) occurs exactly same exception.This problem araised mostly (almost exclusively) with QMC5883 sensor in comparison to other i2c devices.
It looks that
i2c_isr_receive_handlerfunction tries to write some data to user read/write buffer (datamember ofi2c_operation_t) which is not assigned to i2c operation of typeI2C_LL_CMD_STOP, but I could be wrong.I am attaching backtrace, states of lacal variables and states of same other i2c driver related objects acquired using GDB debugger:
gdb-backtrace.txt gdb-i2c_master_bus_t-related.txt gdb-locals.txt