General > General Technical Chat
The Rigol DS1052E
rf-loop:
Read carefully this:
https://www.eevblog.com/forum/index.php?topic=553.0
...and follow it carefully step by step.
(first you need "downgrade" FW to right version for mod (new versions are "modification locked"! (be careful: use exactly right FW version and check it before insert USB stick to front USB connector of scope.)
------------
Also nobody know what time Rigol do next HW/FW versions and they maybe do not accept downgrade FW to 02.02xxxx versions.
(I believe they are thinking it... but also nobody know what is wise for....for what... selling volume is only one point. In every case DS1000E do not kontinue in production long time forward) In every case Rigol name is now more well known as before DS1000E series...
Meiner:
Hello again,
I've desoldered the spansion flash and read out the content (file.rar). Last Action before was downgrading to 02.01.01 (the packed *.rgl file in the attachment). I want to analyze the file to find out, where the *.rgl file has been placed. With this information I hope to be able to replace the 01.01 with a (working) 01.02 or 01.04.
Thans for any comments
Meiner
marianoapp:
i've been looking the files and i think the *.rgl hasn't been placed anywhere.. :-\
the *.rgl has over 2MB worth of content, yet the the other file barely reaches 140KB [not counting the big blocks filled with 0x00 and 0xFF in neither file]
i've also been unable to find anything meaningful or code-like in the other file, except for the model and serial number. The model it's stored at position 0x1FFF40 and in reverse byte order [LSB?], e.g. "SD0125.E"
oh, and the other file content starts all over again at position 0x400000
Mechatrommer:
--- Quote from: Meiner on July 20, 2010, 06:57:48 pm ---I've desoldered the spansion flash and read out the content (file.rar). Last Action before was downgrading to 02.01.01 (the packed *.rgl file in the attachment). I want to analyze the file to find out, where the *.rgl file has been placed. With this information I hope to be able to replace the 01.01 with a (working) 01.02 or 01.04.
--- End quote ---
i agree with marianoapp, i cant find any codelike data inside. by just looking at the flash compressed file 71KB vs original 8MB, your flash only contains a highly redundant bytes with some database/structured/tabular like format chunks inside. maybe your flash got formatted by the bootloader or something... i think.
added: the bin is separated into 2 equal sized 4MB space with a header in each section... the contents are identical except in the middle of 1st section (around 2MB location, some additional data OOOOPPPP..CCCCC where in the same location for the 2nd section, its emptied with FFFFFFFFFFFFFFF ???
this is interesting, @meiner & others... can you suggest a flash reader to me, if the price and availability is right, i think i'm going to get one as well to read my spansion, preferably from ebay, cheaper but reliable. i'm suspecting something from the tabular data in the flash bin, but i think better not to say it for now, only speculating.
ps: i wish a more generic eeprom reader that can read not just spansion, but samsung, atmel etc, so it will be more useful to me, i got quite a number of salvaged samsung eeprom here.
Meiner:
--- Quote from: marianoapp on July 21, 2010, 12:20:27 am ---The model it's stored at position 0x1FFF40 and in reverse byte order [LSB?], e.g. "SD0125.E"
--- End quote ---
You're probably right, the byte order in the file.rar may be wrong. I have no flash reader of my own, so I went to a local dealer who sold some stuff to the company I work for, asked him for some help and he read the spansion's content for me. After reading he told me that the byte order might be wrong and that he could simply flip it. Because I didn't know the right order, I told him not to do so.
@shafri: sorry, I can't remember the brand of their flash reader, but I think it was an expensive one...
I came to the same result: the spansion's content is quite poor. Anyhow I don't think that the *.rgl code is placed in any other non-volatile storage inside the scope, so it should be in the spansion. I have no idea why it isn't. But I guess that's why my scope is definitely doing nothing but blowing the fan.
Next step for me is to find out the correct spansion's content. Maybe I should try to write the *.rgl (without the first 16 byte header) to the lower 4MB and just try it. But on the other hand I can't try this often, because the spansion has no socket.... any suggestions where to get a socket?
Thanks
Meiner
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version