-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another build error ESP32-S3 WROOM N16R8 #614
Comments
The error seems to occur in Windows and is said to be related to the Arduino Core V3.1.0 |
Arduino 3.1.1 and IDF 5.3.2.241224 Win 11 Version 10.0.22631 Build 22631not working for me. |
Hello Wolle, I changed the following Platformio.ini [env] ;platform = https://github.com/pioarduino/platform-espressif32/releases/download/stable/platform-espressif32.zip ;Arduino core 3.1.0 / IDF 5.3.1 seems to be working. For me the file name was too long |
Hello, it is a Windows limitation. Path length limit is max 32767 Bytes. For bigger projects that's not enough. I have a fix included in pioarduino which is not yet in a release build. platform = https://github.com/pioarduino/platform-espressif32.git#develop or platform = https://github.com/pioarduino/platform-espressif32.git#devel/v3.2.x |
@schreibfaul1 There is an option in pioarduino to change sdkconfig settings for Arduino without the need to build the project as Arduino as an component of IDF. I call it Hybrid Compile. This mode is developed from me and just for such use cases you have. Adjusting "some" sdkconfig settings for Arduino. See example https://github.com/pioarduino/platform-espressif32/blob/6a5e1fcf97c3a378b20c48853667b017f05fc942/examples/arduino-blink/platformio.ini#L48-L72 |
Hi @Jason2866, And I will soon be trying out the "Hybrid Compile". best regards |
@schreibfaul1 Viele Grüße aus dem Süden von Deutschland. Tolles Projekt dein Webradio! |
@Jason2866 viele Grüße aus Berlin :-) |
Thank you very much! I tried the current version of the code, and it no longer gives a compilation error, so I eagerly uploaded it to the ESP32-S3-WROOM-1 N16R8 (at least that’s what it says on it) using the default settings in platformio.ini and the necessary modifications in common.h. However, the ILI9341 display did not light up. I connected BL to 3.3V, and the backlight turned on, but that’s all! Assuming the code is running correctly but the SD card is not working, how long does it take for an error message to appear? I tried checking the Serial Monitor, and it doesn't seem right; the board keeps resetting, and the memory settings don’t seem to be OK: ���ESP-ROM:esp32s3-20210327 SPIWP:0xee abort() was called at PC 0x40377830 on core 0 Backtrace: 0x40378361:0x3fceb220 0x4037fc05:0x3fceb240 0x40387b5e:0x3fceb260 0x40377830:0x3fceb2d0 0x403cc9fd:0x3fceb340 0x403ccd19:0x3fceb380 0x403c8905:0x3fceb4b0 0x40045c01:0x3fceb570 0x40043ab6:0x3fceb6f0 0x40034c45:0x3fceb710 It seems like the board keeps rebooting due to an external RAM failure. Any ideas on how to fix this? Wrong ESP? |
@Bigpriap Looks like false PSRAM type. If you have an boards json used with QIO PSRAM use OPI PSRAM and vice versa. |
I find this project fascinating, but unfortunately, I am currently stuck as I cannot compile without errors.
I am using the latest version of Visual Studio Code, version 1.9.6.4, with the PlatformIO extension, and I have followed all the steps in the guide. Since I am not a programmer, I initially thought I was doing something wrong. However, today I asked a programmer friend to try it on his laptop, setting up everything from scratch.
For the ESP32 Wroom1 (N16R8) variant, I am getting the same compilation error:
Archiving .pio\build\esp32s3\esp-idf\framework-arduinoespressif32\libframework-arduinoespressif32.a
The command line is too long.
Compiling .pio\build\esp32s3\hal\rmt_hal.c.o
Compiling .pio\build\esp32s3\hal\pcnt_hal.c.o
*** [.pio\build\esp32s3\esp-idf\framework-arduinoespressif32\libframework-arduinoespressif32.a] Error 1
[FAILED] Took 73.38 seconds
I also tried IDF 5.3.1, but the issue persists.
Can anyone help me, please?
The text was updated successfully, but these errors were encountered: