www.robowars.org

RoboWars Australia Forum Index -> General Chatter

ESP8266
Goto page Previous  1, 2, 3, 4, 5  Next

Post new topic   Reply to topic
  Author    Thread
Tim



Joined: 30 Oct 2013
Posts: 247
Location: QLD


 Reply with quote  

Missed the emails good work! Very Happy

So this has taken up most of my time, the weeks I spent trying to send the esp8266 AT commands was a waste.....thought it was my hardware turns out I'm not the only one some of the units come shipped with IoT Demo on them "allegedly" so I put it down to that....also my USB serial adapter did not pass a loop back test.... yes I had been attempting to communicate with it.

So I setup two uno's as master and slave I2c just for sanity sake Rolling Eyes

After seeing a few of CLNohr's videos I was keen to get this going sweet idea the wifi cup.

Where I'm at - ditched the virtual machine that was on a win 8 machine (Asus 64bit) /gave up on the esp8266 toolchain that's a different story makefiles were not working when I called make dispite the fact the MakeFile was in the same folder as the gen.misc files? over the last 72 hours I've been on a ISO burning frenzy lol a of linux distros amongst others that didn't work prob user ie. my fault related - OS currently installed Debian 7.7, Ubuntu 13.10 Mint 17.1 (x 2 versions) on an identical Asus machine, following CLNohr's video tutorial https://www.youtube.com/watch?v=pWo-ErpVZC4 and using the associated git repo https://github.com/cnlohr/ws2812esp8266 I have got as far as the final build command

code:
./build-elf.sh lx106

which fails, after which the terminal brings a config log to my attention I've read it, however I am by no means a *nix expert far from it new and still learning.

Below is the config file if any one has the time to read it I would love to hear your thoughts, I'm following the tutorial to the letter, obviously this is my fault and I'm making a mistake somewhere however I can't seem to see it? log from a Linux Mint 17.1 32 bit iso installed on a 64bit Asus machine for some reason the 64bit iso's just give a grey/black screen when attempting to boot so I've been using 32bit images.

code:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.64.  Invocation command line was

  $ ../../binutils-2.24/configure --prefix=/home/tim5/esp8266/xtensa-toolchain-build/build-lx106/root --target=xtensa-lx106-elf --disable-shared --disable-werror

## --------- ##
## Platform. ##
## --------- ##

