# Eddy upgrade kit firmware 2.5.0 vs 2.4.9?

**URL:** <https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812>\
**Category:** Sovol SV08\
**Created:** [March 28, 2026, 11:48am UTC](https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812 "2026-03-28T11:48:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![csmall](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.sovol3d.com/csmall/32/4222_2.png) [@csmall](https://forum.sovol3d.com/u/csmall)\
**Post date:** [March 28, 2026, 11:48am UTC](https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812/1 "2026-03-28T11:48:08Z")

</div>

Does anybody know what is new or changed in the 2.5.0 firmware over the original 2.4.9 firmware? Would I want to bother upgrading from 2.4.9? Everything seems to be working fine with 2.4.9

---

<div class="post-metadata">

**Author:** ![mydani](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mydani](https://forum.sovol3d.com/u/mydani)\
**Post date:** [April 4, 2026, 7:44pm UTC](https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812/2 "2026-04-04T19:44:34Z")

</div>

Hm, due to curiosity, I downloaded the firmware onto the usb thumb drive, inserted it in the running printer, watched it reboot… for 1 minute… and then watched the hotend end up in blue smoke. ☹

[![](https://canada1.discourse-cdn.com/flex030/uploads/sovolforum/original/2X/4/4bdfb0fd22609ed06ed5b5b88c12ac6cb950b091.jpeg "Sovol SV08 incl. Eddy Kit after FW Upgrade 2.5.0") ](https://www.youtube.com/watch?v=RwMnB0Dl188)

Afterwards the display kept being blank after boot and the webinterface

Klipper reports: ERROR  
MCU Protocol error

This is frequently caused by running an older version of the firmware on the MCU(s). Fix by recompiling and flashing the firmware.

I will not say it’s due to the software. But I can say - few minutes before I printed a part w/o issue. And only thing done is inserting the thumb drive with the firmware 2.5 on it.

Regards

Daniel

---

<div class="post-metadata">

**Author:** ![BriComp](https://avatars.discourse-cdn.com/v4/letter/b/3be4f8/32.png) [@BriComp](https://forum.sovol3d.com/u/BriComp)\
**Post date:** [April 5, 2026, 11:56am UTC](https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812/3 "2026-04-05T11:56:19Z")

</div>

You need to update both MCUs before installing update from USB drive!

If you didn’t update the MCUs then I am not surprised by the outcome.

---

<div class="post-metadata">

**Author:** ![mydani](https://avatars.discourse-cdn.com/v4/letter/m/f0a364/32.png) [@mydani](https://forum.sovol3d.com/u/mydani)\
**Post date:** [April 5, 2026, 6:08pm UTC](https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812/4 "2026-04-05T18:08:13Z")

</div>

That’s not the way it should be - there should be plausibility checks, failsafes and at least a warning in the firmware upgrade document.

Last time I checked nothing was there.

---

<div class="post-metadata">

**Author:** ![BriComp](https://avatars.discourse-cdn.com/v4/letter/b/3be4f8/32.png) [@BriComp](https://forum.sovol3d.com/u/BriComp)\
**Post date:** [April 6, 2026, 11:29am UTC](https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812/5 "2026-04-06T11:29:16Z")

</div>

When the USB update takes place it deletes the USB contents.

These are the file names for the A2 Eddy Version :Sovol\_Update\_Package-10-20\_2.5.0-eddy.deb and SV08 klipper.bin. The .deb file is blown into the 2 MCUs and the .bin updates the system via the USB drive. It’s all explained in the Sovol Eddy manual.

---

<div class="post-metadata">

**Author:** ![stillme651](https://avatars.discourse-cdn.com/v4/letter/s/b9bd4f/32.png) [@stillme651](https://forum.sovol3d.com/u/stillme651)\
**Post date:** [September 22, 2026, 6:35pm UTC](https://forum.sovol3d.com/t/eddy-upgrade-kit-firmware-2-5-0-vs-2-4-9/9812/6 "2026-09-22T18:35:24Z")

</div>

it seems there is not a kilper update for 2.5 on solvo s web site i think once you installed eddy on 2.49 it should be just a klipper update package for for software or will kilper update 2.49 just have to be re flashed again??? that why mcu shown as different
