Hi Uwe_pg, I also bought this board, and have problems getting it to work. Did you manage ? I have files from esp-adf-master, with AI-examples and components for the audio kit, but it is not clear how to install them, so you can select the audio kit. I was running esp-adf with the board and had ES83...

hi,
do you mean that when installing ESP-ADF , you need to use 2 paths ? :
adf_path=/esp/esp-adf
idf_path=/esp/esp-adf/esp-idf
instead of the idf_path=/esp/esp-idf ?
regards
Ludo

Make is now working in MINGW32, with ESP-IDF v3.2.2 It was not allowed to install toolchain 2.0, as this is for ESP-IDF v4.0 ...but that is not clearly mentioned in the install sheets. Also, I need to manually start IDF_PATH and ADF_PATH, as when starting up mingw32, it does not take into account th...

esp-adf is doing something weard. when I installed this, the whole /esp/home directory cannot be deleted anymore, and it comes to 1 filed in the blink/build/include/config/smp/slave/con This file is not accessible and cannot be deleted. I had this now 2 times. this con file cannot be deleted in the ...

path's are OK, but do not start up anymore from the profile.d directory, have to start them manually. and before, make menuconfig in blink worked, now, after installing the esp-adf I get the error $ make menuconfig Makefile:8: /make/project.mk: No such file or directory make: *** No rule to make tar...

after installing esp-adf, and having the error as mentioned, I go back to esp-idf and are facing the same problem.
It looks as if the adf install is messing up with the idf install....
back to zero.....

Hi, I installed esp-adf in /esp directory. copied play_mp3 directory in /esp, tried also in /esp/esp-adf ,went into play_mp3 and initiated make menuconfig again : $ make menuconfig Makefile:2: /project.mk: No such file or directory make: *** No rule to make target '/project.mk'. Stop. $ printenv ADF...

hi, thanks for your help. I got it to work with export IDF_PATH=/c/msys32/home/user/esp-idf-v3.2.2 tried your version : export IDF_PATH="c:/msys32/home/user/esp-idf-v3.2.2"..also works it is very confusing ...sometimes they refer to /c/, sometimes it is c:/ with ""......I took away the "".... at las...

when I click on the IDF_PATH.sh in the profile.d directory, it opens a screen and says :
bash: c:/msys32/home/user/esp-idf-v3.2.2: is a directory
/usr/bin/bash: Exit 126.
so this does not work..therefore, no automatically created path...now to solve this...

somehow, the system does not take the IDF_PATH file in profile.d directory. when I now manually export it, the path is returned (there was confusion of the export IDF_PATH, which in a documents also was written as EXPORT_IDF_PATH as name.....so had to do export export_idf_path) I now have following ...