I have a project that uses two platforms: espressif32 and ststm32.
A commit that previously worked no longer works for ESP32.
Here is my ini file:
[platformio] default_envs = esp32doit-devkit-v1 [env:esp32doit-devkit-v1] platform = espressif32 board = esp32doit-devkit-v1 framework = espidf monitor_speed = 115200 monitor_flags = --raw monitor_rts = 1 monitor_dtr = 0 upload_speed = 921600 [env:nucleo_f446ze] platform = ststm32 board = nucleo_f446ze framework = mbed
I get the following error messages:
ValueError: Please set custom_freertos_config_location in your platformio.ini to the location of a FreeRTOSConfig.h header file -- relative to the location of platformio
File "C:\Users\<user>\.platformio\lib\STM32Cube Middleware-FreeRTOS_ID6696\add_config.py", line 15: raise ValueError("Please set custom_freertos_config_location in your platformio.ini to the location of a FreeRTOSConfig.h header file -- relative to the location of platformio.ini")
I’ve done a platformio clean. I’ve removed the build folders manually. Restarted platformio and my PC and even reinstalled espressif32 platform because I got the following error message suddenly:
"C:/Users/<user>/.platformio/packages/toolchain-xtensa32/bin/xtensa-esp32-elf-gcc.exe" is not able to compile a simple test program.
The weird thing is that neither environment uses STM32Cube Middleware-FreeRTOS in this commit! It is like ghost build artifact somewhere.
I’ve noticed that unlike the Ubuntu version the Windows version of platformio doesn’t create new vscode files after deletion and subsequent saving of the platformio project.
I have platformio version Core 4.3.1 Home 3.1.1. I can’t wait until platformio releases its first stable version, since I’ve been having nothing but problems on both Windows and Ubuntu.