Standard Spirit v3.2.0 Firmware Update Failure

[HeliMLM]

fu$&... that's bad... esp. as it seems it would have done directly on Mac. so you'll have to wait for Tomas... he - for sure - has again the magic trick.

btw: i've just tested with another unit directly on Mac and it failed... it started to blink quickly after reboot. i again did it on Parallels / Win 10 and the unit was recovered to 3.2 easily. no parameters lost or whatsoever.

[ZeXx86]

The unit can be fixed even if update failed, but in this case normal recovery mode will not work if the update failed right in the most important moment. So to fix the unit it is necessary to open it. In case of RS this is little bit complicated and must be done very carefully to not damage antennas or other electronics. In each case we highly recommend to send it to us. The reflash is done for free. So you do not have to pay for this repair.
For this reason we do not recommend to perform the update on Mac as in this update more data are rewritten than usually.

If the first stage of the update will finish, then you are safe. Maximally the unit will be flashing and new recovery mode can be used.
If unit has at least some LED activity it can be fixed within few seconds through recovery.
Fortunately this issue can happen only now but once 3.2.0 is flashed, it can't happen anymore in the future.

You can contact me regarding the flashing problem via private message. Then we can find the best solution.

[toto_gt]

I am afraid I was not so lucky - reading the waring about using a Mac I reinstalled my VMware and ran windows 10...not fun to start with

Anyway did you usual firmware update procedure and got a "failed" message. Now my RS is dead as a doornail.
No LED at all - yes I tried recovery procedure but the Spirit Settings app just hangs

Don't use VMware or anything else ! It might work, but in most cases it won't.

Because the Guest OS in the VMware has to use the driver of the Hostsystem , in your case the one of the MAC.
So if you are lucky the Guest OS Driver "overwrites" the Host OS Driver and the Guest OS is able to use the Hardware directly.
In most cases it just works like .......

So get a real OS and do it from there. Using real Hardware over a VM is not a good idea and fails over and over again.
(expect for standard things like Hard disk, GPU and so on)

[marcothefly]

Hello,
if someone has updated the DS 12 to v3-2-0 can you tell me how to do it?

Thank you

[ZeXx86]

Please check this page:
http://manual.spirit-system.com/index.p ... N.29_files

[marcothefly]

Thanks Tomas, but I didn't quite understand where to copy the SPIRIT-3-2 file.
Sorry

[ZeXx86]

Old files must be replaced with new files.
So you can see there are 3 things in the SPIRIT-3-2/Devices directory. These must be copied to current Devices directory at your SD card as written in the guide.

[marcothefly]

Old files must be replaced with new files.
So you can see there are 3 things in the SPIRIT-3-2/Devices directory. These must be copied to current Devices directory at your SD card as written in the guide.

Yesss,
now go well!!!
Thank you

[yufasa]

Just want to thank Thomas for reaching out and helping me to sort out my bricked RS unit. Fantastics support and another reason that Spirit FBL is such a fantastic platform to use.

Thanks!

[Ricad]

Hi, I tried updating a standard Spirit to 3.2 Win10 machine that I had just updated a Pro with that worked fine. The standard one is now just flashing the LED and will not connect to the PC.

I am not sure what the recovery procedure is, so some guidance would be great.

Thanks

Adrian

https://photos.app.goo.gl/gVNwyAMDH7NXYJ3F7