错误将NodeMCU闪烁到ESP8266 [英] Errors flashing NodeMCU to ESP8266

查看:236
本文介绍了错误将NodeMCU闪烁到ESP8266的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

尝试刷新最新的dev固件时,我遇到了一些麻烦。我用cli中的大量复制/粘贴示例编辑了问题,并阐明了我到目前为止所采取的步骤。这是我尝试做的事情:




  • 我从自定义构建服务中下载了1.4.0的主版本和固件版本。

    li>
  • 我尝试使用以下命令刷新1.4.0主版本:

      python esptool.py --port / dev / ttyUSB0 write_flash -fm = dio -fs = 32m 0x00000〜/ git / nodemcu- 
    固件/bin/nodemcu_integer_1.4.0_master_20160531.bin
    esptool.py v1。 0.2-dev
    正在连接...
    正在运行Cesanta闪存存根...
    闪存参数设置为0x0240
    编写405504 @ 0x0 ... 405504(100%)
    在35.2秒(92.2 kbit / s)的0x0时间内写入405504字节...
    正在离开...


  • 这似乎成功了,因为我可以连接到devkit

      n?$B 
    4 * 4 * B%,C C
    NodeMCU自定义构建,由frightanic.com
    分支:master
    commit:c8037568571edb5c568c2f8231e4f8ce0683b883
    SSL:错误的
    模块:file,gpio,i2c ,net,节点,rtcfifo,rtcmem,rtctime,tmr,uart,wifi,ws2812
    建立在:2016-06-01 02:58
    由Lua 5.1.4在SDK 1.4.0 $提供动力b $ b lua:无法打开init.lua
    >


  • 我下载了espressif sdk的v1.5.1 nonos以获得我拥有的esp_init_data_default.bin这样做是因为devkit正在运行0.9.6


  • 我尝试使用以下命令刷新固件的1.4.0开发版:

      python esptool.py --port / dev / ttyUSB0 write_flash -fm = dio -fs = 32m 0x00000〜/ git / nodemcu-firmware / bin /nodemcu_integer_1.4.0_dev_20160531.bin 0x3fc000〜/ git / nodemcu-firmware / bin / esp_init_data_default.bin 
    esptool.py v1.0.2-dev
    正在连接...
    正在运行Cesanta Flasher存根。 ..
    Flash参数设置为0x0240
    写入401408 @ 0x0 ... 401408(100%)
    在34.8秒(92.3 kbit / s)中在0x0写入401408字节...
    写4096 @ 0x3fc000 ... 4096(100%)
    在0.4秒(90.0 kbit / s)中以0x3fc000写入4096字节...
    离开...


  • 这似乎失败了,因为当我尝试连接到devkit时,我什么也看不到。我已尝试连接每个波特率设置,但它似乎根本没有改善乱码的问题。

      rll | l。 || l | b |rbb nnlnn  bplrlrlp?n?lbn。| l?b nnllllnn 
    lnr n

    b $`p n

    r $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
    b nl
    nn
    lp n

    r $ lbn。|b nn ll`




fi的主版本rmware工作得很好,但是正如我所说的,它缺少我想使用的wifi和ws2812模块的一些功能。固件的开发版本确实会闪烁,但是当我尝试使用屏幕连接到开发套件时,我得到的只是乱七八糟的东西,并且从未出现Lua提示。我现在要放弃了,我不知道下一步该怎么做,所以有人可以指导我吗?



感谢您的帮助。

解决方案

事实证明,屏幕存在一个错误,通过与固件版本1.5及更高版本上的devkit通信来实现。要解决此问题,您可以在Linux上使用腻子(如果在ubuntu上可以从apt-get获得),也可以将固件降级到1.4



请参见以下答案有关详细信息的超级用户:
https://superuser.com/questions/810937/how-can-i-set-the-parity-bits-when-using-screen-to-access-a-serial-port



Ps我只在armhf编译的二进制文件上确认了此错误。 x86二进制文件可能工作得很好,因为我没有对其进行测试,尽管我链接的关于SuperUser的Q& A似乎暗示x86的屏幕也会出现问题。


