evert-arias / EasyBuzzer

The Beep Library For Arduino
https://evert-arias.github.io/EasyBuzzer
MIT License
84 stars 22 forks source link

Cant seem to compile esp32 #25

Open Tezzatron81 opened 2 months ago

Tezzatron81 commented 2 months ago

Cant seem to compile the examples with esp32. Im trying to make 3 tones a 4800 for 800ms then 4500 for 800ms then 4000 for 800ms. Then stop.

alexitoo00 commented 3 days ago

I've also tried compiling for WROOM and WROVER esp32 boards. The examples don't compile. This is the result after trying to compile:

C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer\src\EasyBuzzer.cpp: In constructor 'EasyBuzzerClass::EasyBuzzerClass()': C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer\src\EasyBuzzer.cpp:17:9: error: 'ledcSetup' was not declared in this scope 17 | ledcSetup(mChannel, mFreq, mResolution); | ^~~~~ C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer\src\EasyBuzzer.cpp: In member function 'void EasyBuzzerClass::stopBeep()': C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer\src\EasyBuzzer.cpp:79:9: error: 'ledcDetachPin' was not declared in this scope; did you mean 'ledcDetach'? 79 | ledcDetachPin(mPin); | ^~~~~ | ledcDetach C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer\src\EasyBuzzer.cpp: In member function 'void EasyBuzzerClass::update()': C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer\src\EasyBuzzer.cpp:139:17: error: 'ledcAttachPin' was not declared in this scope; did you mean 'ledcAttach'? 139 | ledcAttachPin(mPin, mChannel); | ^~~~~ | ledcAttach C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer\src\EasyBuzzer.cpp:144:17: error: 'ledcDetachPin' was not declared in this scope; did you mean 'ledcDetach'? 144 | ledcDetachPin(mPin); | ^~~~~ | ledcDetach Usando librería EasyBuzzer con versión 1.0.4 en la carpeta: C:\Users\alexa\Documents\Arduino\libraries\EasyBuzzer exit status 1 Error compilando para la tarjeta ESP32-WROOM-DA Module.

The error seems to resolve if downgrading to version 2.0.16 of ESP32 from Espressif

Update: On 2.0.17 it is not working but throws a different error. In 2.0.16 it is in fact working fine