ESP8266 Community Forum

- Sat May 16, 2015 12:39 pm #17576 Yeah, those are the first thing I see after a reset. I'm using a Prolific 2303 usb to serial chip, I'm not entirely sure if it supports 74880. I'll look into it and try with a FTDI chip.
Do you have any advice for serial-usb adapters with 74880 support?

These are the modules I'm building with:

Code: Select all#define LUA_USE_MODULES_NODE
#define LUA_USE_MODULES_FILE
#define LUA_USE_MODULES_GPIO
#define LUA_USE_MODULES_WIFI
#define LUA_USE_MODULES_NET
//#define LUA_USE_MODULES_PWM
//#define LUA_USE_MODULES_I2C
//#define LUA_USE_MODULES_SPI
#define LUA_USE_MODULES_TMR
#define LUA_USE_MODULES_ADC
#define LUA_USE_MODULES_UART
//#define LUA_USE_MODULES_OW
//#define LUA_USE_MODULES_BIT
//#define LUA_USE_MODULES_MQTT
//#define LUA_USE_MODULES_COAP
//#define LUA_USE_MODULES_U8G
//#define LUA_USE_MODULES_WS2812
#define LUA_USE_MODULES_CJSON


- Sat May 16, 2015 1:28 pm #17578 The linux driver for that chip contains the following note:

If unsupported baud rates are set directly, the PL2303 seems to
353 * use 9600 baud.

So it may be the case for you. Some chars in your example output seems o match between 9600 and 74880 baud.

No, I can't recommend one. A lot of people seem to use FTDI based boards, a few had problems
with them.

Get your modules here:

https://www.banggood.com/custlink/KvGGhGF4wG

- Mon Sep 12, 2016 10:07 pm #54993 Same exact problem here.
ESP8266 esp-01 (black), also esp-03

esp-open-sdk latest commit 07/12/2016
NodeMCU 1.5.4.1
Fedora 24, gcc-6.1.1

It does work with NodeMCU 0.9.6 compiled in a while back.

Have you found what the problem was and, more importantly, a solution?

- Thu Sep 15, 2016 6:04 pm #55192 SP-12E Devkit V2 had .9 firmware wanted to upgrade so I found directions at https://nodemcu.readthedocs.io/en/master/en/flash/ :

My issue is the directions I found https://nodemcu.readthedocs.io/en/master/en/flash/ told me to download esp_init_data_default.bin and replace the old one, did that, but they didn't say how to setup the Config:
On the first line was INTERNAL://NODEMCU @ 0x00000 they said the esp_init_data_default.bin "Init data goes to 0x3fc000 on an ESP-12E with 4 MByte flash" so I set INTERNAL://NODEMCU @ 0x3fc000 and C:\ESP8266\nodemcu-master-7-modules-2016-09-15-22-12-23-integer.bin @ 0x00000 and clicked Flash, the progress bar moved a little and stopped. So I moved INTERNAL://NODEMCU @ 0x3fc000 to AFTER C:\ESP8266\nodemcu-master-7-modules-2016-09-15-22-12-23-integer.bin @ 0x00000 and X'ed the boxes in front of each then clicked Flash this time the bar moved all the way across but again it never ended, the burning application just sat doing nothing. When I hit the hard reset I get:

load 0x40100000, len 23988, room 16
tail 4
chksum 0x0f
load 0x3ffe8000, len 2180, room 4
tail 0
chksum 0xc9
load 0x3ffe8884, len 8, room 8
tail 0
chksum 0x62
csum 0x62
rf_cal[0] !=0x05,is 0x00

ets Jan 8 2013,rst cause:2, boot mode:(3,6)

on Putty at 74880
My cp2101 version of the NODEMCU just keeps resetting, actually caused Windows 10 to crash, it was asked to leave the building after that.

see this post:
viewtopic.php?f=23&t=10471&start=12#p55196