Setting SPI_CLKCNT_H too high in SPI_CLOCK_REG register makes in some cases (probably depending on SPI_CLKCNT_N) stop SPI working. This is not documented.

You don't seem to understand the core of this issue but that is OK, I just wanted to illustrate that even Espressif FreeRTOS implementation is not correct (in fact I am quite curious where the issue excatly is). I looked a little into your link and you code. I notice that in your UDP example is bind...

I have prototyped many things with it over this time, using uSD, SPI (peripherals and 5" TFT LCD's) & I2C extensively. Even adding Ethernet capability to it. I have not run into one issue with it. Then you are really a lucky man. While writing my own driver for SPI I have found several issues in ES...

Have you considered the possibility that the problem is at your side? Sure, I have. But then I looked at other manufacturers solution and I can clearly say that the problem is not only me. There are certainly bugs in esp-idf (as in any software), but from your posting one could conclude that it is ...

I think the ESP32 was the labrat or testbech for Espressif, to test FreeRTOS, dual cores, and external RAM, as well as new preripherals. There is a funny/ironic analogy between Espressif products and Windows versios: 8266 -> Windows 7: This actually worked, and kind of still used in many many place...

Again and again... Not only that your hardware is badly designed. You don't even know how to test it and how to write drivers for it. (And your docs are incomplete too) 2 years on the market and your SPI drivers are still not working. 2 years on the market and you still don't know about all HW issue...

https://github.com/espressif/esp-idf/blob/960c240578d359a1c5cf8cb3cbd9ce3150d5a370/components/driver/spi_common.c#L382-L438 this is not documented And what does this mean? https://github.com/espressif/esp-idf/blob/960c240578d359a1c5cf8cb3cbd9ce3150d5a370/components/driver/spi_master.c#L843-L846 Is ...

michprev wrote: ↑

Sat Oct 20, 2018 11:33 am

• [SPI] CS setup time does not work in full duplex

I don't think you realise how huge problem this is. Full-duplex is the most common setup and most SPI peripherals require CS active several clocks before the data transfer.

AFAIK there is also bug in WP settings (https://github.com/espressif/esp-idf/bl ... ruct.h#L56) both with user commands and SPI flash commands.

• SPI flash options in SPI registers are not documented (e. g. SPI_FLASH_READ, SPI_FLASH_WREN in SPI_CMD_REG register)

bump SPI flash commands