ESP8266 Community Forum

- Tue Aug 25, 2015 7:11 pm #27044 Hi,
I think I have found a bug with the SPI interface.
I am using a 256x64 OLED display and have double buffering. That means I have to send 8k across the SPI.
I have attached a sample Arduino script that shows the problem I am having. I have stripped down the script to the bare essentials and you do not even need to attach an OLED/SPI device to show the problem.

Please can someone download the script and try it. If you comment out the delay(0) it resets the ESP8266. If uncomment the delay(0) it does not reset and continues to send data.

arduino_script.txt

Thanks
Mark

You do not have the required permissions to view the files attached to this post.

- Tue Aug 25, 2015 7:40 pm #27047 Your techniques to communicate with the OLED seems to be a bit weird ...
Maybe you should mentioned which OLED module it is, is it a SSD1322 ?
Did you try some libraries such as https://github.com/MartyMacGyver/OLED_SSD1322 ?

- Wed Aug 26, 2015 7:04 am #27084 in general, if a dubious reset can be solved by inserting a delay, it is most likely a wd reset.
So: yes, there are issues with the wd beeing blocked for too long on the esp8266.

- Wed Aug 26, 2015 8:32 am #27087 schufti,
You know....I woke the middle of the night wondering if there is a watchdog on the ESP8266 that causes a reset if you end up in a tight processing loop. Isn't the brain wierd.
That could be the issue not the SPI code.
Will investigate that some more.

Thanks
Mark