ESP32 logging falls into the same category as the recent post about embedding binary content. It is about how logging on ESP32 is different from logging on ESP8266. Yet, as “logging” is a software topic (mostly) and “ESP32” describes hardware we need to be more precise with terms. Therefore, this post will look into how logging with the Espressif ESP-IDF has improved over plain NONOS SDK. The same goes for Arduino Core for ESP32.
Rest assured the old stuff still works on ESP-IDF. However, this post hopefully manages to convince you to improve your code by using the new features.
The ESP32 has a lot more internal RAM than the ESP8266 had. But it can use even more by addressing up to 4MB of external SPI RAM memory. In this blog post we will show you how to use the PSRAM in your projects.
There is a reason the title of this post specifically says “Embed Binary Data on ESP32“. This suggests that it is different than embedding binary data on let’s say ESP8266. Yes indeed, that’s part of the story. The other is that to embed binary data on ESP32 you don’t need to jump through hoops anymore like on ESP8266. Instead, you will do what likely feels most natural: store the binary data in a file in the project directory and have the compiler slurp it from there. Easy as pie!
In the last few years all big IT companies have discovered the Internet-of-Things field in one way or the other. Apple and Google have offerings for home automation, Google, Amazon and Microsoft offer services to connect IoT devices to the cloud. For one of our projects we wanted to take a look at Microsofts Azure IoT Hub solution. Microsoft offers comprehensive libraries to connect the ESP8266 to the Azure cloud. But what about the ESP32? In this post we’ll describe how to create a shared access token for the Azure cloud. We’ll further cover how to use this token to send a minimalistic request with the ESP32 to the Azure IoT hub.