ESP8266 Community Forum

- Wed May 11, 2016 2:05 pm #47308

And now it's in the release, together with your other request (tcp port timeouts)

- Sat Jun 04, 2016 2:45 am #48548 New release 14

Major changes: add access point mode.

Changelog:

- Fix issue where esp wouldn't start with default-config.
It appears some fields in the config struct aren't properly defaulted to 0.

- Add recipes in Makefile to backup current config, wipe it or restore it:
make backup-config
make restore-config
make wipe-config
This needs a programmer, it's done using esptool.

- Add gpio trigger for WLAN association
This triggers and I/O whenever
* client mode is connected and IP is obtained
* access point mode is active and a client connects
When the connection is dropped due to whatever reason, the trigger is reset.

- Drop major/minor version scheme. It's obsolete with the new (boot) configuration using access point mode.

- Add flexible end of line handling.
Any combination of \n \r \r\n and \n\r are now accepted as end of line delimiter. A line without any of them is now also accepted, as long as the command is sent in exactly one tcp segment.

- Add access point mode

* use the wac (wlan-accesspoint-config) command to select ssid, passwd, channel
* write the config using cw
* then use the wm (wlan-mode) command to select "ap" mode.
* login over the access point ssid and write the config (cw) to make
* the config permanent or issue a reset/power-cycle to return to client mode
* or use wm client to return to client mode
* use wcc (wlan-client-config) to select ssid, passwd and then issue cw to write to flash.

NOTE: for access point use a password longer than 7, it's required by the SDK.

- New "scratch" configuration mode
At startup the software will now try various schemes to obtain a connection so you can configure it.

1) if the device is configured to start in client mode, try the ssid/passwd stored in flash.
1a) if none is stored (flash is pristine/wiped or ssid/passwd invalid), use "esp" for ssid and "espespesp" for passwd.
1b) if the device cannot connect to the configured/default ssid for more then 30 seconds, change to access point mode -> 2)
2) if the device is configured to start in access point mode (or put in access point mode because of step 1b)), try the ssid/passwd stored in flash.
2a) if none is stored (flash is pristine/wiped or ssid/passwd invalid), use "esp" for ssid and "espespesp" for passwd.

That way you should always be able to connect to the esp.

https://github.com/eriksl/esp8266-unive ... ses/tag/14

- Mon Jun 06, 2016 12:33 pm #48672 Uao, v14 is a very great enhancement, thanks! Having the AP available makes this firmware more flexible Just a notice, I'm trying some basic UART transfer at 1Mbit (between minicom and a netcat client) and I see some messages appear along with messages coming from the TCP bridge. Is the debug UART routed to the UART0 too? I think the UART should stay mute until a TCP bridge connection otherwise these messages can be erratically read by example from a microcontroller connected to the UART port of the ESP8266. Here are example of the output on UART after a reset command:

Code: Select allbcn 0
del if1
usl
��sleep disable
mode : sta(5c:cf:7f:06:fa:4d)
add if0
* set wlan mode to ap, ssid="esp", passwd="espespesp", channel=13

del if0
usl
mode : softAP(5e:cf:7f:06:fa:4d)
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
bcn 0
del if1
usl
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
add 1
aid 1
station: 00:26:4d:1b:4d:2a join, AID = 1
chg_A3:-180                                                                     
chg_A3:0                                                                       
chg_A3:-180

- Wed Jun 08, 2016 9:58 am #48779 Did you unset the print-debug flag? As in:

Code: Select allu print-debug
cw