Espressif, WHY?!
-
Okay let me start by saying how much I love the ESP32. It's a 32-bit dual core SoC with wifi and bluetooth for less than $10, what's not to love? But... Espressif, come on. You made a great piece of hardware, and I want to unlock all of its fancy features. I ditched the Arduino framework and started coding directly against the ESP-IDF (the dev framework Espressif made specifically for the ESP32) All is good, woo! I have access to the full STL, to filesystem mount points, to the humble printf() - all the things I couldn't get under Arduino. Except... The SPI bus drivers for the ESP-IDF seem to be absolute *garbage*. I've written ESP32 based drivers for an ILI9341 display adapter for both ESP-IDF and the Arduino framework, and the Arduino one runs at 40MHz and I can only top the other one out at 26MHz! Furthermore, with the ESP32 SPI drivers there seem to be timing issues. Until my good logic analyzer gets here I can't know for sure, but it looks like the SCLK line is lagging behind the data lines by half a tick. For this or some other reason I cannot get the ESP-IDF to talk to e-paper/e-ink displays at all. Why go through all this effort to make a framework for your hardware, and then botch the SPI implementation for it, all the while making a *good* implementation of it for someone else's (Arduino) framework?! What the heck am I missing? *headdesk*
Real programmers use butterflies
It is Saturday, you know.
-
It is Saturday, you know.
This is what I do to myself on Saturdays.
Real programmers use butterflies
-
This is what I do to myself on Saturdays.
Real programmers use butterflies
-
No cartoons? Horse Opera?
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
Violent Femmes - Waiting For the Bus - YouTube[^] I needed an excuse to listen to the violent femmes. Waiting for the SPI bus seems as good a reason as any.
Real programmers use butterflies
-
Okay let me start by saying how much I love the ESP32. It's a 32-bit dual core SoC with wifi and bluetooth for less than $10, what's not to love? But... Espressif, come on. You made a great piece of hardware, and I want to unlock all of its fancy features. I ditched the Arduino framework and started coding directly against the ESP-IDF (the dev framework Espressif made specifically for the ESP32) All is good, woo! I have access to the full STL, to filesystem mount points, to the humble printf() - all the things I couldn't get under Arduino. Except... The SPI bus drivers for the ESP-IDF seem to be absolute *garbage*. I've written ESP32 based drivers for an ILI9341 display adapter for both ESP-IDF and the Arduino framework, and the Arduino one runs at 40MHz and I can only top the other one out at 26MHz! Furthermore, with the ESP32 SPI drivers there seem to be timing issues. Until my good logic analyzer gets here I can't know for sure, but it looks like the SCLK line is lagging behind the data lines by half a tick. For this or some other reason I cannot get the ESP-IDF to talk to e-paper/e-ink displays at all. Why go through all this effort to make a framework for your hardware, and then botch the SPI implementation for it, all the while making a *good* implementation of it for someone else's (Arduino) framework?! What the heck am I missing? *headdesk*
Real programmers use butterflies
honey the codewitch wrote:
What the heck am I missing?
By the sound, chocolotate.. ..ice cream :) runs for cover
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Okay let me start by saying how much I love the ESP32. It's a 32-bit dual core SoC with wifi and bluetooth for less than $10, what's not to love? But... Espressif, come on. You made a great piece of hardware, and I want to unlock all of its fancy features. I ditched the Arduino framework and started coding directly against the ESP-IDF (the dev framework Espressif made specifically for the ESP32) All is good, woo! I have access to the full STL, to filesystem mount points, to the humble printf() - all the things I couldn't get under Arduino. Except... The SPI bus drivers for the ESP-IDF seem to be absolute *garbage*. I've written ESP32 based drivers for an ILI9341 display adapter for both ESP-IDF and the Arduino framework, and the Arduino one runs at 40MHz and I can only top the other one out at 26MHz! Furthermore, with the ESP32 SPI drivers there seem to be timing issues. Until my good logic analyzer gets here I can't know for sure, but it looks like the SCLK line is lagging behind the data lines by half a tick. For this or some other reason I cannot get the ESP-IDF to talk to e-paper/e-ink displays at all. Why go through all this effort to make a framework for your hardware, and then botch the SPI implementation for it, all the while making a *good* implementation of it for someone else's (Arduino) framework?! What the heck am I missing? *headdesk*
Real programmers use butterflies
That's a bit bizarre - mind you, I see a lot of iOT work at the moment and I shudder when they use a serial port GPS integration rather than I2C or SPI. I'll be learning 'ROS' soon, I missed a really nice job in Ag-Tech here because I wasn't prepared to lie on my CV - that being said, yes, it's not an O/S, and I do know messaging, so I could have bluffed my way through mqtt etc Pretty cool that you write drivers for ESP32 - a level way above me
-
Okay let me start by saying how much I love the ESP32. It's a 32-bit dual core SoC with wifi and bluetooth for less than $10, what's not to love? But... Espressif, come on. You made a great piece of hardware, and I want to unlock all of its fancy features. I ditched the Arduino framework and started coding directly against the ESP-IDF (the dev framework Espressif made specifically for the ESP32) All is good, woo! I have access to the full STL, to filesystem mount points, to the humble printf() - all the things I couldn't get under Arduino. Except... The SPI bus drivers for the ESP-IDF seem to be absolute *garbage*. I've written ESP32 based drivers for an ILI9341 display adapter for both ESP-IDF and the Arduino framework, and the Arduino one runs at 40MHz and I can only top the other one out at 26MHz! Furthermore, with the ESP32 SPI drivers there seem to be timing issues. Until my good logic analyzer gets here I can't know for sure, but it looks like the SCLK line is lagging behind the data lines by half a tick. For this or some other reason I cannot get the ESP-IDF to talk to e-paper/e-ink displays at all. Why go through all this effort to make a framework for your hardware, and then botch the SPI implementation for it, all the while making a *good* implementation of it for someone else's (Arduino) framework?! What the heck am I missing? *headdesk*
Real programmers use butterflies
Quote:
botch the SPI implementation for it, all the while making a *good* implementation of it for someone else's (Arduino) framework?!
Maybe they found, along the way of completing their own framewwork, that Arduino one imperat (attracts many more people)?
"In testa che avete, Signor di Ceprano?" -- Rigoletto
-
Quote:
botch the SPI implementation for it, all the while making a *good* implementation of it for someone else's (Arduino) framework?!
Maybe they found, along the way of completing their own framewwork, that Arduino one imperat (attracts many more people)?
"In testa che avete, Signor di Ceprano?" -- Rigoletto
That's not it or they wouldn't still be maintaining the ESP-IDF.
Real programmers use butterflies
-
That's not it or they wouldn't still be maintaining the ESP-IDF.
Real programmers use butterflies
-
Violent Femmes - Waiting For the Bus - YouTube[^] I needed an excuse to listen to the violent femmes. Waiting for the SPI bus seems as good a reason as any.
Real programmers use butterflies
