Category Archives: ESP8266

#ESP8266 #VSCP Development Intro – part 1

Serial port

Connect the USB cable to the board.  You will get a new CDC serial port. You can check which one you get with

ls /dev/tty*

Normally you get /dev/ttyUSB0 or /dev/ttyUSB1 or the like. To make them usable for you you should add yourself to the dialout group

addgroup user dialout

where “user” is your username. You can also do this manually in the /etc/group file or

chmod a+rw /dev/ttyUSB0

if you like brute force.

Loading code to the ESP8266

The ESP8266 CPU can be booted in three different ways:

  • Flash Mode: default booting mode. Firmware is read and executed from the flash memory. Pins need to be set to: GPIO15=0, GPIO0=0, GPIO2=1
  • UART Mode: used to program our board (through a Serial-to-Usb adapter). Pins need to be set to:  GPIO15=0, GPIO0=1, GPIO2=1
  • SDIO Mode: loads firmware from an SDIO card? Pins need to be set to:  GPIO15=1, GPIO0=0/1, GPIO2=0/1

The boot process is described here.

Switching from a mode to another requires to reset the module while the pin states listed is set.

With the nodemcu board and esptool flash uploader all this is handle automatically but if you have another board you must handle this yourself.

esp-open-sdk

You find it here.

Fetch it

sudo git clone https://github.com/pfalcon/esp-open-sdk.git

cd esp-open-sdk

Install it

apt-get install make unrar autoconf automake libtool libtool-bin gcc g++ gperf flex bison texinfo gawk ncurses-dev libexpat-dev python sed

git clone --recursive https://github.com/pfalcon/esp-open-sdk

cd esp-open-sdk/

make
Error when building?  See this post
This builds the standalone version of the SDK (Non FreeRTOS)
You should add the bin directory to he path
echo 'PATH=$PATH:~/development/esp8266/esp-open-sdk/xtensa-lx106-elf/bin' >> ~/.profile

echo 'PATH=$PATH:~/development/esp8266/esp-open-sdk/esptool' >> ~/.profile

PATH=$PATH:~/development/esp8266/esp-open-sdk/xtensa-lx106-elf/bin
PATH=$PATH:~/development/esp8266/esp-open-sdk/esptool

I have installed the toolchain in

 ~/development/esp8266/ 

so change paths above for your installation folders.

Update it (when updates are available)

make clean
git pull
git submodule update

Firmware upload tool

You need the esptool.py to upliad firmware to the module, you find it here
Install with
pip install esptool

First code (blinky)

You find it here

cd ~/development/esp8266/esp-open-sdk/examples/blinky

Type

make

to build it. Remember that the paths above must have been set. You may get some warnings. No problem.

For your information. If you build from source code should be loaded like this:

  • bin/0x00000.bin to 0x00000
  • bin/0x10000.bin to 0x10000

That is just what we do here. Upload to your module with

esptool.py --port /dev/ttyUSB1 write_flash 0x00000 blinky-0x00000.bin 0x10000 blinky-0x10000.bin

No need to press any buttons during flashing. It is handled automatically by the USB DTR circuitry.

Now we are ready to do some real work for our VSCP system with the ESP8266.  If you rather prefer Arduino this howto may be the one you should go for instead of this one. Life is much simpler in the Arduino world. But the degrees of freedom is better if you do it all by yourself. The penalty for freedom is more problems of course. As always.

Another intro is here http://www.electrodragon.com/w/ESP8266_Open_SDK
esp8266 wiki is here.

Part 2 will follow.

Problems with #esp-open-sdk build on Debian jessie #ESP8266 solved

I have had problems lately to build the esp-open-sdk on my main Debian machine with Jessie. Very annoying of course as I needed it but I haven’t had time to investigate the problem until today. I post the solution here i case it is useful for someone else.

The symptoms is that the build stops quite early in the build process spitting out something like this

