Naim firmware update for legacy streamers

[davidhendon]

This is a well known error that occurs on some of Naim’s printed rear panels of a particular age. In any case the socket shown on the photo is a miniUSB. So if your’s looks like that, that’s the lead you want.

Best

David

[Mike-B]

Yes the picture shows RS232 printed, but the actual port shown is a mini-USB so the picture is wrong. My drawing picture is from the manual.
The other thing is (I believe) RS232 was only fitted to NDX & changed soon after, my 2014 NDX is a mini-USB, & if I’m right ND5XS was never produced with RS232.

[Antonio1]

nice
Also , when update is performed using MacBook Air a fully wired USB C (and not A ) to Mini-USB B cable is the right one, right?
In that case may I use the one that comes with an Asus burner since data is involved?

[Blackbird]

2 min photoshop job to make it right

[davidhendon]

Yes but the issue is that the panels were printed incorrectly for some early production and Naim either didn’t notice or decided to use them rather than scrap them.

[Suedkiez]

I still think it may be technically correct because RS232 is a protocol and not a port specification, but it is quite misleading in the modern age where few people can distinguish it. We had this before

NDX. Naim Android app doesn't list it.... and more...

This is funny and indeed confusing but I believe technically correct as RS-232 is a communication protocol (https://en.wikipedia.org/wiki/RS-232) and not a port specification. Various ports were used for RS-232 (the 9-pin port of the older NDX being quite common, https://en.wikipedia.org/wiki/Serial_port, but others like the 25-pin were as well). I suppose in this case it is RS-232 protocol over mini-USB, quite unusual

[Naim.Marketing]

Did you do a factory reset after updating your NDX? That is worth a go, along with a pinhole reset of your Mu-so.

[Chappers]

Logging off Tidal from within the Naim Tidal app and then re logging in sorted it for me.
Good luck.

[Ceexkay]

Another successful update for N272 using 2012 MacBook Air running macOS Mojave 10.14.6. A data point for support.

No issues were encountered, followed instructions to the letter - I had read the warnings

CK

[SHTom]

Hi Chappers. Yep after signing on and off a couple of times all OK. Probably not helped by the fact we use several iPhones/ipads to control two streamers. Fingers crossed. Thanks both for your comments.

[Dooley]

A successful update using 2014 MacBook Pro running macOS Mojave 10.14.6. No problems with the N272, and the Unitiqute was OK once I was able to install the driver for the USB to RS232 cable. A big thank you to the community for your help and advice in this thread.

[mbishop]

Updated my 272 (from Mac) and Muso (1st gen) without issue - thanks for the clear instructions! Sounding good…

[Ackers]

Only 2 hours in which is due in part to two slow laptops. One has windows 10 the other is 7 which I’m more familiar with. The USB A - Mini USB B cable is a Ugreen data cable. I’m unable to see the downloaded cable driver in Networks after repeated attempts trying different options on both laptops. I’ve now plugged the cable into the NDS and the windows 7 laptop and it appear that there’s no need for a driver with this cable. Once plugged in it says device driver not successfully installed. But in the in Device Manager it shows CP2102 USB to UART Bridge Controller. Device status - drivers are not installed Code28. Says update driver clicking on search online for software isn’t producing anything after 5 minutes. I’m tempted to get another cable unless someone says the cable will transfer the upload to the NDS. A bit fed up with this to say the least thought it would take 20 min max.

Ackers

[davidhendon]

The must read the Naim instructions and do exactly what it says in the order it says it. There is another thread which gives some hints about how to install the drivers. You can’t just download the zip. You have to unpack it and run the x64 file…

Helpful comments and observations when installing update 4.8

I have just performed the 4.8 update on an NDX using a Windows 10 computer and a USB to mini USB cable. Here are some observations that might be useful: If you need to install the USB to mini-USB driver you will get a zip file. Although windows lets you inspect the contents, clicking the installer does nothing and it fails silently, FIX: The fix is to make sure you unzip it to your hard drive There are two installers, CP210xVCPInstaller_x64.exe and CP210xVCPInstaller_x86.exe. The first one is …

[Ackers]

David,

All’s well. I did get another USB cable. The other one did make the laptop go bing/bong and said something about a driver. The other cable seemed to do the trick and the driver software appeared as per the screen shots in the guide. Thank you very much for coming to my aid and the notes from the other thread helped a great deal. The power of this great forum is a big thing when presented with queries and problems. I’m now looking forward to a glass of something calming later on and to see if I can hear an improvement in the sound quality. Tidal is up and running and it’s good to see v4.8 in ‘about’ in Tidal. Thank you.

[SneakyPete]

Same here.
Installed 4.8 without a problem but alas…
Long DSD tracks (only when they are .dsf, .dff files play fine as before) is NOT solved…

DSF file

DFF file

[Naim.Marketing]

I know @Stevesky is looking into specific DSD files people are still having issues with, so flagging this for his attention.

[Lucifer]

Is it installing the update in a mirrored image kind of way?

This looks more like it

[nitrous]

is that for real? Or photoshop?
Pretty serious (although funny because it isn’t mine)…

[Lucifer]

It is for real