hostname = mint-test-os
uname -m = i686
uname -r = 3.13.0-37-generic
uname -s = Linux
uname -v = #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2317: checking build system type
configure:2331: result: i686-pc-linux-gnu
configure:2378: checking host system type
configure:2391: result: i686-pc-linux-gnu
configure:2411: checking target system type
configure:2424: result: xtensa-lx106-elf
configure:2478: checking for a BSD-compatible install
configure:2546: result: /usr/bin/install -c
configure:2557: checking whether ln works
configure:2579: result: yes
configure:2583: checking whether ln -s works
configure:2587: result: yes
configure:2594: checking for a sed that does not truncate output
configure:2658: result: /bin/sed
configure:2667: checking for gawk
configure:2683: found /usr/bin/gawk
configure:2694: result: gawk
configure:3962: checking for gcc
configure:3978: found /usr/bin/gcc
configure:3989: result: gcc
configure:4218: checking for C compiler version
configure:4227: gcc --version >&5
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:4238: $? = 0
configure:4227: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.8/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-i386/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-i386 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-i386 --with-arch-directory=i386 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-targets=all --enable-multiarch --disable-werror --with-arch-32=i686 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
configure:4238: $? = 0
configure:4227: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:4238: $? = 4
configure:4227: gcc -qversion >&5
gcc: error: unrecognized command line option '-qversion'
gcc: fatal error: no input files
compilation terminated.
configure:4238: $? = 4
configure:4258: checking for C compiler default output file name
configure:4280: gcc    conftest.c  >&5
/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
/usr/bin/ld: cannot find -lc
/usr/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:4284: $? = 1
configure:4321: result:
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:4327: error: in `/home/tim5/esp8266/xtensa-toolchain-build/build-lx106/binutils-2.24-elf':
configure:4331: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=i686-pc-linux-gnu
ac_cv_env_AR_FOR_TARGET_set=
ac_cv_env_AR_FOR_TARGET_value=
ac_cv_env_AR_set=
ac_cv_env_AR_value=
ac_cv_env_AS_FOR_TARGET_set=
ac_cv_env_AS_FOR_TARGET_value=
ac_cv_env_AS_set=
ac_cv_env_AS_value=
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_FOR_TARGET_set=
ac_cv_env_CC_FOR_TARGET_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_FOR_TARGET_set=
ac_cv_env_CXX_FOR_TARGET_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_DLLTOOL_FOR_TARGET_set=
ac_cv_env_DLLTOOL_FOR_TARGET_value=
ac_cv_env_DLLTOOL_set=
ac_cv_env_DLLTOOL_value=
ac_cv_env_GCC_FOR_TARGET_set=
ac_cv_env_GCC_FOR_TARGET_value=
ac_cv_env_GCJ_FOR_TARGET_set=
ac_cv_env_GCJ_FOR_TARGET_value=
ac_cv_env_GFORTRAN_FOR_TARGET_set=
ac_cv_env_GFORTRAN_FOR_TARGET_value=
ac_cv_env_GOC_FOR_TARGET_set=
ac_cv_env_GOC_FOR_TARGET_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LD_FOR_TARGET_set=
ac_cv_env_LD_FOR_TARGET_value=
ac_cv_env_LD_set=
ac_cv_env_LD_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_LIPO_FOR_TARGET_set=
ac_cv_env_LIPO_FOR_TARGET_value=
ac_cv_env_LIPO_set=
ac_cv_env_LIPO_value=
ac_cv_env_NM_FOR_TARGET_set=
ac_cv_env_NM_FOR_TARGET_value=
ac_cv_env_NM_set=
ac_cv_env_NM_value=
ac_cv_env_OBJCOPY_set=
ac_cv_env_OBJCOPY_value=
ac_cv_env_OBJDUMP_FOR_TARGET_set=
ac_cv_env_OBJDUMP_FOR_TARGET_value=
ac_cv_env_OBJDUMP_set=
ac_cv_env_OBJDUMP_value=
ac_cv_env_RANLIB_FOR_TARGET_set=
ac_cv_env_RANLIB_FOR_TARGET_value=
ac_cv_env_RANLIB_set=
ac_cv_env_RANLIB_value=
ac_cv_env_READELF_FOR_TARGET_set=
ac_cv_env_READELF_FOR_TARGET_value=
ac_cv_env_READELF_set=
ac_cv_env_READELF_value=
ac_cv_env_STRIP_FOR_TARGET_set=
ac_cv_env_STRIP_FOR_TARGET_value=
ac_cv_env_STRIP_set=
ac_cv_env_STRIP_value=
ac_cv_env_WINDMC_FOR_TARGET_set=
ac_cv_env_WINDMC_FOR_TARGET_value=
ac_cv_env_WINDMC_set=
ac_cv_env_WINDMC_value=
ac_cv_env_WINDRES_FOR_TARGET_set=
ac_cv_env_WINDRES_FOR_TARGET_value=
ac_cv_env_WINDRES_set=
ac_cv_env_WINDRES_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_build_configargs_set=
ac_cv_env_build_configargs_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_host_configargs_set=
ac_cv_env_host_configargs_value=
ac_cv_env_target_alias_set=set
ac_cv_env_target_alias_value=xtensa-lx106-elf
ac_cv_env_target_configargs_set=
ac_cv_env_target_configargs_value=
ac_cv_host=i686-pc-linux-gnu
ac_cv_path_SED=/bin/sed
ac_cv_path_install='/usr/bin/install -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_ac_ct_CC=gcc
ac_cv_target=xtensa-lx106-elf
acx_cv_prog_LN=ln

## ----------------- ##
## Output variables. ##
## ----------------- ##

AR=''
AR_FOR_BUILD='$(AR)'
AR_FOR_TARGET=''
AS=''
AS_FOR_BUILD='$(AS)'
AS_FOR_TARGET=''
AWK='gawk'
BISON=''
BUILD_CONFIG=''
CC='gcc'
CC_FOR_BUILD='$(CC)'
CC_FOR_TARGET=''
CFLAGS=''
CFLAGS_FOR_BUILD=''
CFLAGS_FOR_TARGET=''
COMPILER_AS_FOR_TARGET=''
COMPILER_LD_FOR_TARGET=''
COMPILER_NM_FOR_TARGET=''
CONFIGURE_GDB_TK=''
CPPFLAGS=''
CXX=''
CXXFLAGS=''
CXXFLAGS_FOR_BUILD=''
CXXFLAGS_FOR_TARGET=''
CXX_FOR_BUILD='$(CXX)'
CXX_FOR_TARGET=''
DEBUG_PREFIX_CFLAGS_FOR_TARGET=''
DEFS=''
DLLTOOL=''
DLLTOOL_FOR_BUILD='$(DLLTOOL)'
DLLTOOL_FOR_TARGET=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EXEEXT=''
EXPECT=''
EXTRA_CONFIGARGS_LIBJAVA='--disable-static'
FLAGS_FOR_TARGET=''
FLEX=''
GCC_FOR_TARGET=''
GCC_SHLIB_SUBDIR=''
GCJ_FOR_BUILD='$(GCJ)'
GCJ_FOR_TARGET=''
GDB_TK=''
GFORTRAN_FOR_BUILD='$(GFORTRAN)'
GFORTRAN_FOR_TARGET=''
GNATBIND=''
GNATMAKE=''
GOC_FOR_BUILD='$(GOC)'
GOC_FOR_TARGET=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_GDB_TK=''
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
LD=''
LDFLAGS=''
LDFLAGS_FOR_BUILD=''
LDFLAGS_FOR_TARGET=''
LD_FOR_BUILD='$(LD)'
LD_FOR_TARGET=''
LEX=''
LIBOBJS=''
LIBS=''
LIPO=''
LIPO_FOR_TARGET=''
LN='ln'
LN_S='ln -s'
LTLIBOBJS=''
M4=''
MAINT=''
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE=''
MAKEINFO=''
NM=''
NM_FOR_BUILD='$(NM)'
NM_FOR_TARGET=''
OBJCOPY=''
OBJDUMP=''
OBJDUMP_FOR_TARGET=''
OBJEXT=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_URL=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
RANLIB=''
RANLIB_FOR_BUILD='$(RANLIB)'
RANLIB_FOR_TARGET=''
RAW_CXX_FOR_TARGET=''
READELF=''
READELF_FOR_TARGET=''
RPATH_ENVVAR=''
RUNTEST=''
SED='/bin/sed'
SHELL='/bin/bash'
STRIP=''
STRIP_FOR_TARGET=''
SYSROOT_CFLAGS_FOR_TARGET=''
TOPLEVEL_CONFIGURE_ARGUMENTS='../../binutils-2.24/configure --prefix=/home/tim5/esp8266/xtensa-toolchain-build/build-lx106/root --target=xtensa-lx106-elf --disable-shared --disable-werror'
WINDMC=''
WINDMC_FOR_BUILD='$(WINDMC)'
WINDMC_FOR_TARGET=''
WINDRES=''
WINDRES_FOR_BUILD='$(WINDRES)'
WINDRES_FOR_TARGET=''
YACC=''
ac_ct_CC='gcc'
ac_ct_CXX=''
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnu'
build_alias=''
build_configargs=''
build_configdirs='build-libiberty build-texinfo build-flex build-bison build-m4 build-fixincludes'
build_cpu='i686'
build_libsubdir='build-i686-pc-linux-gnu'
build_noncanonical='i686-pc-linux-gnu'
build_os='linux-gnu'
build_subdir='build-i686-pc-linux-gnu'
build_tooldir=''
build_vendor='pc'
clooginc=''
clooglibs=''
compare_exclusions=''
configdirs='intl libiberty opcodes bfd readline tcl tk itcl libgui zlib libbacktrace libcpp libdecnumber gmp mpfr mpc isl cloog libelf libiconv texinfo flex bison binutils gas ld fixincludes gcc cgen sid sim gdb gprof etc expect dejagnu m4 utils guile fastjar gnattools'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
do_compare=''
docdir='${datarootdir}/doc/${PACKAGE}'
dvidir='${docdir}'
exec_prefix='NONE'
extra_host_libiberty_configure_flags=''
extra_isl_gmp_configure_flags=''
extra_mpc_gmp_configure_flags=''
extra_mpc_mpfr_configure_flags=''
extra_mpfr_configure_flags=''
gmpinc=''
gmplibs=''
host='i686-pc-linux-gnu'
host_alias=''
host_configargs=''
host_cpu='i686'
host_noncanonical='i686-pc-linux-gnu'
host_os='linux-gnu'
host_subdir='.'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
islinc=''
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
poststage1_ldflags=''
poststage1_libs=''
prefix='/home/tim5/esp8266/xtensa-toolchain-build/build-lx106/root'
program_transform_name='s&^&xtensa-lx106-elf-&'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
stage1_cflags=''
stage1_checking=''
stage1_languages=''
stage1_ldflags=''
stage1_libs=''
stage2_werror_flag=''
sysconfdir='${prefix}/etc'
target='xtensa-lx106-elf'
target_alias='xtensa-lx106-elf'
target_configargs=''
target_configdirs='target-libgcc target-libbacktrace target-libgloss target-newlib target-libgomp target-libatomic target-libitm target-libstdc++-v3 target-libmudflap target-libsanitizer target-libvtv target-libssp target-libquadmath target-libgfortran target-boehm-gc target-libffi target-zlib target-libjava target-libobjc target-libada target-libgo target-rda'
target_cpu='xtensa'
target_noncanonical='xtensa-lx106-elf'
target_os='elf'
target_subdir='xtensa-lx106-elf'
target_vendor='lx106'
tooldir=''

## ------------------- ##
## File substitutions. ##
## ------------------- ##

alphaieee_frag=''
host_makefile_frag='/dev/null'
ospace_frag=''
serialization_dependencies=''
target_makefile_frag=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""

configure: exit 77




Thanks in advance to anyone who can shed some light on the matter Very Happy

Cheers Tim

Post Wed Jan 14, 2015 6:01 am 
 View user's profile Send private message
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  

Hmmmm have you tried the one I did?

I saw the tutorial but already had stuff up and running. So haven't been through it personally. I will give it a go on the weekend and will let you know how I go.

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com

Post Wed Jan 14, 2015 9:34 am 
 View user's profile Send private message Send e-mail MSN Messenger
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  

Actually have you done.

sudo apt-get install build-essential libc6-dev

I think your missing libc6-dev.

Then try running that again.

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com

Post Wed Jan 14, 2015 9:39 am 
 View user's profile Send private message Send e-mail MSN Messenger
Tim



Joined: 30 Oct 2013
Posts: 247
Location: QLD


 Reply with quote  

Hi Steve, Thanks for reading the config file, I have tried sudo apt-get install build-essential libc6-dev which fails yet can be installed manually still has issues, so after some digging I found that sudo apt-get install g++-multilib installs the required libs. However according to this thread http://stackoverflow.com/questions/7412548/error-gnu-stubs-32-h-no-such-file-or-directory-while-compiling-nachos-source and the following https://gcc.gnu.org/ml/gcc/2012-02/msg00314.html it may have ended up in the wrong place.

Yes have tried the one you had success with https://github.com/esp8266/esp8266-wiki/wiki/Toolchain and ran into issues


quote:
Makefiles were not working when I called make dispite the fact the MakeFile was in the same folder as the gen.misc file


Willing to give it another go though, I think this is a Hardware/Chipset (Intel/AMD) compatibility issue amongst others, I've read a ton of threads where the user has a 32bit ISO loaded on a 64bit machine tries to compile the gcc tool chain and fails users with AMD chips have less of a problem...from what I have read anyway.

So I can get this working I'll just copy what you did if possible, other than the i7 Asus machines x2 - win 8 and the multi install linux mint/debian/ubuntu I also have a Mac as well, Mountain Lion 10.8.5 2.26GHz Intel Core 2 Duo late '09 if that helps) and a few old dell boxes What OS are you using? the lubuntu vm? if so what machine is it running on? and what is the chipset? Curious to know if this is a Hardware / Software compatibility issue I'm having personally OR simple lack of knowledge re. *nix

could be a user /groups permissions thing as the user tim5 (me) is refused access to several dirs/files via the GUI so I take it I have to go to the terminal and make some adjustments....this is doing my head in lots of reading to do yet!

Cheers Tim

Post Wed Jan 14, 2015 9:05 pm 
 View user's profile Send private message
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  

I might try and make a VM image in ubuntu. I did the install in 13.10 on my old laptop.

I was able to repeat the process on a 14.10 but it needs a few tweaks which I think I sorta just do. And without familiarisation with the command line it would be quite hard.

I should have a module in the next few days and then can do up a from scratch tutorial.

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com

Post Thu Jan 15, 2015 9:22 am 
 View user's profile Send private message Send e-mail MSN Messenger
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  

I have the Toolchain up and running on a AWS EC2 instance.

If you need anything compiled I can give you the login (it would all be remote throught the terminal) but it was pretty straight forward getting that up and running.

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com

Post Thu Jan 15, 2015 11:24 am 
 View user's profile Send private message Send e-mail MSN Messenger
miles&Jules
Experienced Roboteer


Joined: 19 May 2010
Posts: 3959
Location: ipswich QLD


 Reply with quote  

http://www.linkdelight.com/P0013301-Ipega-Bluetooth-Game-Controller-Gamepad-for-Android-iOS-PC-iPad-iPhone-Samsung.html?utm_source=Linkdelight&utm_campaign=dc5d53c46e-Newsletter15_01_15&utm_medium=email&utm_term=0_27a18bceec-dc5d53c46e-48282697

would this work with it?
_________________
Miles Blow - Julie Pitts
www.mulesfilm.com.au
www.wombokforest.com.au

-Pickasso- Vivid Sportsman champion 2015

Post Fri Jan 16, 2015 1:53 am 
 View user's profile Send private message Send e-mail Visit poster's website
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  

You would need an android device and so software but it could. However a real radio would probably be easier and cheaper.

Idea is more to use a PC, tablet or phone which everyone should have.

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com

Post Fri Jan 16, 2015 8:34 am 
 View user's profile Send private message Send e-mail MSN Messenger
Tim



Joined: 30 Oct 2013
Posts: 247
Location: QLD


 Reply with quote  

@Steve Thanks heaps! will take you up on the offer

quote:
Originally posted by marto:
I have the Toolchain up and running on a AWS EC2 instance.

If you need anything compiled I can give you the login (it would all be remote throught the terminal) but it was pretty straight forward getting that up and running.

Steve


If there is any resources other than a *nix box or putty that I may need could you please make me aware of them other wise very cool.

Can PM you any relevant info you way need from my side also.

Cheers Tim Very Happy

Post Sat Jan 17, 2015 7:43 am 
 View user's profile Send private message
Tim



Joined: 30 Oct 2013
Posts: 247
Location: QLD


 Reply with quote  

Flashed the first chip Yay!.... f'n finally, now it is accepting AT commands (my batch was preloaded with the IoT firmware) that and fighting dodgy jaycar hardware is fun! so now to do something useful with it all. I cheated and used this tutorial http://www.esp8266.com/viewtopic.php?f=6&t=490 in the lubuntu VM / will post links to how to do this the easy way for anyone who is interested.

Cheers Tim Very Happy

Post Tue Jan 20, 2015 7:18 am 
 View user's profile Send private message
Tim



Joined: 30 Oct 2013
Posts: 247
Location: QLD


 Reply with quote  

For anyone interested in putting these to use for whatever, just to get started, as posted previously this link http://www.esp8266.com/viewtopic.php?f=6&t=490 is by far the easiest to follow and works! it does however lack all the fruit you would get if you built the tool chain from scratch. I used ESP Flash Download Tool to flash the chip it, Using Putty I was then able to connect to the router and get a IP address.

Problems I encounted other than previously mentioned this is just a few :-

-ESP8266 came Preloaded with IoT Demo so would not accept AT commands spent a lot of time trying to though lol

-The usb serial adapter I was using was faulty - Failed a loop back test, so I replaced it

-The logic level converter was DOA should of had 7 through hole on the PCB mine had 4 - only discovered this after careful examination with a photographers loop 5 volts were going in...Y U NO 3.3 volt other side - replaced it....but haven't needed it yet works without it.

...and sloppy dupont/jaycar cables, I was sure I had connection issues so I put this together, just some male & female header pins and a bit of vero board as the esp8266 is not breadboard friendly, and it worked first time pics below explain


All fits nice and snug...





Used a .4mm solder tip, cut the copper tracks with a stanley knife




And that's it sitting there running as an AP, Funny thing is years ago when trying to build a web server from an ethermega I was talking to some oldheads at ZTE one day about AT commands and they could not understand why any one "in this day and age" would want/need to use them....because I like to understand how things work.


Hope this helps anyone interested may save you a lot of time.


Cheers Tim Very Happy

Post Wed Jan 21, 2015 2:01 am 
 View user's profile Send private message
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  
Toolchain from Scratch

I have just installed a 14.10 64bit clean Ubuntu install and thought I would document how I go about installing the toolchain.

First, update the package lists and upgrade packages. Like most of this you will need to open the terminal and type in. This was going slow so I switched to IInets repos which came down at 1.2mb/s instead of the 100k I was getting before.

sudo apt-get update
sudo apt-get upgrade

Install dependancies

sudo apt-get install git autoconf build-essential gperf bison flex texinfo libtool libncurses5-dev wget gawk libc6-dev-amd64 python-serial libexpat-dev

Make a directory in your home folder and clone the toolchain.

cd ~
mkdir Espressif
cd Espressif
git clone -b lx106 git://github.com/jcmvbkbc/crosstool-NG.git

Build the toolchain

cd crosstool-NG
./bootstrap && ./configure --prefix=`pwd` && make && make install
./ct-ng xtensa-lx106-elf
./ct-ng build

Add the path to your bash file

echo "export PATH=$PWD/builds/xtensa-lx106-elf/bin:$PATH" >> ~/.bashrc

Install SDK

cd ~/Espressif
mkdir ESP8266_SDK
wget -O esp_iot_sdk_v0.9.5_15_01_23.zip https://github.com/esp8266/esp8266-wiki/raw/master/sdk/esp_iot_sdk_v0.9.5_15_01_23.zip
unzip esp_iot_sdk_v0.9.5_15_01_23.zip
mv esp_iot_sdk_v0.9.5 ESP8266_SDK
mv License ESP8266_SDK/
cd ESP8266_SDK/
cd esp_iot_sdk_v0.9.5/
mv * ../



Get Headers

cd ~/Espressif/ESP8266_SDK
wget -O lib/libc.a https://github.com/esp8266/esp8266-wiki/raw/master/libs/libc.a
wget -O lib/libhal.a https://github.com/esp8266/esp8266-wiki/raw/master/libs/libhal.a
wget -O include.tgz https://github.com/esp8266/esp8266-wiki/raw/master/include.tgz
tar -xvzf include.tgz

Get ESP Tool

cd ~/Espressif
wget -O esptool_0.0.2-1_i386.deb https://github.com/esp8266/esp8266-wiki/raw/master/deb/esptool_0.0.2-1_i386.deb
sudo dpkg -i esptool_0.0.2-1_i386.deb

Get ESP upload tool

cd ~/Espressif
git clone https://github.com/themadinventor/esptool esptool-py
ln -s $PWD/esptool-py/esptool.py crosstool-NG/builds/xtensa-lx106-elf/bin/

Check you can build stuff.

cd ~/Espressif
git clone https://github.com/esp8266/source-code-examples.git
cd source-code-examples/blinky

You will need to change all the references to /opt to /home/<your username> in the makefile

gedit Makefile

Replace the two entries of /opt then you should be good to go

make

Modify from here....

Enjoy

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com


Last edited by marto on Mon Jan 26, 2015 8:18 am; edited 2 times in total

Post Mon Jan 26, 2015 7:26 am 
 View user's profile Send private message Send e-mail MSN Messenger
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  

I should also add that I installed cutecom to allow me to communicate over serial.

sudo apt-get install cutecom

and you also need to add yourself to the DIALOUT group other wise you need root access to do anything on the USB serial lines.

sudo addgroup <your username> dialout

you will need to login/out to update the permissions. Or I just reboot.

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com

Post Mon Jan 26, 2015 8:11 am 
 View user's profile Send private message Send e-mail MSN Messenger
marto
Experienced Roboteer


Joined: 08 Jul 2004
Posts: 5443
Location: Brisbane, QLD


 Reply with quote  

I had to tweak a few minor things on the tutorial but now all appears to be working fine. I hadn't copied my unzipped SDK files correctly which messed up a few things if anyone could confirm it works that would be great.

This has only been tried on 64bit 14.10 but should work on Mint and Debian based distros.

Steve
_________________
Steven Martin
Twisted Constructions
http://www.botbitz.com

Post Mon Jan 26, 2015 8:27 am 
 View user's profile Send private message Send e-mail MSN Messenger
Tim



Joined: 30 Oct 2013
Posts: 247
Location: QLD


 Reply with quote  

Hey Steve,

Upgraded Ubuntu 13.0 saucy salamander to ubuntu 14 but 13 was a 32bit install so that's what it upgraded too.
The Tool Chain build went perfectly, I have ran the make file for blinky it pumped out the bins.

Had a go at flashing the bins for blinky with no luck it (never used cutecom before) send the file but the RX & TX leds on the serial adapter didn't flash, will double check my wiring/port setting later today I'm sure that's all it is, otherwise thanks so much for an easy to follow tutorial that works Very Happy

Where is the like button?

Cheers Tim Very Happy

Post Tue Jan 27, 2015 2:24 am 
 View user's profile Send private message
  Display posts from previous:      

Forum Jump:
Jump to:  

Post new topic   Reply to topic
Page 3 of 5

Goto page Previous  1, 2, 3, 4, 5  Next

Forum Rules:
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

 

Last Thread | Next Thread  >
Powered by phpBB: © 2001 phpBB Group
millenniumFalcon Template By Vereor.