eren-terzioglu

Hi @metarutaiga, Thanks for the details. We will look into that.

Hi, We will look into that, thanks for reporting

Hi, Could you send the example code from spi slave driver side?

> Hello @eren-terzioglu > > below you can see an example: > > ``` > #include > #include > #include > #include > #include > #include > #include > >...

Hi @FelipeMdeO , I checked the issue and seems it is some kind of feature. Code flow works like that: - Master devices creates an interrupt and [`spislave_periph_interrupt`](https://github.com/apache/nuttx/blob/master/arch/risc-v/src/common/espressif/esp_spi_slave.c#L599) funtion handles...

> @eren-terzioglu and @tmedicci, Did you understand the issue? Are you able to reproduce it? Yes I reproduced and working on it. Thanks for the report

Hi @FelipeMdeO [Behavior seems explained in idf documentation](https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/peripherals/spi_slave.html#spi-transactions:~:text=Every%20clock%20pulse%2C%20a%20data%20bit%20is%20shifted%20from%20the%20Host%20to%20the%20Device%20on%20the%20MOSI%20line%20and%20back%20on%20the%20MISO%20line%20at%20the%20same%20time). So this is sort of expected behaviour of SPI Slave driver for esp devices. You can get over it with filling TX...

Hi, Seems you are not using newest version of NuttX. I have couple of suggestions and questions: - Please give information about which config you are using - Please share...

Hi, Thanks for the bug report. Could give some information about your setup? For example - NuttX version that running on device - Defconfig that is being used - Doesn't...

Seems it is pretty close to IDF implementation, please create a PR and we can test feature more.