EEVblog > EEVblog Specific

The Dark Side of the Rigol Hack -- Bricked Scope & How to Fix it...

(1/37) > >>

drieg:
The purpose of this thread is to help/support people with their broken Rigol DS1052E scope.

The most common problem is totally dead scope after unsuccessful firmware "downgrade/upgrade". The only way to recover it is to reprogramm the flash chip (Spansion S29GL064N90TFI04) either via BlackFins's JTAG interface or in external programmer. There is very important part inside the flash with the factory calibration data, which is unique to every unit. These data has to be preserved in a new flash image for proper operation.

Second common issue is partially working scope, which doesn't shows signals correctly after a 100MHz patch (see story of shafri and others for details). These problems are caused by corrupted factory calibraion data which may get corrupted probably when patching via serial cable (especially if you accidentally hit the ENTER instead of sending correct <LF> char). This is the reason, why I strongly recommend: DO NOT USE SERIAL CABLE!

Some people ask me about how to hack scope HW version "xy", FW version "xx.xx.xx". The fact is, that different firmware supports different HW version, so there is always some risk when you are running the FW that doesn't support your HW version. Please don't ask me if it's safe to downgrade to FW 02.02, if you have HW version "57" or "58" - I don't know

Here's the table which FW supports which HW. Higher FW supports all older HW versions.
HW version    FW version5800.02.04.01.005700.02.04.00.030700.02.02.02.00

WARNING: Do not experiment with undocumented SCPI commands especially if you don't know the correct syntax. You can corrupt or lost some of imortant calibraion data!


Repair history
repair date        model        (nick)name              details 08/28/2010 DS1052E lynx / SE bricked after unsuccessful FW upgrade 10/08/2010 DS1052E dimlow / UK corrupted calibration data (same as shafri: problem description) 10/08/2010 DS1052E shafri (Mechatrommer) corrupted calibration data (problem description) 09/20/2010 DS1052E jasper / US bricked after unsuccessful FW upgrade 09/26/2010 DS1052E Ben / AU bricked after unsuccessful FW upgrade 10/26/2010 DS1052E Viktor / BY bricked after unsuccessful FW upgrade 10/27/2010 DS1052E Giovambattista / IT bricked after unsuccessful FW upgrade 11/02/2010 DS1052E mainer / AT bricked after unsuccessful FW upgrade 11/03/2010 DS1052E Larry / US bricked after unsuccessful FW upgrade 11/22/2010 DS1052E Peter / AU bricked after unsuccessful FW upgrade 11/23/2010 DS1052E teixeluis corrupted calibration data (problem description) 01/03/2011 DS1102E Mohammad / IR bricked after unsuccessful FW upgrade 02/02/2011 DS1052E Chris / US bricked after unsuccessful FW upgrade 02/03/2011 DS1052E Mel / UK bricked after unsuccessful FW upgrade 02/06/2011 DS1102E Marlon / US bricked after unsuccessful FW upgrade 02/11/2011 DS1052E nasser32 corrupted calibration data (same as shafri: problem description) 02/21/2011 DS1052E Brian/ US bricked after unsuccessful FW upgrade 03/09/2011 DS1052E David / AU bricked after unsuccessful FW upgrade 04/28/2011 DS1052E Denis / RU bricked after unsuccessful FW upgrade 05/05/2011 DS1052E Hans / NL bricked after unsuccessful FW upgrade 06/01/2011 DS1052D Rob / NL corrupted calibration data  06/29/2011 DS1052E Andres / ES bricked after unsuccessful FW upgrade 10/01/2011 DS1052E Ray / UK bricked after unsuccessful FW upgrade 10/16/2011 DS1052E Jeremy / AU corrupted calibration data  10/17/2011 DS1052E Doug / US corrupted calibration data  11/24/2011 DS1052E Aleksandr / RU bricked after unsuccessful FW upgrade 04/10/2012 DS1052E Rob / UK corrupted calibration data  ... 02/11/2019 DS1052E Bruzzel / DE wrong firmware flashed 02/17/2019 DS1042C Taras / UA bricked after unsuccessful FW upgrade 02/21/2019 DS1302CA ivi_yak / UA wrong firmware flashed

dimlow:
Well Drieg has certainly got my hopes up, yesterday i required a scope, so i used my Uni-T UT81B, but it didn't quite meet my needs. Cant look at a 20Mhz signal with a 10Mhz Scope! BTW i love this little meter for when im poking about with micro controllers on a breadboard. I guess a should post my views of it in the UT81B thread.

nebarnix:
 :o Drieg, you have really helped me out! I got the chip back yesterday and I think I soldered it back in record time. I couldn't wait to assemble to scope properly and left the power supply hanging off of the table. Guess what, the scope is alive again!! Thank you!!

To everyone else. my scope was broken when I attempted to upgrade the firmware. I Upgraded, rebooted, and them bam... nothing. Blank. I will admit we had a few beers as an old friend was in town so I was sure that somehow I had put the wrong image on the flash drive. I checked and rechecked but all seemed in order. Its not even my scope so it was somewhat embarrassing to do this in front of a bunch of people including the owner of the scope and have to say "Oh sorry... guess you don't have a scope anymore!".

After trying unsuccessfully for several months with a blackfin programmer and a half-built homebrew programmer in VHDL I met Drieg and I sent my poor blank spansion flash chip off to go see Europe and start a new life there. After becoming sufficiently cultured it crossed the Atlantic once more (I believe that it was quite homesick) and it is perfect working condition!  Thanks so much Drieg! I am lucky that the factory calibration data was not erased  :D

-Nebarnix

Waifian:

--- Quote ---Second common issue is partially working scope, which doesn't shows signals correctly after a 100MHz patch (see story of shafri and others for details). These problems are caused by corrupted factory calibraion data which may get corrupted probably when patching via serial cable (especially if you accidentally hit the ENTER instead of sending correct <LF> char). Currently I'm working on a solution how to correct these data without the need of even opening the scope;)

--- End quote ---
Would that include a square wave frome a function generator that appeared as a sine wave on the rigol scope. I didn't know what to think. I am still not sure if it was the function generator or the scope as the scope seems okay... I did run the recalibration tool a few times because I also had the issue of the vertical system being wierd at the 5volt per division mark. It was about a volt below ground with nothing connected and seemed to be the worst at the 5volt per division area. After recalibrating it again it seems okay.... I am not sure if my scope is shoddy now or not...   ???

armandas:

--- Quote from: shafri on September 28, 2010, 03:00:48 pm ---i deleted my previous comment, its nonsense!
pls keep this thread clean guys!

--- End quote ---

What about all other threads in this forum, shafri? ;)

Navigation

[0] Message Index

[#] Next page