First we clone esptool repository, then we get latest SDK release directly
from forum and finally we ran esptool.
If you will get something like this:
Traceback (most recent call last):
File "../../esptool/esptool.py", line 408, in <module>
File "../../esptool/esptool.py", line 143, in connect
raise Exception('Failed to connect')
Exception: Failed to connect
You can work around this by toggling power to the module right before executing
esptool command. It works on my side.
esp-open-sdk at the moment of writing this post didn’t support v0.9.5 SDK,
but adding this support was pretty straight forward and can be found on my
github for of the repo.
There is also pending PR that hopefully will be merged.
Procedure is straight forward to follow:
git clone email@example.com:pietrushnic/esp-open-sdk.git #or use https with https://github.com/pietrushnic/esp-open-sdk.git
git co v0.9.5-support
sed -i -e '/\s0.9.4/s/^/#/g' -e '/\s0.9.5/s/^#//g' Makefile
sed command will cause using 0.9.5 string as VENDOR_SDK for default build.
On my i7-4700 single threaded compilation takes ~20min. BTW I’m trying to
figure out why I cannot use multiple jobs
Just execute this command in your shell. If you missed that message run make
again it should skip all already compiled parts and display final message
To use toolchain with example code from v0.9.5 SDK you can simply:
Use package like it was presented in “Upgrade using binaries from Espressif” section. Trying to compile exmaples in esp-open-sdk will give you error like this:
../../Makefile:154: warning: overriding recipe for target 'clean'
../Makefile:258: warning: ignoring old recipe for target 'clean'
You cloned without --recursive, fetching submodules for you.
git submodule update --init --recursive
make -C crosstool-NG -f ../Makefile _ct-ng
make: *** crosstool-NG: No such file or directory. Stop.
../../Makefile:140: recipe for target 'crosstool-NG/ct-ng' failed
make: *** [crosstool-NG/ct-ng] Error 2
When inside esp_iot_sdk_v0.9.5:
cp -r examples/at .
Ommiting COMPILE=gcc will result in error caused by using differen compiler name:
Thanks for reading. Hope that this post fill the gap that some of beginner can
experience when goolging through straight forward tutorial about playing with
ESP. If you like this post please share. If you see some bias or you just want
to share some facts, ask question then please leave a comment.
Founder and Embedded Systems Consultant at 3mdeb as well as freelance CTO of Vitro Technology and CEO of LPN Plant. Passionate about building firmware that enables advanced hardware features in modern products. Dedicated to customers that treat embedded software security and upgradeability as forethought. Open source firmware evangelist interested in platform security and trusted computing. In favor of fixed price projects with a clear definition of success.