MycontrollerDevice OTA challenges

  • Hi again. I am trying to make the magic OTA firmware update work with the setup I have.

    I have a ESP8266 with 4M flash and pubsubclient set to 512. I have defined a new version and a new type to the node, and uploaded the new bin-file to mycontroller.

    The resource log is then filled with firmware requests and responses and then after a while the device reboots, but with the same firmware as it started with.

    This is the serial monitor on the device while rebooting....

    <here is stuff that indicates the device is in its normal loop>
    MC[I]: Firmware update success...
    MC[I]: Rebooting...
     ets Jan  8 2013,rst cause:2, boot mode:(3,7)
    load 0x4010f000, len 1384, room 16
    tail 8
    chksum 0x2d
    csum 0x2d
    MC[I]: Booting ESP8266 device...
    MC[I]: WIFI not connected, trying connection...
    MC[I]: Connecting to WiFi with ssid[1421530] and with password...........OK
    MC[I]: WiFi BSSID:[00:02:61:A8:32:58], RSSI:[-69 dBm, 62 ], IP:[], StatusCode:[3]
    MC[I]: Configuration(NodeEUI:[ESP_2D5A26], Mqtt{mDNS-status:[0], Server:[], Port:[1883], FeedId:[esp], User:[]})
    MC[I]: MQTT settings(Broker:[], Port:[1883])
    MC[I]: MQTT authenticating as anonymous
    MC[I]: MQTT connection failed, rc=-4
    MC[I]: Initialization done...
    MC[I]: MQTT failed! Retryting to connect...
    MC[I]: MQTT settings(Broker:[], Port:[1883])
    MC[I]: MQTT authenticating as anonymous
    MC[I]: MQTT connected :)
    MC[I]: MQTT topic subscribed:[in_esp/ESP_2D5A26/#]
    <here is stuff that indicates everything is in order (but wrong version of software)>

  • @njbuch I do not see any recent change on this. I will check this locally and update you. Thank you!

  • Is there anything I can do to assist finding the caveat in this?

  • @njbuch Ah, Sorry I forget about this. I will update you soon. Thank you for your patience.

  • @njbuch Thank you for your patience. Today I tried with the latest firmware from the repository. I see some other issue.

    MC[I]: FW Config Internal(Type:65535, Version:65535, Blocks:65535, md5sum:[---------md5sum-not-set---------])
    MC[I]: FW Config Response(Type:1, Version:1, Blocks:1520, md5sum:[c51ee13cbd11ded58f19844a92ee3a62])
    MC[I]: Firmware upgrade started...
    ERROR[7]: MD5 Failed: expected:c51ee13cbd11ded58f19844a92ee3a62, calculated::rc11cd:00cc010rs:c=sdd6=A11d6eA

    I am not a CPP export. I will try to fix this issue soon. I have to go through some tutorials.

    I have files an issue to track this one.

  • @njbuch in the released version 1.0.0 everything working good. The only problem with the master build.

    Until I resolve the issue you may use 1.0.0 version

  • @jkandasa Thanks for looking into this. I will wait till a new release, unless you want me to do some testing?

  • @njbuch master branch works well with ESP8266 2.3.0 version.

    The problem comes when we upgrade to 2.4.0 and above. For now, you should revert back your esp8266 Arduino version to 2.3.0

Suggested Topics