Return to the land of ESP LUA

As I’d just installed the latest update to the ECLIPSE environment.. I thought I might take a look again at LUA to see what version was on there.

Sure enough – the latest.. but look what happened when failing to connect to an access point – I asked for a list of access points..

image

Hmm. Best go to the site and get a fresh copy I think and hope it compiles.

 

So:

I went to the NODEMCU site … https://github.com/nodemcu/nodemcu-firmware

Grabbed the ZIP file – and after ensuring all files had been removed from the ECLIPSE setup, unzipped then renamed (to exclude –master) the package into the EXAMPLES folder in ESPRESSIF..

I imported the project – changed the PORT number to the port number of my FTDI (does anyone know how we can specify that ONCE somewhere and have all the projects take notice).. and

 

17:50:03 **** Build of configuration Default for project nodemcu-firmware ****
make clean
Cannot run program "make": Launching failed

Error: Program "make" not found in PATH
PATH=[C:\Windows\system32;C:/Program Files (x86)/Java/jre1.8.0_25/bin/client;C:/Program Files (x86)/Java/jre1.8.0_25/bin;C:/Program Files (x86)/Java/jre1.8.0_25/lib/i386;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\ProgramData\Oracle\Java\javapath;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\adb;C:\Program Files\nodejs\;C:\Users\Peter\AppData\Roaming\npm;C:\Espressif\xtensa-lx106-elf\bin]

17:50:03 Build Finished (took 47ms)

 

On advice from a friend I added this to the PATH variable (don’t understand why it’s not in there)

C:\MinGW\bin;C:\MinGW\msys\1.0\bin; C:\Python27;

 

I added this here… right click the project – properties – C/C++ Build – Environment – PATH.

 

C:\Windows\system32;C:/Program Files (x86)/Java/jre1.8.0_25/bin/client;C:/Program Files (x86)/Java/jre1.8.0_25/bin;C:/Program Files (x86)/Java/jre1.8.0_25/lib/i386;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\ProgramData\Oracle\Java\javapath;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\adb;C:\Program Files\nodejs\;C:\Users\Peter\AppData\Roaming\npm;C:\Espressif\xtensa-lx106-elf\bin;C:\MinGW\bin;C:\MinGW\msys\1.0\bin; C:\Python27

I must tidy this up as I don’t have some of those directories but everything else compiles ok…

CLEAN  -WORKS

ALL – WORKS right to the end and then…

 

make[2]: Leaving directory `/c/Espressif/examples/nodemcu-firmware/app/spiffs’
xtensa-lx106-elf-gcc  -L../lib -nostdlib -T../ld/eagle.app.v6.ld -Wl,–no-check-sections -u call_user_start -Wl,-static -Wl,–start-group -lc -lgcc -lhal -lphy -lpp -lnet80211 -lwpa -lmain -ljson user/.output/eagle/debug/lib/libuser.a driver/.output/eagle/debug/lib/libdriver.a lwip/.output/eagle/debug/lib/liblwip.a json/.output/eagle/debug/lib/libjson.a ssl/.output/eagle/debug/lib/libssl.a upgrade/.output/eagle/debug/lib/libupgrade.a platform/.output/eagle/debug/lib/libplatform.a libc/.output/eagle/debug/lib/liblibc.a lua/.output/eagle/debug/lib/liblua.a smart/.output/eagle/debug/lib/smart.a wofs/.output/eagle/debug/lib/wofs.a spiffs/.output/eagle/debug/lib/spiffs.a modules/.output/eagle/debug/lib/libmodules.a -Wl,–end-group -o .output/eagle/debug/image/eagle.app.v6.out
../tools/esptool.py elf2image .output/eagle/debug/image/eagle.app.v6.out -o ..\\bin\\
/usr/bin/env: python: No such file or directory
make[1]: *** [.output/eagle/debug/bin/eagle.app.v6.bin] Error 127
make[1]: Leaving directory `/c/Espressif/examples/nodemcu-firmware/app’
make: *** [.subdirs] Error 2

17:55:02 Build Finished (took 44s.245ms)

Ideas anyone?

Advertisements

6 thoughts on “Return to the land of ESP LUA

  1. Hi Peter,

    Is it possible you walked over your working make file (from the eclipse-sdk version) when you directly downloaded the nodemcu lua stuff and copied that into your examples/ version of the project?

    I don’t know if or where CHERTS has made the files from his eclipse SDK available, and I’m away from my dev system, so i can’t just throw you the file. Worst case, you’d have to re-install the latest eclipse ESP8266 sdk to get back to the working make file.

    Anyway it seems you got it to build…? Can you see some freshly compiled .bin files somewhere in the project dir?

    If you did get bin files, then the remaining issue is just to flash the ESP8266. If you type ‘python’ in a DOS prompt, what do you get? Or, in the make file, you can try to change the call for esptool.py to esptool.exe, which I believe you mentioned you already have or prefer?

    I may have mentioned elsewhere that I just use a .bat file in every project to do the flashing;

  2. Hi there

    Thanks a pal helped me tonight – I’m sure this is something that could be fixed in the original files..

    For the benefit of others – (right click the properties of the project in the LEFT pane of ECLIPSE, C/C++ build, Environment – PATH – EDIT) I had to add C:\MinGW\bin;C:\MinGW\msys\1.0\bin; C:\Python27 to the system path as they don’t seem to be in there. Additional complication – ECLIPSE does not see this change until you close down – and start up again. I now have a working compile thanks and I’ve blown a chip and it works,

    • Well, as I noted this morning – finally a test setup – it has not yet been added to the mainstream Lua and we’ve no information on how much precious RAM it will use. I’ve been testing the BIN files all day, reported a trivial potential issue, noted RAM usage – BUT – I’ve a test rig subscribing to 2 items – and it hasn’t fallen over yet!!! more info soon.

  3. this seems to be an environment problem. Many times the Python2 executable is called python2 in order to distinguish it from Python3. Many environments run both versions in parallel. In your case this might also be called python2.exe. Looks like you have to adjust the Makefile or rename the python binary (are there symlinks in windows – I do not know).

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s