Products > Test Equipment
Need help with restoring License eeprom Lecroy 7200A Wavepro
<< < (5/7) > >>
DaJMasta:
Thank you, again.  I will give reflowing the DS2433 a shot (can't see any solder tags and the dots line up) and if nothing from there, I'll try buzzing out the data trace and checking for activity to make sure it didn't get damaged somehow, and then looking at it with a scope in case there's some damage making the read waveform wonky.

Oddly, the cached data has disappeared in the registry, but regedit saved my spot, so it was in HKEY_CURRENT_USER -> Software -> LeCroy -> XStream -> Options -> XStream and it was in a folder name that was encoded somehow starting and ending with a curly bracket.  There were two binary keys in there, the second, longer one, had the format that seemed similar to the DS2433 dump.

I think that may have been the cached info, though, as the XStream root directory in the registry has a cached serial number - this could be explaining why it shows correctly in software but isn't properly communicating with things.
e
Even more oddly, on this boot, the touchscreen responded, but only slightly.  I went to calibrate and 3/5 points couldn't be reached near them on the screen, so the data is wonky, but perhaps the serial port was working properly and there's a connector not making full contact down the line (the flat flex from the screen to the display board is my first suspect).  Perhaps the device reading the screen hangs or doesn't report itself over serial when the sensor itself isn't present, as the driver was reporting nothing presnt on the port (defaults to COM3 regardless of PCI slot or driver reinstallation) in previous boots.  Luckily, it doesn't seem to be related to the version 8.1.2.0 installation.
nctnico:

--- Quote from: ollopa on January 31, 2023, 06:52:11 am ---Your scope id comes from the ds2433.  If it's not reading correctly then neither are the licenses.  Your 7300 comes from the HBW license which can't be read, that's why it decides that it is a 7100.  The WP7K (and WR6K) have analog filters that limit the bandwidth in the front end and the BW option is purely cosmetic as far as I am aware.

--- End quote ---
For the 7k series there is a hardware bandwidth limit as well. You can mod a 7100/7200 into a 7300 but you'll need to replace some resistors / capacitors with a 0 Ohm resistor to get to full bandwidth (and install the 7300 license).
hpw:

--- Quote from: DaJMasta on January 31, 2023, 07:47:21 am ---Thank you, again.  I will give reflowing the DS2433 a shot ...

--- End quote ---

As someone have a valid dump of the eeprom as given ScopID to compare as one license key too...

as the given dump picture, shows in a readable form only valid license keys, no more... or do we need a real hex dump as first dump char's are bogus...
DaJMasta:
I modified the sketch to send hex characters as ascii, then converted it and saved as a binary.  For some reason just sending back didn't want to respond to commands from my default terminal program, so hopefully this suffices.  Should have some time to poke around in the next day or two for the physical parts of it.

ollopa:
Maybe you sketch has a bug or the clock rate is too fast.  It appears there are missing bytes or nibbles, especially values of 0.  First of all the length should be 512 bytes but your dump is only 298.

The beginning two bytes of EEPROM are always 0x01 0x01 and I don't see that in your dump.  Instead I see one byte that is 0x11 -- you've dropped 4 bits of 0 from each byte.

Next comes the count of licenses as a little endian uint16 and you have 5 licenses so the next two bytes should be 0x05 0x00, but you have one byte 0x50 instead.

Next is the block size of 512 bytes = 0x200 which is 0x00 0x02 (uint16_t le). Instead you have 0x02 and are missing the byte of 0x00.

The following pattern in EEPROM  is always 0x00 0x00 0xff 0xff.  I can see the 0xffff pattern in your data but 0x0000 has been reduced to 0x00.  Again, this looks like a bug in your sketch.

Each of your 5 licenses should be terminated with the bytes 0x00 0x01 (and you guessed it, your dump only shows the 0x01 byte)

Towards the end you have this little sequence:  DD 0D F0    This is also missing nibbles.  It should be 0D D0 0D F0.  These are two 16-bit words that spell 0xD00D 0xF00D, a kind of hex-speak joke like 0xDEADBEEF that is used as a marker in the EEPROM to know that the data is valid/this is the start of the section where demo licenses are stored.

So to me it looks like 1) your sketch has a bug but otherwise 2) the contents of your EEPROM are correct.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod