Skip to content
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

make: esptool2: Command not found #13

Closed
alexborisov opened this issue Mar 21, 2016 · 6 comments
Closed

make: esptool2: Command not found #13

alexborisov opened this issue Mar 21, 2016 · 6 comments

Comments

@alexborisov
Copy link

I'm trying to build the esp8266/Basic_Blink example but I'm getting the following error:

# Generating image...
make: esptool2: Command not found
make: *** [out/build/app.out] Error 127

I'm running a fresh vagrant provisioned with Sming as per the project wiki and this article

I've patched my provision.sh file to pull in esptools2 as per issue #12

cd ~/dev
if [ ! -e ~/dev/raburton-esp8266 ]; then
  git clone https://github.com/raburton/esp8266 raburton-esp8266
fi

if [ ! -e ~/dev/raburton-esp8266/esptool2 ]; then
  cd ~/dev/raburton-esp8266
  git clone https://github.com/raburton/esptool2.git
  git clone https://github.com/raburton/rboot
fi

cd ~/dev/raburton-esp8266/esptool2
export XTENSA_BINDIR=$XTENSA_TOOLS_ROOT
make 

So I'm assuming there is something wrong with the environment variables. I've updated them manually in Makefile-user.mk:

ESP_HOME = /opt/Espressif
SMING_HOME = /home/vagrant/dev/Sming/Sming

But i'm guessing something is off - seeing that I was pulling esptool2 into ~/dev/raburton-esp8266/

Any suggestions?

@slaff
Copy link
Owner

slaff commented Mar 22, 2016

@alexborisov Most probably the executable binary is not in the PATH. I will check this.

slaff pushed a commit that referenced this issue Mar 22, 2016
Simpliefies the Sming compilation (spiffy is no longer external program)
Related to #12 and #13.
@slaff
Copy link
Owner

slaff commented Mar 22, 2016

@alexborisov Can you get the latest git version and try again?

@alexborisov
Copy link
Author

# Generating image...
Generate firmware images successully in folder out/firmware.
Done

Awesome thanks. I hard reset everything and pulled the latest version. It looks like you fixed issue #12 as well 👍

@slaff slaff closed this as completed Mar 22, 2016
@rajatksud
Copy link

rajatksud commented Jun 2, 2016

i cloned the develop version and find that issue is there. the esptool2 path in the Makefile-project.mk shows
'# esptool2 path
ESPTOOL2 ?= esptool2
should this not be
ESPTOOL2 ?= $(ESP_HOME)/esptool2/esptool2
i hardcoded it to my path for the esp_home and it worked

@slaff
Copy link
Owner

slaff commented Jun 2, 2016

The line ESPTOOL2 ?= esptool2 in your Makefile-project.mk file means check if the ESPTOOL env variable is set and if yes use it otherwise use esptool2 as value.

The project/sming/provision.sh script should have set already the correct env variable.

HAS_ESPTOOL2=`cat $PROFILE_CONF | grep ESPTOOL2 || :`
if [ -z "$HAS_ESPTOOL2" ]; then
  sudo echo "export ESPTOOL2=`pwd`/esptool2" >>  $PROFILE_CONF
  source $PROFILE_CONF
fi 

My suggestion would be to run again the Sming provisioning. This means that from the host machine you should run again

PROJECT=sming vagrant provision

Then check inside of the guest machine, the one that Vagrant created, if inside of the /etc/profile.d/ directory there is an esp8266.sh profile file and if it contains line starting with export ESPTOOL2=

@rajatksud
Copy link

i am using vagrant on a windows machine and i cant seem to provision the projects.
vagrant provision keeps rebuilding the Espressif Home. I use cmder for this, although it does state project = sming but it does not update the Sming files. Thanks for the help. What you suggest seems correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants