Relax. We don't know there's anything seriously wrong.

As far as I can see, you uploaded the beta firmware successfully so that it displayed 2.5b9M without saying "bad software", then used the wrong Config programme and the 568 has got confused.

You need to start from scratch and reload the same firmware that you did at the start. Can you do that and then stop and come back to us? You seem to have done it successfully in the first place.

A few other points

- Just to reiterate, once you start to configure (which I suggest you wait to do), you should not be using the current MConfig with the graphical interface, but the Legacy Configuration Program with a much older interface. Instructions for finding it are above (from Carl I think).

- It will never display an "MM" so don't be worried about that. I'm not sure it will say 568.2 either, and can't check as I don't have one right now.

Important question: you mentioning "doing a fetch" a few times. Do you mean fetching from the device to the configuration programme? That is not recommended as it seems to cause more problems that it solves. The recommended workflow is that for each new configuration you create it on your PC and then download it to the 568. You can base each new one on a previous version which you have saved on the PC.

HTH


Ex-moderator
Sitting room: dCS Network Bridge, 818v3, HD621, 8kSE
Library: dCS Rossini Apex DAC/Clock, Clearaudio Performance Wood, Audio Research PH2, Mjölnir KGST, Mjölnir PureBipolar
SWMBO Room: 210, D33
Kitchen: Meridian MS200, Genelec 6010 actives
Mobile: Audioquest DragonFly Copper, Sennheiser IE600
Desk: Merging Anubis
Server: Roon/ROCK/NUC

Headphones: Stax SR-X9000, Stax SR-007, Stax SR-404LE, Audeze LCD-X...

Oldest audio file: 1889 Edison cylinder