ESP32 Microcontroller Hardware and Software

[@homelessrobot]

there is now also an llvm fork that supports xtensa. I think a lot of it has been upstreamed, its just not enabled by default so most binary distributions don't have it enabled.

[@beautifulsmall]

Great explanation of the features, thank you. Fantastic chip. Just started with IDF, I2S camera example ? The examples I've tried in eclipse compile ok ( python path had to be added to file in profile.d) But generally it was a very smooth toolchain setup, thanks to the very clear setup guide. More videos would be great explaining how the rtos interacts for those of us that have come from bare metal.

[@triularity]

@12:55 - "The plan is to only leave the low level wi-fi and bluetooth connectivity, which is chip specific, and proprietary, in binary" Is this another gaping security hole waiting to happen, like the recent BroadPwn and BlueBorne vulnerabilities, due to everyone being forced to use and trust "magical" proprietary firmware blobs?

[@yekutielbenheshel354]

I read your insightful comment and hope someone will properly address this issue in this comment section. But I am not holding my breath. I am not well-versed in this subject matter. Therefore my thoughts below might be incorrect. However, it seems that the inherent conflict of interest that is set in place when a hardware vendor puts proprietary code on their hardware can best be solved by separating hardware sales from software sales. This remind me of the Chinese wall Wall Street firms legally yet typically only purportedly to set up to prevent the illegal "leakage" of corporate inside information. In other words, if hardware vendors were to only sell hardware, then this problem could likely be solved with free and open source software. But frankly I suppose this comes down to, "Trust the hardware vendor to be vigilant about properly maintaining and updating security" This seems like a sure fire recipe for hackers finding and exploiting security vulnerabilities. I would be glad for others who know more about this than I am to comment about this important issue. At this point my sense is the real message might be something like: "Go develop exciting and useful IoT applications with the wonderful new ESP32... and then just wait until some evil hacker wreaks havoc with the hardware your ESP32 is controlling."

[@phizicks]

Yay krackattacks.com to name a new one.

[@coffeedev1992]

I have a question to ask you how can I adapt the ESP32 to create traffic lights and want to make it performed automatically and controlled by the App inventor or another app (it's required at least 16 output) big thanks in advance sir :)