|
|
Post by scubadave on Dec 18, 2017 14:15:37 GMT -5
Hi,
My UMC-200 currently has a "DSP2 Code Not Match" Error, and I'm wondering what is a good path forward.
I spent about three hours last night upgrading the firmware from .39 to .52. With lots of trial and error, I had varying degrees of success and failure. At one point for example, I had what looked like a 'successful' upgrade, but the unit showed a DSP1 error, the OSD error, and a DSP2 error, so I reinstalled it all again. Eventually I got to an install that only had a DSP2 error, so I again tried to fix that, and I eventually had the Loading... error for many attempts...etc. Eventually, I got the unit back to showing a successful install of all four modules with the only error being the one I have now: DSP2 Code Not Match.
The unit works with this error, but I can't run Emo-Q. I have two main questions:
Question 1: What does DSP2 do and can I use the UMC-200 with this error? In other words, "Can I live with it?"
Question 2: Should I go back to the Updater program and try to reinstall the DSP2 module, or all modules, or something else? As stated above, I already tried once to reinstall just the DSP2 module and that mucked it all up and I had to start from scratch again.
Any suggestions?
Thank you!
|
|
|
|
Post by Gary Cook on Dec 18, 2017 14:57:12 GMT -5
Are you using the original load process or the alternate load process? I've had best success with the alternate process. There is a thread somewhere with the detailed instructions, if I have time today I'll try and search for it.
Merry Xmas to all
Gary
|
|
KeithL
Administrator 
Posts: 9,929
|
Post by KeithL on Dec 18, 2017 14:59:11 GMT -5
When you get one of those errors, it's not as simple as saying that a certain error will indicate that certain things won't work. It's more like "if you get a DSP 1 mismatch or a DSP 2 mismatch - odds are some things won't work right" - frequently what you get is no audio. We have encountered situations where back-dating the unit to VERY old firmware (maybe v.15) then updating it to current firmware worked perfectly and fixed occasional odd errors. However, it is also possible to render the unit inoperative - especially if there's an underlying power supply problem. On that note: 1) After the update you must DISCONNECT THE USB CABLE FROM THE UMC-200 (if you disconnect it from the computer, but leave it connected to the UMC-200, then it may cause errors). 2) Make sure that the power supply seems to be OK (if the unit sometimes drops back into Standby when you first turn it on, then that strongly suggests a power supply problem). Other than that, you may have better luck with one of the alternate load methods that calls for loading each module one at a time, and restarting the unit between each module. (If you want to try back-dating it, call in and we'll send you a copy of the old firmware.) Hi, My UMC-200 currently has a "DSP2 Code Not Match" Error, and I'm wondering what is a good path forward. I spent about three hours last night upgrading the firmware from .39 to .52. With lots of trial and error, I had varying degrees of success and failure. At one point for example, I had what looked like a 'successful' upgrade, but the unit showed a DSP1 error, the OSD error, and a DSP2 error, so I reinstalled it all again. Eventually I got to an install that only had a DSP2 error, so I again tried to fix that, and I eventually had the Loading... error for many attempts...etc. Eventually, I got the unit back to showing a successful install of all four modules with the only error being the one I have now: DSP2 Code Not Match. The unit works with this error, but I can't run Emo-Q. I have two main questions: Question 1: What does DSP2 do and can I use the UMC-200 with this error? In other words, "Can I live with it?" Question 2: Should I go back to the Updater program and try to reinstall the DSP2 module, or all modules, or something else? As stated above, I already tried once to reinstall just the DSP2 module and that mucked it all up and I had to start from scratch again. Any suggestions? Thank you! |
|
|
|
Post by scubadave on Dec 18, 2017 15:15:17 GMT -5
Are you using the original load process or the alternate load process? I've had best success with the alternate process. There is a thread somewhere with the detailed instructions, if I have time today I'll try and search for it. Merry Xmas to all Gary Gary, I used the original and both alternative load methods. I found that "alternative two" worked best. Thanks for asking. - Dave |
|
|
|
Post by scubadave on Dec 18, 2017 15:21:59 GMT -5
When you get one of those errors, it's not as simple as saying that a certain error will indicate that certain things won't work. It's more like "if you get a DSP 1 mismatch or a DSP 2 mismatch - odds are some things won't work right" - frequently what you get is no audio. We have encountered situations where back-dating the unit to VERY old firmware (maybe v.15) then updating it to current firmware worked perfectly and fixed occasional odd errors. However, it is also possible to render the unit inoperative - especially if there's an underlying power supply problem. On that note: 1) After the update you must DISCONNECT THE USB CABLE FROM THE UMC-200 (if you disconnect it from the computer, but leave it connected to the UMC-200, then it may cause errors). 2) Make sure that the power supply seems to be OK (if the unit sometimes drops back into Standby when you first turn it on, then that strongly suggests a power supply problem). Other than that, you may have better luck with one of the alternate load methods that calls for loading each module one at a time, and restarting the unit between each module. (If you want to try back-dating it, call in and we'll send you a copy of the old firmware.) Keith, thanks for the help. 1. I definitely did remove the USB cable after the upgrade. I try to follow the directions to a "t". 2. My UMC-200 has never dropped back to standby after turning it on. I can't think of any issues that would indicate a power-supply problem. For loading methods, I tried all three methods throughout the evening with varying results. Eventually I had the best luck with Alternative 2. It sounds like I should try back-dating the firmware and moving ahead to V52 from there. I will call in to Tech Support. Thank you! - Dave |
|
|
|
Post by scubadave on Dec 20, 2017 8:29:55 GMT -5
When you get one of those errors, it's not as simple as saying that a certain error will indicate that certain things won't work. It's more like "if you get a DSP 1 mismatch or a DSP 2 mismatch - odds are some things won't work right" - frequently what you get is no audio. We have encountered situations where back-dating the unit to VERY old firmware (maybe v.15) then updating it to current firmware worked perfectly and fixed occasional odd errors. However, it is also possible to render the unit inoperative - especially if there's an underlying power supply problem. On that note: 1) After the update you must DISCONNECT THE USB CABLE FROM THE UMC-200 (if you disconnect it from the computer, but leave it connected to the UMC-200, then it may cause errors). 2) Make sure that the power supply seems to be OK (if the unit sometimes drops back into Standby when you first turn it on, then that strongly suggests a power supply problem). Other than that, you may have better luck with one of the alternate load methods that calls for loading each module one at a time, and restarting the unit between each module. (If you want to try back-dating it, call in and we'll send you a copy of the old firmware.) Keith, Thank you for providing the V15 firmware - I was able to install it successfully and without any errors. I was then able to install V52 successfully except for DSP2, so I ended up with the same result. I went back and forth between V15 and V52, using different load methods, but the DSP2 mismatch error persisted. When loading the V52 DSP2 module, the progress bar made it all the way to 100%, but it then paused differently than other modules, then showed a "Successful" message. But as I stated above, the unit still has the DSP2 mismatch error and EMO-Q doesn't respond. I reset the unit back to "default" too, but that didn't help. Is there anything else I can do at my end, or have I exhausted those options and I need to send it back to Emotiva? Thanks! - Dave |
|
|
|
Post by Soup on Dec 20, 2017 9:10:04 GMT -5
Sorry to hear that didn't fix your problem. If its under warranty, send it in. If not, does any version of the firmware work. You may not notice any difference if you go back to an earlier version of the firmware. YMMV.
Or you can wait for after the holidays when a lot of great equipment will be available on the second-hand market.
Personally, I sold my UMC-200 back a few years ago.....its replacement has been working PERFECTLY for a couple of years.
|
|
|
|
Post by scubadave on Dec 20, 2017 9:25:54 GMT -5
Sorry to hear that didn't fix your problem. If its under warranty, send it in. If not, does any version of the firmware work. You may not notice any difference if you go back to an earlier version of the firmware. YMMV. Or you can wait for after the holidays when a lot of great equipment will be available on the second-hand market. Personally, I sold my UMC-200 back a few years ago.....its replacement has been working PERFECTLY for a couple of years. Great feedback and great ideas! I'll see if I can get good firmware files between V15 and V52 and see if I can get one to stick. I originally had V39, so that one may work. Thanks! |
|
KeithL
Administrator
Posts: 9,929
|
Post by KeithL on Dec 20, 2017 15:14:42 GMT -5
Unfortunately that's about it from your end. (We can load the individual modules directly to the appropriate boards - but that takes hardware programming stuff.) It's time to think about sending your UMC-200 in for service. (You could keep using it with v.15 .... but it did have quite a few bugs.) Keith, Thank you for providing the V15 firmware - I was able to install it successfully and without any errors. I was then able to install V52 successfully except for DSP2, so I ended up with the same result. I went back and forth between V15 and V52, using different load methods, but the DSP2 mismatch error persisted. When loading the V52 DSP2 module, the progress bar made it all the way to 100%, but it then paused differently than other modules, then showed a "Successful" message. But as I stated above, the unit still has the DSP2 mismatch error and EMO-Q doesn't respond. I reset the unit back to "default" too, but that didn't help. Is there anything else I can do at my end, or have I exhausted those options and I need to send it back to Emotiva? Thanks! - Dave |
|
|
|
Post by scubadave on Dec 20, 2017 16:22:24 GMT -5
Unfortunately that's about it from your end. (We can load the individual modules directly to the appropriate boards - but that takes hardware programming stuff.) It's time to think about sending your UMC-200 in for service. (You could keep using it with v.15 .... but it did have quite a few bugs.) Keith, Thank you for providing the V15 firmware - I was able to install it successfully and without any errors. I was then able to install V52 successfully except for DSP2, so I ended up with the same result. I went back and forth between V15 and V52, using different load methods, but the DSP2 mismatch error persisted. When loading the V52 DSP2 module, the progress bar made it all the way to 100%, but it then paused differently than other modules, then showed a "Successful" message. But as I stated above, the unit still has the DSP2 mismatch error and EMO-Q doesn't respond. I reset the unit back to "default" too, but that didn't help. Is there anything else I can do at my end, or have I exhausted those options and I need to send it back to Emotiva? Thanks! - Dave Can you provide the V39 and V47 firmware files (or any others you would recommend)? I'd like to see if either of those will load without error, and either of those would be better than V15. Hat tip to Soup for the suggestion. I already responded to the email that sent the V15 file, requesting V39 and V47, so you may be asked about it. Thanks for the great help! |
|
|
|
Post by scubadave on Dec 23, 2017 10:12:15 GMT -5
I want to take a minute to close the loop on this thread I started. My latest efforts involved loading various firmware (V15, V39, V47, and V52). The DSP2 module in the firmware is identical in V39 through V52, so as expected, the DSP2 Mismatch error occurred with each of those loads. To get through the holidays, I loaded V15 in hopes of some stability, but that's not working well. My UMC-200 gets worse each day and I have less functionality.
I will call Emotiva on Tuesday with plans to have it sent back for repair. All this time I was assuming my 5 year warranty had expired, but I discovered yesterday that I literally have "days" left on that warranty in January 2018. Big relief!
Big thanks to everyone who commented and helped me, especially Keith.
Happy New Year's!
|
|
