HW version | FW version |
58 | 00.02.04.01.00 |
57 | 00.02.04.00.03 |
07 | 00.02.02.02.00 |
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 (http://www.rcgroups.com/forums/showthread.php?t=1222045&page=3#33)) |
10/08/2010 | DS1052E | shafri (Mechatrommer) | corrupted calibration data (problem description (http://www.rcgroups.com/forums/showthread.php?t=1222045)) |
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 (https://www.eevblog.com/forum/index.php?topic=553.msg24179#msg24179)) |
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 (http://www.rcgroups.com/forums/showthread.php?t=1222045&page=4#60)) |
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 |
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;)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... ???
i deleted my previous comment, its nonsense!
pls keep this thread clean guys!
Like I said in the other thread (https://www.eevblog.com/forum/index.php?topic=553.msg18626#msg18626 (https://www.eevblog.com/forum/index.php?topic=553.msg18626#msg18626)), drieg has a way to fix your scope if you have one that:
- Came with firmware 2.04 SP1
- Has been downgraded to firmware 2.02 SP2 for changing the model number
- Exhibits repetitive noise at high sampling rates after self calibration
- Cannot be upgraded to 2.04 SP1 (because the firmware isn't available to the public yet)
Just post your problem on this thread and drieg or someone else may be able to assist you.
I would assume performing hacks like this will void any warranty so do it at your own risk and preferably after the warranty period has expired otherwise you have to take responsibility for repairing it.i dont think sending legitimate RS232/USB command will void the warranty. for me, it shouldnt. even if we feed with random data, the scope should be well protected from that, as proven by Drieg sometime ago, RS232 comm is not so reliable, so meaning the Rigol design got flaw.
I wonder if someone should approach Rigol and just ask them how they stand on this. It would be interesting to see what they have to say about the hack/ undocumented feature. Its obvious that they know about it.i bet they wont reply. thats their "pant". and they know we keep peeping it, and so they will be busy try covering it. they forgot... thats the thing that makes us interested at them. ;)
I wonder if someone should approach Rigol and just ask them how they stand on this. It would be interesting to see what they have to say about the hack/ undocumented feature. Its obvious that they know about it.
well, the funny thing is the costumes :D if they are wearing the EEVBlog T-Shirt, that will become slightly a different picture. i was about to do that with my Rigol before Drieg comes to rescue.you haven't seen The Best Movie Evaar? (http://www.imdb.com/title/tt0151804/)
you haven't seen The Best Movie Evaar? (http://www.imdb.com/title/tt0151804/)the company where I work is certifying the ISO 9000 (http://en.wikipedia.org/wiki/ISO_9000) standards for quality management systems, so I'm gonna be filling TPS-like reports in no time >:(
In my experience manufacturers take a dim view of any attempted 'hack' of an equipments BIOS.
Could someone of repute, one we can trust to transfer the funds, setup a Paypal donation account for Dreig?
Thanks guys for bringing up this topic.Could someone of repute, one we can trust to transfer the funds, setup a Paypal donation account for Dreig?
The best person to do that is Drieg :)
If you're in the Euro zone then simply ask him his IBAN account nr (do not post it somewhere) and transfer what you want.
In contrast to Paypickpocket (for a $1 donation he will get only $0.67) it will mean that he get actually the amount you transfer and not amount minus 2.2% + $0.30 costs.
- Exhibits repetitive noise at high sampling rates after self calibration
No, I don't have 02.05 FW yet. If anyone has it, I'd be interesing to look at it...
Check my 1st post in this thread for your question. Usually the flash desolder/read/write/solder cycle is needed. The JTAG connects to Blackfin only.
first post, had indicated the blackfin jtag was daisy chained to the flash....
"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."
if you have the tools to do the job. ie. remove the flash, save copy, place a lower version, up the model number ;) , and then return the 02.05 firmware ?
prehaps continue in email ?
if you have the tools to do the job. ie. remove the flash, save copy, place a lower version, up the model number ;) , and then return the 02.05 firmware ?
prehaps continue in email ?
Darrylp,
If Drieg is willing to do the work for you, I would recommend that you not return your scope to FW2.05 unless Drieg finds that the hardware requires it. As you have HW58 it is very likely that FW2.04SP1 will work perfectly with it and you will then have the ability to do further unofficial firmware updates in the future. FW2.05 would appear to be just a countermeasure release, hobbled to prevent unofficial firmware updates. From my understanding, Rigol were not intending to make any significant improvements to the 2.04 firmware. It's your decsion but given the opportunity I would prefer FW2.04SP1 to FW2.05.
Aurora is right, if you have HW58, you should be able to run 02.04 SP1 without problems (after Self-Cal).
Unfortunately the flash dump and the firmware file are two (more or less) different things. Most probably they changed file header and/or implemented some kind of protection/encryption or maybe changed the file structure too. To be able to create working FW file from the flash dump, you have to exactly know how.
I think the only way is to wait until somebody manages to get the oficial 2.05 FW file...
That would be definitely possible, as long as you have enough time, skills and tools to do so... ;)Well, as for me, time and skills enough (retired), just tools missing. May be some cooperation will be useful for all involved?
FW 2.05 appears to be hackable ..........Current DS1052E's come with 02.05.02.00 firmware so the hack for 02.05.01 does not work.
Sorry for my english.
Hi everyone! I live in Russia. I wanted to tell you my story how I killed my Oscilloscope Rigol DS1052E. He came to me with firmware 00.02.05.02., At that time upgrate in DS1102E was impossible. Not long ago there was information about how to do it. https://www.eevblog.com/forum/index.php?topic=553.msg42404#msg42404. (https://www.eevblog.com/forum/index.php?topic=553.msg42404#msg42404.)
In short, I flashed it. ... .. After that it could not run. The mood has fallen. I will not tell you how I did it ...
I turned to Drieg. He told me to read a dump from the chip Spansion S29GL064N90TFI04 and send it back to him. If you’re interested in programming, I had a Triton + V5.7T http://www.triton-prog.ru (http://www.triton-prog.ru). I ordered an adapter for this chip. Not the first time but I managed to read the data correctly. Posted the dump to Drieg. Soon he sent me a corrected dump. I flashed the chip and soldered it in place. After that, my Rigol alive.
I would like to express my deep gratitude to Drieg. Thanks very much to him! The world is not without good people. For more of these ...
@Shafi
.... i was going to test it against my 400Mhz HP54502A scope, but when i turned on my old reliable, she is no longer reliable. It popped up with Calibration Memory checksum error. So i spent quite a few hours trying to recalibrate it and failing, it seems that the old HP is dead now ???
I have since fixed the scope, only needed some new NVRAM!
...solved via PM/email.
we have to find out the hardware version of your unit (from the serial number or better from PCB version) and then we can fix it.
Hi matthewell,
could you post the connection schematic which you have used for jtag and what the software that handles this
Hi equinoxefr,
I think I have the same problem as you did, but I can't seem to find 3.01 firmware file anywhere.
Where did you find it? Do you think you can post a link?
Thanks in advance.
I, too have DEM07.we have to find out the hardware version of your unit (from the serial number or better from PCB version) and then we can fix it.
So, we did this, and it fixed the problem! Restoring the "HardVersion" to 07 (my board was marked "DEM07") allowed me to upgrade to 2.06 without the ADC offset problem that was present before when the field was blank. It seems my assumptions about the software assuming a newer hardware version were correct. My realtrigdelay/equtrigdelay were also wiped to 0 and I decided to also calibrate those -- not sure what I did originally. Thanks, drieg!
Yes, if the unit doesn't start at all, you need to reprogramm the flash either in external programmer or via JTAG (as we did in this case).My bricked DS1052e is all fixed up, huge thanks to drieg.That's not fair!!! leaving us in the dark as to what you did to revive your scope!
Did it involve using the JTAG connection?
Good to hear you got your baby back!
Hello,
I have flash a wrong firmware to my old DS1042C and now it is dead, nothing works. |O
What can I do to fix my bricked scope?
Where can I find information and correct Hex-data for reprogramming the Flash?
The DS1042C board is very similar to the DS1042E Board but has only a S29GL032A flash
(not a S29GL064 flash) and has no second front USB-Port near the serial EEPROM.
The last firmware was 02.03.16.
Can anybody help me?
hiHello,
I have a brick after firmware updating of DS1302CA |O
Could you post a manual for reflash or advice what to do?
Please post any info about repairing of software bricked RIGOLs
Help me.
hxd hex editor :popcorn:I have hxd, for changing the flash file contents, what I meant was software for the actual communication through jtag. Are you perhaps using openocd or some custom software?
topjtagThanks!
I rewrote the single bit errors with data from the RGL file and the scope seems to be working again. I then tried running the firmware update from USB again, and got the exact same single bit errors once more. Something seems to be reproducibly wrong. However, I have now settled for fixing the single bit errors and hopefully that is all that is required. I am unsure why so much of the RGL file is not written to flash?
hi. i need to know what kin of programer i need. which software have to use to program flash via jtag. and do you have the file that i have to program in my oscilloscope?:scared: don't hesitate take a read 6 pages of this thread and you got all what you need to know
Could you advise me on the right configuration to use to read and write the flash memory?
are you sure about the setting that you uploaded? i used your setting and read several time. each time some different datas.
I tried to update firmware on my DS1052E and its got bricked.
Hi,
when I bought my DS1052E, I did the 100mhz hack (over serial) and upgraded the firmware to 02.04. It went all well and good.
Time flies and my first child was born, second child followed and all my electronics hobby dried up.
Yesterday I built up my electronics workbench again and thought it would be a good idea to update the oscilloscope, since there have been a few firmware updates.
Well, or not so well: the firmware update ran, the DS1052e restarted and after short flickering a black screen is the only thing which is coming up.
I currently have no idea how to solve it on my own, and I am afraid to kill of the calibration data by tinkering around on my own.
I sent Drieg a message, but I am not confident if he still fixes boards, since he started this 10 years ago ...
My dump starts to differ very early on, at address 0xFFEB, but I find long chains of bytes from the RGL data scattered throughout the dump. They tend to be on page boundaries. It's very odd to me.
My Program.cs expects there to be a header on the RGL file. That might explain your differences if you removed the header.