Page 1 of 1

compiled windows (64?) xtensa-esp108 toolchain

Posted: Sun Dec 27, 2015 10:38 pm
by ladyada
merry merry!
Want to compile on windows? here ya go, its a cygwin64 compilation of the esp31/32 crosstools-ng toolchain from the beta PDF. I did toss in cygwin1.dll but no guarantees this will work outside of cygwin. Also, i compiled on a 64-bit win7 machine so dunno if this will work on 32-bit
you can upload with an FTDI-like cable, i had to set the COM port to COM4 and it then appeared as /dev/ttyS3 which is what you'll have to pass into esp31tool
i suggest installing cygwin and getting all the companion tools like make, patch, python, etc from there and using the cygwin terminal for starters

http://adafruit-download.s3.amazonaws.c ... 151227.zip

Re: compiled windows (64?) xtensa-esp108 toolchain

Posted: Mon Dec 28, 2015 12:57 am
by Baoshi
Hi ladyada,

I'm able to run it under Cygwin environment, Thanks!

However it seems I'm not able to run it alone outside Cygwin. It gives
" *** fatal error - cygheap base mismatch detected - 0x180320400/0x180321400. This problem is probably due to using incompatible versions of the cygwin DLL. Search for cygwin1.dll using the Windows Start->Find/Search facility and delete all but the most recent version. The most recent version *should* reside in x:\cygwin\bin, where 'x' is the drive on which you have installed the cygwin distribution. Rebooting is also suggested if you are unable to find another cygwin DLL." - under a Windows command prompt. I'm pretty sure I only have one cygwin1.dll in the system.

Coincidently I've compiled the same for Cygwin32, I've uploaded it to https://dl.dropboxusercontent.com/u/347 ... 151227.zip
Same thing I can use it under 32-bit cygwin but not native windows command prompt (different error).

I found the original crosstool-ng lx106 target toolchain was compiled under Mingw64, still trying to figure out how to compile the esp108 one.

Baoshi

Re: compiled windows (64?) xtensa-esp108 toolchain

Posted: Mon Dec 28, 2015 8:03 am
by CHERTS
Hi all

I released a Beta version of Unofficial Development Kit for Espressif ESP32

The kit includes the following components and tools:
* Unofficial GCC compiler for SoC Xtensa L108.
* Official Espressif ESP32 RTOS SDK v1.1.0
* Documentation for SoC ESP32.
* Examples in the firmware source code in C language.
* Additional tools for working with boards based on the ESP32.

http://esp32.com/viewtopic.php?f=13&t=83&p=340

Re: compiled windows (64?) xtensa-esp108 toolchain

Posted: Tue Dec 29, 2015 7:23 am
by cdtdoug
Yeah, you really need a MinGW-based toolchain to work properly on Windows, especially with the Eclipse C/C++ IDE. It looks like CHERTS has one with his SDK. I'm planning on doing one based on my Arduino C++ CDT plug-ins. I really like how Arduino has made it easy to add new hardware to the build and launch system. I think we can reuse that for non-Arduino platforms like the ESP family. I also have a formula for building gnu toolchains for Linux, MinGW and Mac that would give us support on the three major hosts. No promises on when I'll get around to that. And I don't have an ESP32/31 board yet anyway, but I'll get there.

Re: compiled windows (64?) xtensa-esp108 toolchain

Posted: Tue Jan 26, 2016 3:20 am
by rudi ;-)
Baoshi wrote: ..
I found the original crosstool-ng lx106 target toolchain was compiled under Mingw64, still trying to figure out how to compile the esp108 one.
hi baoshi,
have you found a runing way for mingw?
:)
let us know how you did it :mrgreen:
http://esp32.com/viewtopic.php?f=2&t=111

best wishes
rudi ;-)

Re: compiled windows (64?) xtensa-esp108 toolchain

Posted: Fri Jan 29, 2016 10:22 am
by rudi ;-)
Baoshi wrote: ..
However it seems I'm not able to run it alone outside Cygwin.
..
Same thing I can use it under 32-bit cygwin but not native windows command prompt (different error).
hi baoshi

successful done the toolchain here in cygwin too.
( have used cygwin32 on OS64 )

if you have only one cygwin1.dll, that is in your c:\cygwin install folder c:\cygwin\bin
test this:

rename the c:\cygwin to :\cygwin-test
( yes this will chrash the build because cygwin1.dll was not found )

but now for using outside:
for win64 OS and cygwin32 builds:

if you use win64 system and the cygwin32 toolchain then copy the cygwin1.dll to the c:\windows\wow64 folder then you ready for this without c:\cygwin\bin;

btw copy the cygwin1.dll to the /xtensa-esp108-elf/bin folder has no effect.

rules:
cygwin1.dll from cygwin32 is not the same like cygwin64.
be sure, you use the right cygwin1.dll version ( 32 / 64 ) which was build the toolchain.

the cygwin1.dll must be on OS System folder, which you use the cygwin1.dll for it.
you will use the cygwin1.dll for OS64, then copy the dll in c:\windows\wow64
you will use the cygwin1.dll for OS32, then copy the dll in c:\windows\system32 ( i have install to c:\windows\wow32 too )

then you can use it outside cygwin folder / you need not install cygwin
thats the second trick

best wishes
rudi ;-)

Re: compiled windows (64?) xtensa-esp108 toolchain

Posted: Fri Mar 04, 2016 9:12 am
by Chinmay_K
Hey ladyada,
I followed your steps as mentioned on the adafruit link: https://learn.adafruit.com/compiling-a- ... s/overview
and also your video tutorial, and i guess i have succesfully configured the toolchain.
But when compiling i came across some huge chunks of error message when i try to execute 'make clean' and 'make'.
I hv used cygwin64 terminal for toolchain configuration ,I hv attached below some snips of the terminal window which shows the error as well my toolchain directory finishing installation succesfully.

Can any please help me out,i dnt hv any idea what this error might be....

Re: compiled windows (64?) xtensa-esp108 toolchain

Posted: Mon Jun 06, 2016 9:33 am
by rudi ;-)
hi
your_path_is_missing.png
your_path_is_missing.png (7.94 KiB) Viewed 20153 times
your path to the toolchain is missing
you can setup it in a batch file before you compile/link

Code: Select all

path=your_path_to_your_toolchain;%path%
or you can edit/create a system environment for this

or you can append it, when you build the toolchain by registry command
example a other gnu build ( gcc )

Code: Select all


../binutils-<version>/configure --target arm-eabi --enable-win32-registry=MyToolchainName --prefix /c/gnu/out


and be sure you will then append in the registry too like this

Code: Select all


[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Free Software Foundation\MyToolchainName]
"GCC"="C:\\New-Location"
"BINUTILS"="C:\\New-Location"
"G++"="C:\\New-Location"

be sure you have installed cygwin.dll in the windows 32 folder too.

best wishes
rudi ;-)