[INFO ] =================================================================
[INFO ] Retrieving needed toolchain components’ tarballs
[INFO ] Retrieving needed toolchain components’ tarballs: done in 208.37s (at 03:41)
[INFO ] =================================================================
[INFO ] Extracting and patching toolchain components
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step ‘Extracting and patching toolchain components’
[ERROR] >> called in step ‘(top-level)’
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR] >> called from: CT_Extract[scripts/functions@982]
[ERROR] >> called from: do_binutils_extract[scripts/build/binutils/binutils.sh@38]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@615]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: ‘build.log’
[ERROR] >> There is a list of known issues, some with workarounds, in:
[ERROR] >> ‘share/doc/crosstool-ng/crosstool-ng-1.22.0-60-g37b07f6/B – Known issues.txt’
[ERROR]
[ERROR] (elapsed: 4:12.94)
[04:15] / ct-ng:152: recipe for target ‘build’ failed
make[2]: *** [build] Error 2
make[2]: Leaving directory ‘/home/esp/esp-open-sdk/crosstool-NG’
../Makefile:132: recipe for target ‘_toolchain’ failed
make[1]: *** [_toolchain] Error 2
make[1]: Leaving directory ‘/home/esp/esp-open-sdk/crosstool-NG’
Makefile:128: recipe for target ‘/home/esp/esp-open-sdk/xtensa-lx106-elf/bin/xtensa-lx106-elf-gcc’ failed
make: *** [/home/esp/esp-open-sdk/xtensa-lx106-elf/bin/xtensa-lx106-elf-gcc] Error 2

Investigating the crosstools-NG/build.log (less crosstool-NG/build.log)

[DEBUG] ==> Executing: ‘touch’ ‘/home/esp/esp-open-sdk/crosstool-NG/.build/sr
c/.ncurses-6.0.patched’
[DEBUG] ==> Executing: ‘rm’ ‘-f’ ‘/home/esp/esp-open-sdk/crosstool-NG/.build/
src/.ncurses-6.0.patching’
[DEBUG] ==> Executing: ‘touch’ ‘/home/esp/esp-open-sdk/crosstool-NG/.build/sr
c/.binutils-2.25.1.extracting’
[DEBUG] Entering ‘/home/esp/esp-open-sdk/crosstool-NG/.build/src’
[EXTRA] Extracting ‘binutils-2.25.1’
[DEBUG] ==> Executing: ‘mkdir’ ‘-p’ ‘binutils-2.25.1’
[DEBUG] ==> Executing: ‘tar’ ‘–strip-components=1’ ‘-C’ ‘binutils-2.25.1’ ‘-xv’ ‘-f’ ‘-‘
[FILE ] tar: This does not look like a tar archive
[FILE ] tar: Skipping to next header
[FILE ] tar: Exiting with failure status due to previous errors
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step ‘Extracting and patching toolchain components’
[ERROR] >> called in step ‘(top-level)’
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR] >> called from: CT_Extract[scripts/functions@982]
[ERROR] >> called from: do_binutils_extract[scripts/build/binutils/binutils.sh@38]
[ERROR] >> called from: main[scripts/crosstool-NG.sh@615]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: ‘build.log’
[ERROR] >> There is a list of known issues, some with workarounds, in:
[ERROR] >> ‘share/doc/crosstool-ng/crosstool-ng-1.22.0-60-g37b07f6/B – Known issues.txt’
[ERROR]
[ERROR] (elapsed: 4:12.94)

The line

[DEBUG] ==> Executing: ‘tar’ ‘–strip-components=1’ ‘-C’ ‘binutils-2.25.1’ ‘-xv’ ‘-f’ ‘-‘
[FILE ] tar: This does not look like a tar archive

says it is a problem with a tarball and testing the binutils tarball under crosstool-NG/.build/tarballs shows it really is a problem with the tarball.

So after some discussions here is finally found a solution to the problem.

  • remove the partly extracted binutils – rm -rf crosstool-NG/.build/src/binutils*
  • remove flags  – rm crosstool-NG/.build/src/ .binutils-*
  • remove the bad tarball  – rm crosstool-NG/.build/tarballs/binutils*
  • Download binutils
  • copy this tarball from the gnu link to crosstool-NG/.build/tarballs
  • Continue with the build – make

This will make things build.  At least it did for me.

if the version of binutils is something else in your case you have other versions here.  Select the tar.gz version