Tariq Bugti

I'm thinking about replacing them. Preferably, everything near the power supplies. Or at least measure them with an ESR tester.

No the successful main firmware update happened through another display panel(including the isolating board) which was working fine. In my inverter's case the isolating board was the reason my firmware updates were getting failed.
Your are right and i am happy to tell you that my issue is resolved, i checked its opto couplers and one of them was faulty, i changed it with a new one and the inverter has come back to life. I did that ealier today, now that you too have shared fixing a similar problem being recified by changing optos. 
My inverter is working fine now, with both main and display firmwares updated.
Thank you very much for your continous replies and help.  
Hope this thread will help those who are struggling with same issue.

Glad it's all resolved and yes the information here will certainly help.

No the successful main firmware update happened through another display panel(including the isolating board) which was working fine. In my inverter's case the isolating board was the reason my firmware updates were getting failed.
Your are right and i am happy to tell you that my issue is resolved, i checked its opto couplers and one of them was faulty, i changed it with a new one and the inverter has come back to life. I did that ealier today, now that you too have shared fixing a similar problem being recified by changing optos. 
My inverter is working fine now, with both main and display firmwares updated.
Thank you very much for your continous replies and help.  
Hope this thread will help those who are struggling with same issue.

I had tried vm3.hex several times it didn't work then i changed the name just to see if it changed anything. Chaning the name didn't make any difference both the times same error was poping up. I don't think that changing file name from vm3 to dsp would cause any change in hex file it self or make it king firmware.

Just a note that we recently flashed some trial software from Voltronics for the king and we were getting error 32 as well. The feedback from the factory was that we had to have solar panels connected because the software changes affect the SCC/MPPT control. So maybe try flashing with solar panels connected in case this is a similar problem?
 

? What do you hope to achieve by that? It only confuses things, and makes it possible to do goofy things like uploading a King firmware into a VM3 machine. That's not going to end well.