# Firmware Update Issue

**URL:** <https://forum.sovol3d.com/t/firmware-update-issue/2089>\
**Category:** Sovol SV06 Fully Open Source 3D Printer\
**Created:** [March 29, 2023, 4:00pm UTC](https://forum.sovol3d.com/t/firmware-update-issue/2089 "2023-03-29T16:00:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![JRChristenson](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JRChristenson](https://forum.sovol3d.com/u/JRChristenson)\
**Post date:** [March 29, 2023, 4:00pm UTC](https://forum.sovol3d.com/t/firmware-update-issue/2089/1 "2023-03-29T16:00:56Z")

</div>

I’m trying to update the firmware on my SV06 but it’s not flashing. It’s been on the blue screen for a very long time. How long should it take?

---

<div class="post-metadata">

**Author:** ![Ac7ss](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.sovol3d.com/ac7ss/32/930_2.png) [@Ac7ss](https://forum.sovol3d.com/u/Ac7ss)\
**Post date:** [April 1, 2023, 8:56am UTC](https://forum.sovol3d.com/t/firmware-update-issue/2089/2 "2023-04-01T08:56:54Z")

</div>

Try it again with a fresh, blank SD card with only the file on it. (Reformat it fat32 if necessary.)

---

<div class="post-metadata">

**Author:** ![jdrabik](https://avatars.discourse-cdn.com/v4/letter/j/b19c9b/32.png) [@jdrabik](https://forum.sovol3d.com/u/jdrabik)\
**Post date:** [April 7, 2023, 9:14pm UTC](https://forum.sovol3d.com/t/firmware-update-issue/2089/3 "2023-04-07T21:14:52Z")

</div>

Same problem here. I have a fresh SDcard, formatted as vfat. The firmware file is the only file on the card (except for the System Volume info folder from vfat). I’ve tried SV06V2.0.0A\_2.24.bin (the original name from Sovol), and also have tried renaming the file to: firmware.bin, FIRMWARE.BIN, firmware1.bin, FIRMWARE1.bin, firm.bin, and sv06v2.0.0A\_2.24.bin (i.e., upper and lower case variants of each of the names). None of these work. Unlike the OP, the blue screen goes away fairly quickly, but going to “About Printer” still shows the original version of V2.0.0\_A and there are no apparent operational differences (so, since there is no progress bar and since the version is identical, I conclude that the update has NOT occurred).

Could you have your team investigate the firmware update problem? It appears many other people are encountering this too. Thank you.

---

<div class="post-metadata">

**Author:** ![Rossco](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@Rossco](https://forum.sovol3d.com/u/Rossco)\
**Post date:** [April 9, 2023, 10:45am UTC](https://forum.sovol3d.com/t/firmware-update-issue/2089/4 "2023-04-09T10:45:15Z")

</div>

usually the bootloader on the 32bit controller boards NEEDS fat32 format and can not use any other formats other than FAT32

---

<div class="post-metadata">

**Author:** ![jdrabik](https://avatars.discourse-cdn.com/v4/letter/j/b19c9b/32.png) [@jdrabik](https://forum.sovol3d.com/u/jdrabik)\
**Post date:** [April 11, 2023, 3:46pm UTC](https://forum.sovol3d.com/t/firmware-update-issue/2089/5 "2023-04-11T15:46:48Z")

</div>

In my case, both SD cards I tried were formatted for VFAT. There is still no indication an update is in progress (such as a message or a progress bar) and the software version does not change in the “About Printer” menu.

---

<div class="post-metadata">

**Author:** ![Rossco](https://avatars.discourse-cdn.com/v4/letter/r/5f9b8f/32.png) [@Rossco](https://forum.sovol3d.com/u/Rossco)\
**Post date:** [April 14, 2023, 6:27am UTC](https://forum.sovol3d.com/t/firmware-update-issue/2089/6 "2023-04-14T06:27:36Z")

</div>

vfat is NOT fat32, it is a later structure of the allocation tables and directories/files and is NOT readable by fat32 only OS’s
