RS520: MCU update loop after [Early Access] v5.12.04

Early Access
#1

After the latest update to version [Early Access] Ver 5.12.04, a window pops up prompting me to update the MCU to a new version. After clicking the Yes button, the device reboots, and once it boots up, the MCU update window appears again — and this repeats endlessly, meaning the update gets stuck in a loop. As a result, I’m unable to update the audio device’s components.

For now, I’ve rolled back to the stable version 5.9.0.9. But as far as I understand from reading the forum, this means I’m now unable to update the MCU on my device at all.

I also noticed that after the update, the ROSE ID in Rose Connect One was displayed as ‘ABCD’. However, after rolling back to the stable version, it started displaying correctly again.

This is completely unacceptable for a premium device at this price point!!!

#2

@Geka4epist
Thank you very much for the detailed description of the issue.
As we are currently unable to replicate this issue on our end, we plan to run repeated tests across multiple devices to analyze and identify the root cause.

In the meantime, we would like to ask a quick clarifying question regarding the issue: When the MCU update pop-up appeared and you selected “Yes,” did the device reboot after the progress bar finished, or did it restart immediately without showing the progress bar at all?

Could you please check if you have any prior history of MCU updates?

Thank you for your cooperation.

#3

Thank you for your response.
To answer your question: after I click the Yes button, no progress bar appears at all — the device reboots immediately.
As for the MCU update history: before this, I had never received any MCU update prompts on my device at all. This was the first time the MCU update pop-up ever appeared.

I’d also like to point out that this issue looks very similar to a previously reported case on the RS151: RS151 - Repeated Audio MCU Update message. In that thread, the same endless MCU update loop was reported back in October 2025. It seems the same class of bug has now appeared on the RS520 with the [Early Access] v5.12.04 update.

One more thing I’d like to add: my RS520 occasionally fails to wake up from standby. Sometimes it doesn’t respond to either the remote control or the power button on the unit itself — I can hear the power relays clicking when I press the button, but the device doesn’t actually turn on. It can take quite a while (and several attempts) before it finally boots up. If the MCU update is meant to address issues like this, then the broken update process is preventing me from receiving a fix for a real, recurring problem with my device.

I hope this helps your team connect the two cases and identify the root cause, and that the fix can be delivered via a software update.