1 (edited by Holmz 2022-06-24 05:24:34)

Topic: Cannot flash the ADI-2 Pro firmware... but why?

I've tried this on a MacBook Pro, in 10.11.6 and again a day later using 11.6.7
And also on an Intel NUC running windows.
Both give this message "Programming Status: Failed with error 9000007E/5"

Are there protections somewhere on the unit?
The unit is new to me and I am struggling with Linux and OSX, but was able to capture sound on the Intel NUC running windows.
The same USB was used direct in both computers.

Unit is a few years old "RME ADI-2 Pro".

2 (edited by KaiS 2022-06-24 06:45:18)

Re: Cannot flash the ADI-2 Pro firmware... but why?

For Windows PC, the driver needs to be installed:
https://www.rme-audio.de/adi-2-pro-fs-be.html
https://rme-audio.de/downloads/driver_m … _09747.zip

Excerpt from manual page 11:

7 Firmware Update
... The Flash Update Tool updates the firmware of the ADI-2 Pro to the latest version. Under Windows it requires an already installed MADIface series driver, which is found on the same download page.


• Try another USB Cable.

• Under Windows you could even try:
Right Click - Run as admin

Re: Cannot flash the ADI-2 Pro firmware... but why?

Holmz,

Per the above guidance, the RME Driver is essential for the application of new RME FW.

It's an easy, free process.  The updates via the FUT are remarkably easy, and often bring about the most amazing new features/functionalities!

Download/Install the RME Driver, and..

Enjoy!

Curt

Vintage 2018 ADI-2 DAC. "Classic AKM4490 Edition"
Cables:  Red, and White Ones.
Speakers:  Yes

Re: Cannot flash the ADI-2 Pro firmware... but why?

I got (another) new (and shorter) USB cable today.
When I turned the unit one now. I get a status overview.

And the s/w loaded fine.
It was either the cable was bad, or maybe the USB was not plugged in when it was turned on?

In any case it worked finally.

5 (edited by KaiS 2022-06-25 07:28:58)

Re: Cannot flash the ADI-2 Pro firmware... but why?

Holmz wrote:

I got (another) new (and shorter) USB cable today.
When I turned the unit one now. I get a status overview.

And the s/w loaded fine.
It was either the cable was bad, or maybe the USB was not plugged in when it was turned on?

In any case it worked finally.

Seems some USB-C to USB-A or USB-B cables are for charging only, not for data transfer.


In general, USB cables longer than 3-5 m (depending on the quality) are problematic for reliable data transfer.

For long distances an “active” USB cable with repeater is necessary.

I do use such 10 and 15 m USB cables without problems:
https://smile.amazon.de/gp/product/B004 … &psc=1

https://smile.amazon.de/gp/product/B003 … &psc=1

https://m.media-amazon.com/images/I/81ggxtqFl+L._SX522_.jpg