General > General Technical Chat
The Rigol DS1052E
shirsch:
--- Quote from: beerhunter on July 06, 2010, 12:54:22 am ---
Now its getting to be more fun. You're right, only using the *IDN command via the RS-232 port does the full revision number show up. My scope is now at firmware 00.02.04.00.03 .
You can now download this firmware version at the USB upgrade for dummies thread. This file was downloaded directly from my USB stick that was used for my scope.
--- End quote ---
At the risk of belaboring the point, has anyone verified that a DS1052E shipped with 00.02.04.00.03 can be successfully "downgraded" to 00.02.02 SP2 ?
Polossatik:
--- Quote from: shirsch on August 11, 2010, 02:41:04 pm ---
At the risk of belaboring the point, has anyone verified that a DS1052E shipped with 00.02.04.00.03 can be successfully "downgraded" to 00.02.02 SP2 ?
--- End quote ---
I just updated the guide for this
Cheshyr:
--- Quote from: halman on June 29, 2010, 07:02:42 pm ---It must have been an incomplete flash. I inserted an usb stick with the firmware and ran it from the menu system, once it was done I restarted the scope, it was then it refused to start up properly. Strange things go on with the button lights they light up randomly and if i do quick restarts they move...it looks kinda like a counter is incrementing.
spansion?
I can reprogram flash memories and eeproms easily enough, if i have to. But I don't know which parts of the .rgl file to place where.. and in what order ...
--- End quote ---
I'm watching this thread too. My symptoms are identical to Halman's. Expensive brick.
Mechatrommer:
we found another "bricker"! maybe rigol has take more evasive action for this hack!
can anybody point me to where i can get Spansion Flash cheaper? i need a spare for my rigol and for testing.
Cheshyr:
--- Quote from: shafri on August 12, 2010, 11:17:30 am ---we found another "bricker"! maybe rigol has take more evasive action for this hack
--- End quote ---
I'm going to blame this one on my incompetence. I didn't get the file or hear about the hack from EEVB. I ended up here after the fact while searching for a fix, only to find a much more rigorous and professional procedure. I did a checksum on my file, and it matches the one stored here. The calibration date was June 2010, which I believe matches with someone else's successful flash. I think it was just a bad flash; nothing indicated a problem with the downgrade.
Either way, I just wanted to see if someone had found a way to force a reflash or fix it somehow. My gut instinct thinks we either need to find a way to access the bootloader so we can trigger a 'factory update', or we need to get a complete image of a working flash, and do a full overwrite. I have no evidence to back this up however.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version