I've been having a bit of a rough time trying to flash the latest dev firmware. I've edited the question with a bunch of copy/paste examples from my cli and to clarify the steps I've taken so far. Here's what I've tried doing:

  • I downloaded the 1.4.0 master and dev versions of firmware from the custom build service.
  • I tried to flash the 1.4.0 master version with this command:

    python esptool.py --port /dev/ttyUSB0 write_flash -fm=dio -fs=32m 0x00000 ~/git/nodemcu-
    firmware/bin/nodemcu_integer_1.4.0_master_20160531.bin 
    esptool.py v1.0.2-dev
    Connecting...
    Running Cesanta flasher stub...
    Flash params set to 0x0240
    Writing 405504 @ 0x0... 405504 (100 %)
    Wrote 405504 bytes at 0x0 in 35.2 seconds (92.2 kbit/s)...
    Leaving...
    

  • This appears to succeed because I can connect to the devkit

    n?$B�
          ��4"*���4"*��B%,��� C�
    NodeMCU custom build by frightanic.com
            branch: master
            commit: c8037568571edb5c568c2f8231e4f8ce0683b883
            SSL: false
            modules: file,gpio,i2c,net,node,rtcfifo,rtcmem,rtctime,tmr,uart,wifi,ws2812
     build  built on: 2016-06-01 02:58
     powered by Lua 5.1.4 on SDK 1.4.0
    lua: cannot open init.lua
    > 
    

  • I downloaded v1.5.1 nonos of the espressif sdk to get the esp_init_data_default.bin I had to do this because the devkit was running 0.9.6

  • I tried to flash the 1.4.0 dev version of the firmware with this command:

    python esptool.py --port /dev/ttyUSB0 write_flash -fm=dio -fs=32m 0x00000 ~/git/nodemcu-firmware/bin/nodemcu_integer_1.4.0_dev_20160531.bin 0x3fc000 ~/git/nodemcu-firmware/bin/esp_init_data_default.bin 
    esptool.py v1.0.2-dev
    Connecting...
    Running Cesanta flasher stub...
    Flash params set to 0x0240
    Writing 401408 @ 0x0... 401408 (100 %)
    Wrote 401408 bytes at 0x0 in 34.8 seconds (92.3 kbit/s)...
    Writing 4096 @ 0x3fc000... 4096 (100 %)
    Wrote 4096 bytes at 0x3fc000 in 0.4 seconds (90.0 kbit/s)...
    Leaving...
    

  • This appears to fail because when I try to connect to the devkit I get nothing but gibberish. I have tried to connect with EVERY baud setting and it doesn't appear to improve the gibberish at all.

    rll|l�|l�b|�rbb�nnlnn��bplrlrlp�n�lbn�|l�b�nn�ll`nn
                                                 lnr�n
    
                                                       b��`p�n�
    
                                                                  r���bn�|llb�nn�l`nnl�l`nr�n
    
                                                                                                 ��l``�n
    
    
                                                                                                         ��b�nl�
                                                                                                                ��nn�
                                                                                                                     lp�n�
    
      r���lbn�|b�nn�ll`
    

The master version of the firmware works very well, but as I said its missing a couple things from wifi and ws2812 modules that I want to use. The dev version of the firmware does flash, but when I try to use screen to connect to the devkit all I get is gibberish and a Lua prompt never shows up. I'm giving up now I don't know what to try next so can somebody please guide me?

Thanks for any help.

解决方案

It turns out that there is a bug with screen that keeps it from communicating to the devkit on firmware versions 1.5 and above. To work around this issue you can either use putty for linux (available from apt-get if you're on ubuntu) or downgrade your firmware to 1.4

See this answer on SuperUser for some detailed info: https://superuser.com/questions/810937/how-can-i-set-the-parity-bits-when-using-screen-to-access-a-serial-port

P.s. I have only confirmed this bug on armhf compiled binaries. It is possible that the x86 binaries work just fine as I have not tested it, though the Q&A on SuperUser that I linked seems to imply that screen on x86 will have problems too.

这篇关于错误将NodeMCU闪烁到ESP8266的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