start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
start [2024/03/20 01:27] sausage |
start [2024/04/04 02:12] (current) sausage |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== ESP32-S2 and the APA102 RGB LED ====== | ||
| + | [[feathers2_apa102|{{:esp32s2:feathers2.jpg?direct&300 |}}]] | ||
| + | |||
| + | I recently picked up an ESP32-S2 based board that features an APA102 RGB LED which is a serial device with data and clock pins. | ||
| + | |||
| + | Working with this LED device seemed tricky at first, but thankfully a good datasheet made everything pretty clear. | ||
| + | |||
| + | [[feathers2_apa102|Read Article]] | ||
| + | |||
| ====== ESP32 OTA and Rollbacks - What happens under the hood? ====== | ====== ESP32 OTA and Rollbacks - What happens under the hood? ====== | ||
| Line 5: | Line 14: | ||
| Over The Air (OTA) provides a way to send firmware to your ESP32 board in the field without the need for a cable and physical access to the device. | Over The Air (OTA) provides a way to send firmware to your ESP32 board in the field without the need for a cable and physical access to the device. | ||
| - | The purpose of this article is manually step through the various stages of the OTA process and illustrate the state of the ESP32 at each stage. | + | The purpose of this article is to manually step through the various stages of the OTA process and illustrate the state of the ESP32 at each stage. |
| [[esp32_ota|Read Article]] | [[esp32_ota|Read Article]] | ||
| Line 37: | Line 46: | ||
| [[gs_2000_home_theatre_modification|Read Article]] | [[gs_2000_home_theatre_modification|Read Article]] | ||
| + | |||
| + | ---- | ||
| ====== Deploying an open, insecure .NET Core WebAPI to a Plesk host ====== | ====== Deploying an open, insecure .NET Core WebAPI to a Plesk host ====== | ||
start.1710898069.txt.gz ยท Last modified: 2024/03/20 01:27 by sausage
Page Tools
