logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Troubleshooting Magic Home BL602 OTA Update Stuck on Starting OTA Status

hubiverse 2358 20
Best answers

Why does the BL602 Open Beken web OTA update get stuck at “starting OTA,” and how can I update it?

The OTA is likely failing because the BL602 firmware image is too large for OTA on these memory-limited devices, so the updater gets stuck at “starting OTA” [#20918840] Use the latest build 17.450, since that version should work again, although flashing from an older version may still take a few tries [#20945544] If you keep retrying, do it immediately after a restart and with logging stopped or disabled to improve the chance of success [#20945544][#20959374] Wi‑Fi OTA problems do not affect UART flashing, so UART is a reliable fallback if OTA keeps failing [#20924027]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 20918603
    hubiverse
    Level 3  
    Posts: 11

    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  
    Posts: 14400
    Help: 650
    Rate: 12330
    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.
  • #3 20922160
    hubiverse
    Level 3  
    Posts: 11

    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!
  • ADVERTISEMENT
  • #4 20923912
    hubiverse
    Level 3  
    Posts: 11
    If I updated via UART, should that work alright?
  • ADVERTISEMENT
  • #5 20924027
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14400
    Help: 650
    Rate: 12330
    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 16  
    Posts: 173
    Help: 15
    Rate: 29

    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.
  • ADVERTISEMENT
  • #7 20959057
    hubiverse
    Level 3  
    Posts: 11

    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 16  
    Posts: 173
    Help: 15
    Rate: 29

    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.
  • #9 20966268
    hubiverse
    Level 3  
    Posts: 11

    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 16  
    Posts: 173
    Help: 15
    Rate: 29

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

    Is the dev console different from the log console?
  • #12 20968532
    miegapele
    Level 16  
    Posts: 173
    Help: 15
    Rate: 29

    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  
    Posts: 11

    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 16  
    Posts: 173
    Help: 15
    Rate: 29

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

    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 16  
    Posts: 173
    Help: 15
    Rate: 29
    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.
  • #17 20969780
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14400
    Help: 650
    Rate: 12330
    What does the DTS stands for there?
    Helpful post? Buy me a coffee.
  • #18 20969794
    miegapele
    Level 16  
    Posts: 173
    Help: 15
    Rate: 29

    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  
    Posts: 11

    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  
    Posts: 14400
    Help: 650
    Rate: 12330
    @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  
    Posts: 11
    >>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.
Generated by the language model.
Today's popular

FAQ

TL;DR: BL602 OTA can hang at "starting OTA". Users report freezes after 3 tries; "if I tried 3 times it froze". Disable logs, reboot, then retry with the latest build; use UART as fallback. [Elektroda, miegapele, post #20959374]

Why it matters: Helps OpenBeken users on Magic Home BL602 controllers recover stuck OTAs without dismantling devices.

Quick facts:

Quick Facts

Why does BL602 OTA get stuck at “starting OTA” on Magic Home with OpenBeken?

A common cause is image size. It’s a “known issue when BL602 image grows too big.” BL602 has tighter memory than Beken. Oversized builds can’t fit the OTA slot, so updates stall. Wait for a smaller build or a trimmed release. [Elektroda, p.kaczmarek2, post #20918840]

Which firmware version first improved BL602 OTA reliability?

Version 17.450. The maintainer noted BL602 OTA should work there. From older versions, updates may still be troublesome. You might succeed after a few tries. Restart the device and stop logs before attempting the upload. [Elektroda, miegapele, post #20945544]

How do I get past the “starting OTA” status right now?

Try this:
  1. Restart or power‑cycle the device.
  2. In the web app, disable all log categories.
  3. Upload the latest firmware immediately after the reboot. “Try flashing immediately after restarting and stopping logs too.” This sequence can help older builds finish OTA. [Elektroda, miegapele, post #20945544]

How do I stop logs to improve OTA stability?

Open the web app and disable all log categories. That stops logging. If the first upload fails, start another upload immediately. Watch for freezes after repeated attempts. “If I tried 3 times it froze and required a power cycle.” Limit tries and power‑cycle if it locks up. [Elektroda, miegapele, post #20959374]

Is the browser dev console different from the OpenBeken log console?

Yes. The log console lives in the web app. The developer console is your browser’s console. Use the browser console to watch upload errors and timing. The thread shows a screenshot of the browser console during OTA tests. This view helps time quick retries. [Elektroda, hubiverse, post #20968856]

Should I switch to UART when OTA fails?

Yes. “WiFI OTA problems do not affect UART, so it will work.” Serial flashing bypasses Wi‑Fi transfer limits and OTA size constraints. Use BL Dev Cube or another UART tool to refresh the device cleanly. Then try OTA again on a newer build. [Elektroda, p.kaczmarek2, post #20924027]

Which BL Dev Cube version works best with BL602?

Use BL Dev Cube 1.4.8. Users reported trouble with 1.8. Version 1.8 uses a different partition layout and can remove existing settings. Ensure you select the correct image in the flasher. Missing DTS can set the MAC address to all zeros. [Elektroda, miegapele, post #20969643]

What is DTS in BL Dev Cube, and why does it matter?

DTS is Device Tree Source. It defines device configuration for flashing. The DTS includes defaults, such as where the MAC address is read. Set it so the device keeps correct identification and layout. The post also links an explainer with DTS basics. [Elektroda, miegapele, post #20969794]

What does “OTA:recv returned -1 … remaining 400,958” mean?

It’s the OTA log for an early termination. The receiver reached end of data with 400,958 bytes still pending. Enable OTA logging to capture this if updates stall. This confirms an incomplete or stuck OTA transfer on your BL602 unit. [Elektroda, hubiverse, post #20966268]

After manual UART flashing, will future OTA updates work again?

Yes. One user completed a UART flash and then reported that later OTA updates worked. A clean serial reflash can restore OTA reliability on Magic Home BL602 controllers. This indicates the base firmware matters for OTA success. [Elektroda, hubiverse, post #21594790]

How many OTA attempts should I try before power‑cycling?

Limit yourself to two quick attempts. The thread notes freezes after three tries and then a power cycle is required. If the device stops responding, cut power briefly and retry with logs disabled. This reduces lockups and improves success rates. [Elektroda, miegapele, post #20959374]

Did I choose the right firmware image for my method (OTA vs UART)?

Verify the image matches your method. The thread flags errors when the wrong image is used. Also set DTS in BL Dev Cube. Missing DTS can zero the MAC address and cause configuration issues after flashing. [Elektroda, miegapele, post #20969643]

Is BL602 more memory‑limited than Beken, and how does that affect OTA?

Yes. The maintainer states BL602 has tighter memory. Larger builds can outgrow the OTA slot. That leads to OTA that starts but never progresses or stalls mid‑transfer. The team trims features to fit. Waiting for a leaner image can resolve it. [Elektroda, p.kaczmarek2, post #20918840]

What if OTA still fails after retries and log tweaks?

Flash over UART, then revisit OTA on a newer build. A user confirmed BL Dev Cube 1.4.8 worked via UART. After that, subsequent OTAs succeeded. This resets the base and avoids constraints from older images. [Elektroda, hubiverse, post #20971227]
Generated by the language model.
ADVERTISEMENT