ESP8266 page

From Eric

(Difference between revisions)
Jump to: navigation, search
m
m
Line 67: Line 67:
*[https://github.com/igrr/esptool-ck/|esptool-ck] in C
*[https://github.com/igrr/esptool-ck/|esptool-ck] in C
*[https://github.com/DonKinzer/esp_tool/|esptool-ck] in C++
*[https://github.com/DonKinzer/esp_tool/|esptool-ck] in C++
 +
 +
I use Esptool.
 +
 +
==Restoring the AT firmware==
==Restoring the AT firmware==
Line 74: Line 78:
The NodeMcu firmware can be found [here https://github.com/nodemcu/nodemcu-firmware].  
The NodeMcu firmware can be found [here https://github.com/nodemcu/nodemcu-firmware].  
-
To download the firlware, do  
+
To download the firmware, do  
   wget https://github.com/nodemcu/nodemcu-firmware/raw/master/0.9.2/512k-flash/nodemcu_512k.bin
   wget https://github.com/nodemcu/nodemcu-firmware/raw/master/0.9.2/512k-flash/nodemcu_512k.bin
and then flash it to the module using
and then flash it to the module using

Revision as of 20:04, 27 April 2016

Contents

The chip

The ESP8266 is a SoC designed by Espressif.

Someone managed to decap the chip (well, a similar one) and show its internal layout (source here):

Esp8266 internals.jpg

The MCU is a Tensilica lx106 processor IP.

The board

I use the following board.

Esp8266 board.jpg


Connecting the ESP8266 board to a PC

The main things to know:

  • VCC is 3.3V (NOT 5V).
  • Input pins are NOT 5V tolerant.
  • The power supply shall deliver at least 500mA.
  • Pin CH_PD must be pulled-up to 3.3V
  • Pin RST must be pulled-up to 3.3V.

The ESP8266 board pin-out is the following:

Esp8266 pinout.jpg


Using AT commands

Every command must end with a CR/LF sequence. On minicom, this can be obtained using CTRL-M followed by CTRL-J. The AT commands are fully described in Espressif manual "[|ESP8266 AT Instruction Set]".


Reprogramming the ESP8266

The ESP8266 can be reprogrammed. To do so, you can either go the easy way using Arduino or the hard way installing a cross-compiler, a firmware uploading tool, etc.

Using the Arduino environment

(To be completed.)

Building and installing the cross-compiler and sdk

I have followed the indications given here. A lot of information is also provided by Espressif on their BBS). In particular, a lot of documents are available on this page.

On a fresh MINT installation, here are the commands I had to type to get a complete development environment:

 git clone --recursive https://github.com/pfalcon/esp-open-sdk.git
 cd esp-open-sdk/
 sudo apt-get install autoconf
 sudo apt-get install gperf
 sudo apt-get install texinfo
 sudo apt-get install libtool
 sudo apt-get install automake
 sudo apt-get install ncurses-dev
 sudo apt-get install g++
 sudo apt-get install expat
 make STANDALONE=y


A lot of very interesting/important information about programming the ESP8266 are given here.


Uploading the software to the chip

The chip can be placed in the flash programming mode by pulling down GPIO0 during reset (pull down GPIO0, pull down RESET, pull-up RESET).

A flash download tool is provided by Espressif here. Other tools:

I use Esptool.


Restoring the AT firmware

The AT firmware can be found [4] at Espressif.

= Using NodeMcu

The NodeMcu firmware can be found [here https://github.com/nodemcu/nodemcu-firmware]. To download the firmware, do

 wget https://github.com/nodemcu/nodemcu-firmware/raw/master/0.9.2/512k-flash/nodemcu_512k.bin

and then flash it to the module using

 python esptool.py --port /dev/tty.usbserial-ABC123456 write_flash 0x000000 nodemcu_512k.bin


Using MQTT

The MQTT standard is available here. Other information can be found on the dedicated web site mqtt.org.

Setting up the MQTT broker on the Raspberry Pi

Just type:

 sudo apt-get install mosquitto mosquitto-clients python-mosquitto

Then you can retrieve all topics from the mosquitto test broker:

 mosquitto_sub -h test.mosquitto.org -t "#" –v

To use you own broker, type

 mosquitto

Then you can publish your own data:

 mosquitto_pub -h localhost -t "eric" -m "10"

and see (in another terminal) that it has been correctly handled by the broker:

 mosquitto_sub -h localhost -t "#" -v

returns:

 eric 10

You can also use the following page: http://test.mosquitto.org/gauge/ When you publish a new value of topic "temp/random", it is displayed on a graphical gauge.

Setting up the MQTT client on windows

I use [MQTT.fx].

Compiling and installing the MQTQ client on the ESP8266

To be completed.

Compiling the MQTT client on the Raspberry Pi

The simplest way uses [Paho] and Python:

 sudo pip install paho-mqtt

The python code (taken from I-don't-remember-where) connect to IBM test server :

 host="messagesight.demos.ibm.com"
 port=1883
 
 def on_connect(pahoClient, obj, rc):
 # Once connected, publish message
 	print "Connected Code = %d"%(rc)
 	client.publish("eric/test", "Hello World", 0)
 
 
 def on_log(pahoClient, obj, level, string):
 	print string
 
 def on_publish(pahoClient, packet, mid):
 # Once published, disconnect
 	print "Published"
 	pahoClient.disconnect()
 
 def on_disconnect(pahoClient, obj, rc):
 	print "Disconnected"
 
 # Create a client instance
 client=paho.Client()
 
 # Register callbacks
 client.on_connect = on_connect
 client.on_log = on_log
 client.on_publish = on_publish
 client.on_disconnnect = on_disconnect
 
 #connect
 x = client.connect(host, port, 60)
 
 client.loop_forever()
 

Let's try to compile paho on the Raspberry:

 git clone https://git.eclipse.org/r/paho/org.eclipse.paho.mqtt.embedded-c
 cd org.eclipse.paho.mqtt.embedded-c/
 make

Well, it should work but it doesn't:

 mkdir -p build/output/samples
 mkdir -p build/output/test
 cc -o build/output/samples/pub0sub1 MQTTPacket/src/../samples/pub0sub1.c -lpaho-embed-mqtt3c -I MQTTPacket/src  -L build/output
 /tmp/ccV9SzgN.o: In function `main':
 pub0sub1.c:(.text+0x148): undefined reference to `transport_open'
 pub0sub1.c:(.text+0x1cc): undefined reference to `transport_sendPacketBuffer'
 pub0sub1.c:(.text+0x29c): undefined reference to `transport_sendPacketBuffer'
 pub0sub1.c:(.text+0x414): undefined reference to `transport_sendPacketBuffer'
 pub0sub1.c:(.text+0x458): undefined reference to `transport_sendPacketBuffer'
 pub0sub1.c:(.text+0x474): undefined reference to `transport_close'
 pub0sub1.c:(.text+0x4a8): undefined reference to `transport_getdata'
 collect2: ld returned 1 exit status
 Makefile:106: recipe for target 'build/output/samples/pub0sub1' failed
 make: *** [build/output/samples/pub0sub1] Error 1

The makefile is erroneous and must be corrected as follows (see here):

 ${SYNC_SAMPLES}: ${blddir}/samples/%: ${srcdir}/../samples/%.c ${srcdir}/../samples/transport.o
 	${CC} -o $@ $^ -l${MQTT_EMBED_LIB_C} ${FLAGS_EXE}


And now it compiles smoothly. To run the samples, the LD_LIBRARY_PATH shall include "<wherever>/org.eclipse.paho.mqtt.embedded-c/build/output".

Other sources of information

Personal tools