platform-espressif32 issues

esp32-s2-saola-1 ESP-Prog debugging issue

1

Hi - I’m new to ESP32 and PlatformIO. I am using the ESP-Prog and haven’t been able to get debugging to work correctly. This is my platformio.ini file: ``` [env:esp32-s2-saola-1]...

websterelec

help wanted

ESP-IDF

After upgrading PlatformIO: cannot compile [email protected]

1

After auto-update of PlatformIO it is not possible to use [email protected]: platformio.ini [platformio] ; select application src_dir = testREV6/wiFiSniffer lib_dir = src [env:pico32] platform = [email protected] board = pico32 framework...

trichl

help wanted

ESP-IDF

PlatformIO/platform-espressif32 running on RaspberryPi0W - (Raspbian 11 Lite ARMv6 / arch: v6l / Linux-v6l)

1

Hi! I’m getting ready to join into development of Fujinet, which is a WiFi modem (+ some other stuff) for retro computers - mostly Atari 8bit. Inside Fujinet device we...

peterkaczorowski

help wanted

ESP-IDF

examples/espidf-arduino-blink build fails: unknown type name '_lock_t'

8

I followed the directions in platform-espressif32/examples/espidf-arduino-blink/README.md exactly, but the build failed with ````error: unknown type name '_lock_t'```` in lots of places. Instead of using the zip file I also tired...

skiphansen

help wanted

Arduino

ESP-IDF

Espressif 32 2.1.0 broke after reinstalling python

4

Hi, I have been using Espressif 32 2.1.0 on VSCODE IDE for a long time wihtout any problem. I was having some trouble with python at flashing ESP32 devices outside...

jrHernandezSio

help wanted

ESP-IDF

ESP32 Crash Report is not properly formatted

6

Environment Development Kit: LoLin D32 PRO / ESP32-CAM and more Kit version NA Module or chip used: [ESP32-WROOM-32] PLATFORM: Espressif 32 (3.3.1+sha.33ff413) WEMOS LOLIN D32 PRO IDF version (run git...

MartinMueller2003

bug

Use gcc-ar and gcc-ranlib

10

In order to use link time optimizations (lto) `ar` and `ranlib` need to have the lto plugin supplied. This is achieved easiest by using the `gcc-*` equivalents. More info: https://embeddedartistry.com/blog/2020/04/13/prefer-gcc-ar-to-ar-in-your-buildsystems/...

krzmaz

enhancement

remove fixed address 0x10000 for firmware

3

since this prevents to use a factory firmware which should be placed at address 0x10000. The flash address for the user firmware (ota_0) is read from the [partition.csv](https://github.com/arendst/Tasmota/blob/development/partitions/esp32_partition_app1856k_fs1344k.csv). A [flash_extra_images](https://github.com/arendst/Tasmota/blob/development/boards/esp32_4M.json)...

Jason2866