Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems Firmware update 568.2mm and 5k 18bit

While updating my 568.2mm I had a power interupt. Machine is unharmed and still functioning well but unfortunately it now shows the "bad software" at start up. Searching the forum the best way forward is to reflash the firmware. So I'm looking for the firmware previous installed being version 2.5b9.

I also have a pair of old 5K 18 bit, still running at firmware 2.18 or so. I would like to upgrade those as well. Latest according to the wiki is 5.21 but I don't know if that is suitable for the 18 bit version as well.

If anyone could help me out that would be much appreciated.

Erik

Hopefully a friendly dealer will help with 568 firmware but for 18bit DSP5000's the firmware is on EPROM chip and not the same as 96/24 versions so not freely available and possibly not even worth the hassle of obtaining later chips and fitting them even if someone has access to spares.

Here you go....

WayBackMachine Meridian Firmware archive

Thanks very much.

Downloaded the zipfile and installed the *.mfp file according to the wiki and with a bit of perseverance I managed to get that installed (seems I needed the older version of the Winfup software.) However the mfp file does the upload for four separate mfu files. but the TYPES568.MFU is not uploaded. Do I have to do that separatly again with WINFup ?

Did you grab the beta version of the upload software?

It has been so long since I did it I can't remember.

It says on that link..
Go to the install directory
(which is normally C:\program files\Meridian\Meridian)
and replace the 'Meridian.exe' file with this.

beta version.

As far as I am aware you should use WinFUP for installing the firmware mfp file (which then installs, in my case, 4 out of the 5 mfu files, found in de 2.5b zip file)

Then you should retype the 568.2mm

Then, using the Legacy installer you should start setting up your DSP, inputs etc. saving as an MSF file which you then store to the 568.2mm.

The Meridian.exe file your referring to is an update to the Legacy Installer with in a dropdown menu has now the ability to store MSU files in a firmware 2.5 or above format. I have used this update (version 2.215R) to create a file.

The only thing is the Types568.mfu file which is not uploaded by the mfp file using WinFUP.

Is this required ? Should I install it with WinFUP or the Legacy installer (via advanced tab) ?

Hi,

The .mfp file loads all that is required, ignore the Types568.mfu

Regards,
Carl

I�ve uploaded the latest firmware (2.5b9) and using the WinFUP software this went OK (after a couple of attempts)
I�ve retyped the 568 to a 2.0 channel DSP setting. (no sides, no center, no sub.)

I�ve created an MFU file, using the legacy installer version 2.215R and the tab of using firmware 2.5 and higher. I�ve then uploaded this to the 568 and according to the installer this went ok as well.

Certain parts of the MFU file are picked up correctly (name of the machine, controller yes/no, whether some inputs are available or not etc. However it does not store the fact it should use large DSPs (it goes to the standard of 96/24 DSPs), initial volume or the fact it should use an MSR+ remote, making it very slow to respond).

I�ve tried then to use firmware 2.12 (latest official) with exactly the same results. (Firmware uploaded correctly, certain parts of the MFU file picked up correctly where other bits are not stored (DSPs type and start-up volume).

When I (at a last resort) fetch the settings of the latest uploaded file, the settings I get are again the standard settings (DSP 96/24, startup volume 65, etc.)

What am I doing wrong? To me it doesn�t seem to be an EEPROM issue as it definitely stores some parts of the MFU file, but other parts not.

Erik

It's been a while since I did config on a 568 but IIRC the fetch was always incomplete. What you see is I think ' normal'. Others I am sure will confirm.

Set your config in the PC file and just send to the unit.

Nick,

I seem to remember this being the case... Can't be 100% though.

Matt

+1 - always remember having to tweak the config file after fetching.

Is this where the general view of not fetching the config started?

Russ