ESP8266 Community Forum

- Sun Jun 26, 2016 3:43 am #49791 Hello everyone, i have a nodemcu 0.9 dev board that came to me with AT firmware, i was sucess to change the firmware from AT to nodemcu 0.9.5. At this point everything works almost perfect (with all the well known issues that the platform have) but a couple of days ago i was wondering how to upgrade my firmware to the recent version and see if many of the bugs present in the 0.9.5 version could disapear. I follow the guide from marcelstoer through docker framework (thank you very much for all the effort) https://hub.docker.com/r/marcelstoer/nodemcu-build/ again at this point a can build a sucessful bin archive to flash via esptool on a Macbook, but the problems just begin here. When i flash the firmware no matter if i define flash size (-fs), baud rate (-b) in esptool, and define -ff, always i get the same error when the module restart:

Code: Select all ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 27528, room 16
tail 8
chksum 0x6d
load 0x3ffe8000, len 2184, room 0
tail 8
chksum 0xca
load 0x3ffe8888, len 8, room 0
tail 8
chksum 0x91
csum 0x91
don't use rtc mem data
;l???

Just when i edit the baud rate from 115200 to 9600 in the user_config.h file in the app/include folder from the firmware

from this:

Code: Select all#define BIT_RATE_DEFAULT BIT_RATE_115200

to this

Code: Select all#define BIT_RATE_DEFAULT BIT_RATE_9600

the error message gone every restart , but now

even flashing the esp_init_data_default.bin to the adress 0x7c000 or 0x3fc000 from the esp_iot_sdk_v1.4.0_15_09_18 SDK, and no error message when the module restart, all my lua scripts have a bad behaviour that ran perfect on the past 0.9.5. firmware.

I´m stuck at this point.

I really think that someone with the good knowledge must write a ultimate guide to sucessful flash of a new (master or dev) firmware into the esp (1, 2, 3.......12 or 12E) that way more people arround the globes can give something, even small, the the maker, hack and developer comunity.

Thanks in advance

- Sun Jun 26, 2016 7:08 am #49800 Well, there are instructions for you to follow in the NodeMCU docs at http://nodemcu.readthedocs.io/en/dev/en ... x-firmware. However, I suspect you already found those.
Also, as per http://nodemcu.readthedocs.io/en/dev/en/modules/uart/ there's no need to change baud rate as NodeMCU 1.5.1 has auto-baud built in. If the device panics and resets at any time, errors will be written to the serial interface at 115'200 bps. That's the reason you don't see any errors if you lower the transfer rate to 9'600.

https://frightanic.com/
https://nodemcu-build.com/
https://github.com/marcelstoer/nodemcu-pyflasher

- Sun Jun 26, 2016 3:44 pm #49827 Thank for your quick response, so then what i´m doing wrong? i´m building the frimware wrong way? i´m flashing the firmware wrong too?

I need a solid base to make that the nodemcu board work properly, i followed many online tutorials and guides but seems all fall in the same error.

Or maybe i must stay in the 2015 0.9.6 frimware?

I really love the nodemcu firmware and want to keep working with it for my future projects.

Thanks again

- Sun Jun 26, 2016 3:59 pm #49831

what i´m doing wrong? i´m building the frimware wrong way? i´m flashing the firmware wrong too?

We don't have enough information to tell. Let's establish a baseline by doing the following:

- Build a firmware using the NodeMCU custom firmware builder: http://nodemcu.readthedocs.io/en/dev/en/build/
- Flash with esptool as per http://nodemcu.readthedocs.io/en/dev/en/flash/#esptool and ignore the esp_init_data_default.bin for now. "-fm dio -fs 32m" should be fine for NodeMCU devkit 0.9 as it's got an ESP-12 with 4MB flash.
- Connect with ESPlorer (115'200 baud) and report what you see at the prompt.

Or maybe i must stay in the 2015 0.9.6 frimware?

Oh no, definitely not. It's no longer maintained and contains lots of bugs.

https://frightanic.com/
https://nodemcu-build.com/
https://github.com/marcelstoer/nodemcu-pyflasher