logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Troubleshooting Magic Home BL602 OTA Update Stuck on Starting OTA Status

hubiverse 1557 20
ADVERTISEMENT
Reply | New topic
  • #1 20918603
    hubiverse
    Level 3  

    Hello, I have several Magic Home LED controllers flashed with Open Beken. I'm trying to flash the BL602 OTA file using the web app but I get stuck with a status of "starting OTA". I've tried a couple of web browsers with no improvement. They're currently on version 1.17.308. Any help would be great. UART flashing these sounds like a pain considering how many I have around the house. Thanks!
  • ADVERTISEMENT
  • #2 20918840
    p.kaczmarek2
    Moderator Smart Home  
    Thank you for reporting the problem. I will check this on my side, but it seems like a known issue when BL602 image grows too big. It happens from time to time.

    This basically means that newer build is a bit too big for OTA and you have to wait for us to reduce it's size a bit.

    BL602 is a bit more memory-limited than Beken, I will need to look into the code and figure out what can I strip.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 20922160
    hubiverse
    Level 3  

    Ah, okay! I'll see if previous releases that are a bit newer than what I'm on seem to work. I'll report back if I get one to take. Thanks for the help!
  • #4 20923912
    hubiverse
    Level 3  
    If I updated via UART, should that work alright?
  • #5 20924027
    p.kaczmarek2
    Moderator Smart Home  
    WiFI OTA problems do not affect UART, so it will work.
    Some related discussion and testing here: https://www.elektroda.com/rtvforum/topic4020634.html#20923793
    Helpful post? Buy me a coffee.
  • #6 20945544
    miegapele
    Level 15  

    This should now work with the latest version 17.450. Flashing from the old version may still be troublesome, but it should succeed after a few tries. Try flashing immediately after restarting and stopping logs too.
  • #7 20959057
    hubiverse
    Level 3  

    I assume when you say stopping logs, you're saying to setting the log level to none? Or is hitting pause good enough.

    Added after 2 [minutes]:

    Is there a command to disable logs on boot?
  • #8 20959374
    miegapele
    Level 15  

    Yes, I mean stopping logs. You can disable all the categories. I think that stopped logging. Also, you can try to upload firmware again immediately after the first try fails (need to watch dev console). It also helped me. But watch out for freezes. Usually, if I tried 3 times it froze and required a power cycle.
  • ADVERTISEMENT
  • #9 20966268
    hubiverse
    Level 3  

    Unfortunately, no matter what I try, ota does not succeed. ota gives me OTA:recv returned -1 - end of data - remaining 400958 when I allow logs of ota. I tried everything to update with logs disabled but I'm afraid the feature doesn't play nice with these magic home devices.
  • #10 20966469
    miegapele
    Level 15  

    Did you try to hit upload immediately after first try fails (watch for error in dev console)
  • #11 20967507
    hubiverse
    Level 3  

    Is the dev console different from the log console?
  • #12 20968532
    miegapele
    Level 15  

    Log console I guess you mean the one in web app? They are not the same dev console is opened by pressing f11 in the app. However, error message you see looks functionally equivalent, however I have never seen that one.
  • #13 20968856
    hubiverse
    Level 3  

    Screenshot of an OTA interface and developer console with errors. Oh! You mean the dev console for the web browser itself, sorry I thought there was a console on the web app somewhere I was missing lol. Unfortunately, it doesn't seem to have improved. I've tried several times, but I receive an error on each attempt. I'm not experiencing any freezing, though. I'll attach a screenshot of my last attempt. Maybe it'll be useful.
  • #14 20968862
    miegapele
    Level 15  

    Okay, I also did not experience that. Unfortunately cannot think of anything else to try
  • #15 20969616
    hubiverse
    Level 3  

    Any ideas as to why dev cube is giving me this error?

    Screenshot of a microcontroller programming tool with an error message list index out of range.
  • #16 20969643
    miegapele
    Level 15  
    People have trouble with 1.8. try flashing with 1.4.8 it's in openbl602 SDK repo.


    Added after 1 [hours] 18 [minutes]:

    Also that log is very strange. It says something about the OTA. Did you pick correct image?.
    You also do not have dts specified in this flasher. I think that will make Mac address all zeros.
  • ADVERTISEMENT
  • #18 20969794
    miegapele
    Level 15  

    DTS is device tree source. It's coming from Linux and specifies device config. But it's also used in some microcontrollers. I see in that file various defaults, including where to get device MAC from.

    Also, if I remember correctly, partition layout is different onq1.8 so flashing with that will probably remove existing settings

    Added after 33 [minutes]:

    Some more information here: https://lupyuen.github.io/articles/flash#device-tree
  • #19 20971227
    hubiverse
    Level 3  

    1.4.8 BL Dev Cube ended up working well for me. Thanks for your help. I'll see if OTA works again once a new version is released
  • #20 21014590
    p.kaczmarek2
    Moderator Smart Home  
    @hubiverse hello again, what is the state of this issue, can you check whether BL602 OTA works or not? Thank you.
    Helpful post? Buy me a coffee.
  • #21 21594790
    hubiverse
    Level 3  
    >>21014590 hey! sorry it's been so long. I went through and manually flashed firmware over UART and then recent updates seem to work. Thanks for your help. I'm now trying to see if I can get the strips to return to their values after power loss but I'm sure I'm just overlooking something in the module config flags.
Reply | New topic
Report a violation of the law

Topic summary

The discussion addresses an issue with Magic Home LED controllers running Open Beken firmware, where OTA updates for the BL602 chip get stuck at "starting OTA." The problem is linked to the BL602 image size exceeding OTA memory limits, causing update failures. Users reported that UART flashing bypasses OTA issues but is inconvenient for multiple devices. A newer firmware version 17.450 improved OTA success rates, especially when logs are disabled and flashing is attempted immediately after restart. Disabling logs and retrying uploads multiple times can help but may cause device freezes requiring power cycles. The dev console in the web browser aids in diagnosing errors, revealing OTA reception errors and potential image mismatches. Downgrading to OpenBL602 SDK version 1.4.8 instead of 1.8 resolved some flashing problems, as 1.8 has partition layout differences and missing device tree source (DTS) configurations, which affect MAC address and device settings. Manual UART flashing followed by recent updates restored OTA functionality. The device tree source (DTS) is critical for device configuration, including MAC address assignment. Overall, OTA updates on BL602 require careful firmware version selection, log management, and sometimes fallback to UART flashing due to memory and partition constraints.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT