Need help with restoring License eeprom Lecroy 7200A Wavepro - Page 1
Forum section: electronics / testgear

author: steven4601
author_rank: Contributor
timestamp: April 21, 2018, 07:58:32 am
content: Dear all,I bought this (used) scope about a year ago in a rather bad period (health-wise) of my life , to keep my mind from wandering the dark alley's...Been fairly happy with the unit , Installed the Ipad retina screen, upgraded the mainboard , gave her a good clean. Even called around to order some license options for serial decode , but those are way too expensive to justify for private/hobby usage.(3 to 10k for some options, paid 4k for the scope already)Today I decided to fumble with something I shouldn't have. License keys ... (I really wanted USB 2 time base and serial/spi/can for fun) After a few tries the scope locked up...Too keep it simple, the DSO software detects a fault, and no longer boots.For the usual first aids, I t reinstalled the DSO package, tried turning it off and on again too..I think its bad, as in EEPROM bad ... Not even sure where the EEPROM is located for it.I am willing to accept a loss, I shouldn't have been messing around with this. Will be quite sour and hard to digest though.If someone knows a way to undo messing around with license keys id be really grateful.

author: ollopa
author_rank: Regular Contributor
timestamp: April 21, 2018, 08:56:18 am
content: PM sent.

author: steven4601
author_rank: Contributor
timestamp: April 22, 2018, 07:39:04 am
content: Scope is restored ! thanks !!!Topic can be closed.

author: mos6502
author_rank: Frequent Contributor
timestamp: April 22, 2018, 08:30:02 am
content: So you're not going to explain what exactly happened?

author: steven4601
author_rank: Contributor
timestamp: April 22, 2018, 06:55:46 pm
content: I messed up big time playing with the scope in the service menu / entering things I should not ...But the 1-wire eeprom was recoverable. by making an Arduino 1--wire programmer to remove the bad data

author: xemax
author_rank: Contributor
timestamp: April 23, 2018, 08:37:57 am
content: For Lecroy options show this thread:https://www.eevblog.com/forum/testgear/lecroy-options-recovery/

author: ollopa
author_rank: Regular Contributor
timestamp: April 23, 2018, 12:27:14 pm
content: The irony, xemax, is that thread is what got his box bricked in the first place.

author: darkstar49
author_rank: Frequent Contributor
timestamp: April 23, 2018, 08:52:59 pm
content: it is indeed not always very clear what options to choose... always best check on Lecroy's site, and don't activate something that is not mentioned explicitly for your scope (either in the scope's data sheet, or in the option's data sheet when it exists...)Although not very clear why enabling options required the service menu... there's absolutely nothing in there to play with options (excepted to erase some...)

author: Mechatrommer
author_rank: Super Contributor
timestamp: December 16, 2018, 03:05:23 am
content: Quote from: darkstar49 on April 23, 2018, 08:52:59 pmsorry to break the silence i'm in the learning business right now. but for anyone in the future to make sure, all (or some?) of the options available to the WavePro 7000 Series (aka WP7K) can be seen here at the end of the manual...https://www.atecorp.com/atecorp/media/pdfs/data-sheets/lecroy-wavepro7000-series_datasheet.pdfso you have a high risk trying to activate something thats not in there, including the mentioned USB2, HDMI,SAS etc... fwiw...

author: little.tesla
author_rank: Regular Contributor
timestamp: March 06, 2019, 10:44:09 pm
content: Hello,Sorry for resurrecting this thread again from its grave.Unfortunately I made the same mistake with my waverunner Xi and I would be very thankfull if somebody could point me in the right direction to reset the options.Any help is very apreciated.Thanks and regards,DI

author: mldevw
author_rank: Contributor
timestamp: March 15, 2021, 11:15:41 am
content: Hi,I am also sorry I did the exact same mistake and bricked my (all new to me) WaveSurfer 343.I can build a OneWire Interface with arduino no issue. May I have some hints where exactly to look / what to change on the eeprom to get my old licenses back? I have a screenshot of them.Thanks a lot in advance.

author: DaJMasta
author_rank: Super Contributor
timestamp: January 21, 2023, 02:59:40 am
content: Would have been helpful to share some info on how/what you do rather than just posting that it was solved, but let's see if we can get to that point again:I've got a WavePro 7300 that had no hard drive, I've been able to install an OS, system drivers, the X-Stream software, and the requisite driver packages, but when I boot the X-Stream software, it gives me the "No hardware detected, not authorized to run on this system" message, even though the drivers for the PCI card and all subsequent components have been sorted. I see the same error when I pull the PCI interface card entirely.Well I assumed that the DS2433 eeprom on the PCI card was bad, so I desoldered it, mounted it on a carrier, and had at it with the arduino sketch and.... well it still has data, though some of it is certainly not alphanumeric (not sure if this is correct formatting). As I haven't seen the output of a working one, I don't know if this data is corrupted or if it's just fine and the fault lies elsewhere, so if there's someone who knows or who has an eeprom to compare it to, mine is included as an image, since some of those early characters evidently can't be pasted in a post (short line is ROM ID, second line is "flash" contents).

author: ollopa
author_rank: Regular Contributor
timestamp: January 23, 2023, 01:17:24 am
content: Quote from: DaJMasta on January 21, 2023, 02:59:40 amYour DS2433 is fine. You're able to read it and it contains your licenses:QuoteThe "No Hardware Detected" / "Not authorized to run on this system" error is not related to the contents of your EEPROM, as you observed. This message pops up before the contents are examined and I would say you either have a driver issue or something has gone wrong with your PCI interface card. This error means that the XStream software wasn't able to communicate with the hardware and determine the scope id. Recent versions of XStream/Maui software go looking for a Maui Studio license at this point.. Maui Studio is the productization of the simulation mode that allows you to run the firmware without being connected to hardware. You can't capture any real data but you can analyze data captured on a real scope and simulate measurements. Cool as it is I don't know how useful a feature the simulation aspect is..Anyway my point is that it's not talking to hardware, hasn't read the scope id, and can't even think about reading the contents of the EEPROM yet. You need to look elsewhere.

author: DaJMasta
author_rank: Super Contributor
timestamp: January 29, 2023, 06:09:30 am
content: Thank you, I've made some progress with it.I put the DS2433 back on the board and replugged it, the OS only saw a single LeCroy device attached, so I reran the driver installation package, and though the same had been successful before, it seemed to take better this time, and I've gotten past that error. In fact, for practical purposes, the scope works, oddly except for the options.The scope interface boots up, starts acquiring, can be recalibrated through the service menu, and appears to allow all normal control and operation, except that it has no options listed in the utilities -> options tab, and the ScopeId is ffffff-c4, even though the serial number is now displayed correctly and matches the back of the unit (also IDs as a 7100, but I assume this is just a bandwidth license thing)Now the weirder part, I update XStream to 8.1.2.0 I had the touchscreen configured and working, but it seems to have stopped working - and the device manager is back to a single device... so I go to reinstall the drivers. Everything reinstalls correctly except for one "Multifuction Device" which I manually point to being a "LeCroy Data Acquisition Device" and it installs without complaint... and even though the port showed up as installing, it seems to be absent on reboot.I'm going to have to swap PCI slots and see if it makes a difference and then maybe try taking a look at the PCI board itself - it seems to work fine on one hand, and then seems to be up to something on the other.

author: ollopa
author_rank: Regular Contributor
timestamp: January 29, 2023, 09:53:18 am
content: I don't know what's going on with your acquisition card driver disappearing but as for your scope id, you haven't reinstalled the DS2433 correctly. Make sure it's not backwards and doesn't have any solder bridges.

author: nctnico
author_rank: Super Contributor
timestamp: January 29, 2023, 02:14:44 pm
content: Try to clean the card and the PCI / AGP slots using alcohol / IPA / ethanol. I used some thick cardboard soaked in ethanol to clean the contacts in the PCI and AGP slots on my 7200A. Don't use contact spray!

author: hpw
author_rank: Frequent Contributor
timestamp: January 29, 2023, 06:11:09 pm
content: Quote from: nctnico on January 29, 2023, 02:14:44 pmAs long his ScopeId is ffffff-c4 , no deal with his current optionsas may running as a demo model only...CheersHp

author: nctnico
author_rank: Super Contributor
timestamp: January 29, 2023, 06:40:36 pm
content: Yep. If the acquisition card isn't recognised, the software will run in demo mode. Gettting the acquisition card going is priority number one. The problem is that the acquisition card and the AGP video card don't quite adhere to the size requirements. On top of that, the casing of this oscilloscope is used to keep the card in place so any mechanical pressure/force that is or has been on the top cover, is transferred directly into the motherboard. Cleaning the acquisition card & PCI slot is the only thing you can try really. I don't think any chips are broken; it is just a contact problem.

author: DaJMasta
author_rank: Super Contributor
timestamp: January 31, 2023, 05:49:08 am
content: Well I've tried now reseating the card, cleaning the contacts with IPA (why not contact cleaner, I've deoxit at the ready, though I'll admit they don't look like they need it), and even changing PCI slots. No difference with the ScopeID or touch panel usage, for whatever reason, though I got some weird color problems and a totally normal boot when I reseated the AGP card the first time.I feel like at least for my symptoms, people are on different pages. At least with this system, it's not booting into demo mode - the waveforms displayed are read from the input BNCs and ranges/coupling/timebase settings and the controls respond properly (it even self calibrates correctly through the service menu). Right now my only issues are the ScopeID being misreported, which I believe is the cause of no options existing in the software (though perhaps there's one failure that's causing both), and the touchscreen not being found. The touchscreen worked properly under XStream version 6 but appears to have stopped working since upgrading to 8. In other observations which probably aren't faults: in the device manager after fully installing appropriate drivers for the PCI card, it only shows up as a single device (Multifunction DSO device or something), even though it's nearly a dozen different elements on install. Switching PCI slots causes all to be reinstalled (correct behavior), but the second slot is tight enough of the wiring loom I wouldn't want to just leave it there without redoing the looming. Worth noting that the serial number in XStream is reported correctly even when the ScopeID isn't, and it identifies as a WP7100, even though it's a 7300 (probably an option not working/being read, if I were to guess). For completeness, I'm using a clean XP install since this unit arrived without a hard drive. I installed the OS, the motherboard drivers, the UPDD drivers, XStream 6, then XStream 8, and the WP7200 driver package a couple times in between to be sure.In any case, I'm wondering about a couple of specific things that I hope someone has insight into:Where is the ScopeID actually stored? Is it part of the DS2433 on the PCI card? On the acquisition board? On the fan controller/display board? Something generated or stored by XStream? If I can pin down where it is, I should be able to troubleshoot why it's not being retrieved.Is it possible to manually force a 'refresh' of the ScopeID/options/serial number information? In some service menu panels and in the registry, it seems to mention that data being cached, so I'm wondering if there's a way to convince it to reread the data in case it was bad before and that data was stored without retrying. In the registry there's one short value (8 hex characters, just shy of a ScopeID), and one long value that looks approximately like the dump of the DS2433, a few lines of data and then all zeroes, should these be the contents read from the PCI board? Are they unrelated? Should I delete them and see what repopulates?Otherwise I think my next course of action is to poke around on the PCI card. Voltages appear normal and no chips are cooking themselves. There's a MAX232A up near one of the ribbons that I think is the transceiver for the touchscreen that I can probe to see if there's activity, and for whatever reason (different kind of part used once?) the footprint for the DS2433 has traces routed to most pins - odd for a one wire device - so I could probe the pins I know it uses for data to see if anything's being read as a starting point. I could pull the acquisition board and start checking too, but from failures I've seen there... it would report other issues while booting. I can also read board version information correctly from the service menu, so I think the control FPGA and the basic housekeeping stuff on that board is all happy.

author: ollopa
author_rank: Regular Contributor
timestamp: January 31, 2023, 06:52:11 am
content: 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. This isn't the case for the Zi scopes, however, which do appear to have software limited BW that can be uncapped with a bit-flip. The scope id is not cached on disk or anything like that, it is read from hardware on every launch of XStream. You seem to have a physical problem with the DS2433. The screenshot you posted was fine but now your acquisition card can't read from it, so something is damaged, shorted/bridged, installed backwards, open, etc. There's nothing relevant going on in the registry that I can think of. If you post the keys you're looking at maybe I can tell you what they are.

author: DaJMasta
author_rank: Super Contributor
timestamp: January 31, 2023, 07:47:21 am
content: 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.eEven 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.

author: nctnico
author_rank: Super Contributor
timestamp: January 31, 2023, 10:33:31 am
content: Quote from: ollopa on January 31, 2023, 06:52:11 amFor 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).

author: hpw
author_rank: Frequent Contributor
timestamp: January 31, 2023, 01:59:08 pm
content: Quote from: DaJMasta on January 31, 2023, 07:47:21 amAs 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...

author: DaJMasta
author_rank: Super Contributor
timestamp: February 01, 2023, 04:58:51 am
content: 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.

author: ollopa
author_rank: Regular Contributor
timestamp: February 01, 2023, 05:42:10 am
content: 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.

author: hpw
author_rank: Frequent Contributor
timestamp: February 01, 2023, 11:58:16 am
content: Quote from: ollopa on February 01, 2023, 05:42:10 amWell, this comes to my conclusion, that no ScopeId is stored on that EEProm or I am wrong as only license keys stored?As long this ScopeId is is wrong, no deal to decode the options keys.

author: hpw
author_rank: Frequent Contributor
timestamp: February 01, 2023, 01:25:06 pm
content: Quote from: tv84 on February 01, 2023, 12:24:33 pmWell, any hint where the 3 ScopeID digits are placed, as EEProm location asExample 1:ScopeId =x1x2x3 [?] = x1; [?] = x2; [?] = x3 really address as on EEProm... or are the ASCI coded as the options?Example 2:As from a different DSO dump: The Scopy ID is complete incorrect00000000 F0 00 00 01 02 00 00 02 00 00 FF FF 00 00 42 38 ð.............B800000010 34 33 39 36 41 38 36 38 43 31 34 43 42 34 00 01 4396A868C14CB4..

author: tv84
author_rank: Super Contributor
timestamp: February 01, 2023, 02:45:30 pm
content: Quote from: hpw on February 01, 2023, 01:25:06 pm1. The options have ScopeID inside (the correct one).2. Where did you get this dump? Place here the whole dump (or via pm).

author: ollopa
author_rank: Regular Contributor
timestamp: February 01, 2023, 04:50:01 pm
content: Sorry hpw, I joined this thread to help DaJMasta fix his scope, not explain to you about the scope idTry shorting your EEPROM data line to GND or pulling it high with a small resistor and see what happens. An inquisitive mind with the reading skills of a bassoonist should be able to figure it out if he tried a bit.

author: hpw
author_rank: Frequent Contributor
timestamp: February 01, 2023, 06:11:37 pm
content: Quote from: tv84 on February 01, 2023, 02:45:30 pm1) YES this known.... so the ScopeID reading from the first or any options key??2) This was already given within "LeCroy Recovery" thread. In addition the mentioned EEProm Reset ToolSo as @ollopa mentioned, if the the contents is marked as trash, now way to clear the contents and enter the options key as from scratch.This is IMHO all very scare as looking about a dog

author: DaJMasta
author_rank: Super Contributor
timestamp: February 04, 2023, 05:40:53 am
content: Well, it appears ollopa was right on the money - it took me some time to get back to it, but I reflowed and reinspected the chip, reconnected the card and cables, and it read as a 7300 with the correct options! I've also removed the fan controller/touchscreen controller board and basically just wiggled the touchscreen flex connector and the screen calibrates again. I will be applying some hot glue to some connectors internally, and will need to test a couple more times, then put the top back on and shake it around good and test again, but it appears my problems have been solved.I've seen other intermittent faults with contacts and whatnot on these scopes before (this one even wouldn't boot until the RAM was reseated), but I wonder if this unit was dropped or something - it seems like quite a few contacts were slightly ajar and I don't see any signs of corrosion or a humid environment or something.As for the incomplete EEPROM dump, I used the onewireProxy sketch, but had modified the read function to use Serial.print instead of Serial.write, since it allowed for me to define the output over serial as hex instead of just as a character, and I wonder if the timing of returning two characters through that interface messed with the timing of reading from the onewire interface. I doubt it was significant delay in the reading of it from the MCU's side just because the functions seem to only read until the dump is complete, and since the bit-banging of the Arduino's onewire interface is already going to be substantially lower data rate than the EEPROM is capable of. I reworked the sketch to instead do two separate operations - one reading everything into an array, and then a second returning it all to the serial port - so if that was the problem, it would be worked around (and the original sketch appears to be written for absolutely minimum hardware, so there's plenty of memory available), but since I didn't have to remove it to inspect it, haven't tried the new variant.I'd rather not keep the top off for too many more days, but if it would be helpful to try and get a complete 512 byte dump of the EEPROM, now confirmed working, let me know and I'll try and make a complete copy.

author: ollopa
author_rank: Regular Contributor
timestamp: February 04, 2023, 06:54:53 am
content: I'm glad you got it repairedI have no need for a dump -- there's nothing it could reveal that I don't already know. So I say button it up and enjoy!

author: hpw
author_rank: Frequent Contributor
timestamp: February 05, 2023, 02:04:59 pm
content: Quote from: DaJMasta on February 04, 2023, 05:40:53 amHmm, did you used any python scripts running on target W2K/XP system, so I get any chance to dump it once..

author: DaJMasta
author_rank: Super Contributor
timestamp: February 05, 2023, 11:34:23 pm
content: Nope, no python scripts whatsoever. I just used an arduino and connected up the DS2433 to it out of circuit, then used a sketch that used the OneWire library to read from it.

author: MBla56
author_rank: Newbie
timestamp: June 04, 2025, 10:41:39 am
content: Hello, everyone.I hope somebody will notice my new post on this quite old discussion.I ask your support to solve a problem of scope lock up, similar to that encountered by steven4601, little.tesla and mldevw, but probably caused by a little different circumstances.I have a LeCroy WavePro 7100 scope (not version “A”), Win 2000 NT operative system, with firmware update 6.8.1.4 (build 169683) and:• Hw options: -L (acquisition memory), FE2 (front-end)• Sw options (default for fw 6.8.1.4): JTA2, XDEV, XMAP, XMATHFollowing the indications contained in the “Lecroy options -=recovery=-” topic,(https://www.eevblog.com/forum/testgear/lecroy-options-recovery/?all)I made several trials and successfully enabled several additional sw option packages, just for fun and for hobby investigation.I tried to add, one after the other, only “suitable” options for a WP 7k scope and experimented some one that seemed “reasonable”.All went well, new capabilities were added, and the scope was working fine.Entering the Service menu (with “Developer” privilege), I was also capable of disable (cancel) some useless/not-working options that I tested for trial; all OK.When I was sufficiently satisfied with the selected options (mainly about Serial Data Analysis and Decode, DMOD, Spectrum), I decided to simplify the quite long list of option keys loaded on the scope (DS2433 EEPROM), trying to group together those with the same “flag”, using the relevant “mask” to generate the corresponding single option key.To achieve this, I started deleting the newly added single keys in order to reinsert later the groped ones.In the “Developers” Service menu (tab More Options), you may select each option key (one at a time) and push the “Remove Key” button, after which a Win-window appears asking you to reboot the XStream sw for the removal to take effect (“Yes” / “No” choice buttons).I repeated the procedure several times, once for each key to remove, and each it takes a couple of minutes to reboot.Considering that I had to remove more than a dozen of keys and I was soon bored to wait minutes each time, I tried to take a shortcut: answering “No” to each single request of re-booting XStrem, pressing again“Remove Key” on the other keys that I wanted to remove and then “Yes” only at the end.Doing this bring the scope to lock up (multiple key removals without rebooting XStream between each removal).I am reporting this to advise others not to repeat the same mistake!The XSteam sw crashed with a Fatal Error message, not allowing me to restart the scope application (neither after power-off power-on cycling all the instrument).At this point, I tried to reinstall (from the beginning) the fw update rev 6.8.1.4 (last available on Teledyne/LeCroy site for WP 7k Win-2000 OS scopes; launching “xstreamdsoinstaller_6.8.1.4.exe”), but the following error message appears:XStrean detected a fatal error - Internal inconsistency - Source: CommMsgExecs.cpp - Summary 80070057 (etc.).I loaded all the requested drivers using the executable “AlddinDriversInstaller.exe”, but an error message says:Error: Drivers failed to be updated, reboot the scope and try again (Error 0x2)Rebooting the scope demonstrates useless.Ignoring the driver issue, the fw installation completes, but after PC reboot the XStrem application crashes:Error - No Hardware detected (1) - Not authorized to run the system (plus a long hex code)I haven't (yet) inspected the contents of the DS2433 EEPROM on the PCI interface board, but (as suggested by ollopa) the problem should be elsewhere.I suspect that the XStream sw installation requires to read some scope identification data (Scope-Id ?, scope s/n?) from the hw boards mounted on the instrument (via I2C or other internal links). Where exactly?Here is where my scope is now blocked (I guess).In a second phase (after sw installation), each time you switch on the instrument and the XStream is automatically launched (or you manually doble-click the “start DSO” icon on the PC desktop), a verification procedure occurs checking the paring of hw detected scope-Id (explicit or decoded from another hw identification code) with the one implicitly contained (encrypted) in the encoded option keys inside the DS2433 EEPROM (on PCI board).I think that now my blocked scope fails to get scope-identification from hw and so it cannot compare/verify with the EEPROM stored one.Anyway, my problem arose from deleting option keys without rebooting the XStrem sw (EEPROM access to cancel keys and possible corruption due to lack of rebooting).I guess that no other (independent) hw failure occurred (by chance) at the same precise moment...As some of you appear to be very skilled and knowing many details on these scopes, I would be very grateful if you may give me some hint on how to re-establish normal working of the scope (fw installation, driver selection, Registry correction, how to force the reading of scope identification from hw boards, etc.).Correction of possible EEPROM corruption for added option keys is of secondary importance.I would prefer not de-soldering the EEPROM from PCI board, if possible, just to discover that what is stored there it’s all ok. At least, not doing that for nothing if the problem is possibly located elsewhere.If some of you (as it seems) is not happy with disclosing some sensible information on the open blog, I am ready to provide you with my personal e-mail address for direct exchange of possible hints.Best regards,Mario B

author: ollopa
author_rank: Regular Contributor
timestamp: June 05, 2025, 02:10:28 am
content: I think it's just a coincidence. I've never had a problem removing multiple options without rebooting in-between. Have you checked the Device Manager in Windows for the presence of the Aladdin acquisition board and that there are no errors reported by the driver? "No Hardware Detected" means that XStream couldn't talk to the PCI card.

author: MBla56
author_rank: Newbie
timestamp: June 05, 2025, 09:35:39 pm
content: Quote from: ollopa on June 05, 2025, 02:10:28 amGood to know!About coincidence: it may be, but it seems quite unlikely to me that it happened exactly at that time.Probably I was misleading using the term reboot. The step that I jumped at each key removal was: exit XStream sw and restart it (Not reboot all the PC inside the scope!)Quote from: ollopa on June 05, 2025, 02:10:28 amAs mentioned (may be not very clearly), I face problems during the repeated installation of the firmware (xtreamdsoinstaller_6.8.1.4.exe).At about one half of the installation process, a new window announces the loading of DSO drivers and that the process will take several minutes. Several drivers are reported as correctly loaded (of diffeerent types: PCI boad, Multifunctional device - with several different icons-, fan controller, etc.), except one that fails with the following message:AladdinDriversInstaller.exe - Error: Driver failed to be updated. Reboot the scope!Rebooting the scope doesn't solve the problem.But, if I ignore the problem and continue (no other choices are available to me...), the installation procedure goes on and completes up to the end without oter complains. After rebooting all the scope and auto-launching "Start DSO" the XSteam sw crashes with theInternal inconsistency error message (source: CommMsgExecs.cpp).Exiting to Windows and launching Computer Management \ Device Manager, apparently non error advices are show (yellow triangles wit question mark). But, opening "Data Acquisition Devices" (two of them, but with different icons), a message on the "General" tab advices that no drivers are installed for those two devices. the "Driver" tab is more trichy: "Unkown device"; no drivers are required or have been loaded for this device, but LeCroy provider and version are shown (?!)Pushing the buttons "Update Driver", "Next", "Search for suitable driver...", "Specify location" (C:\Program Files\LeCroy\XStream\Drivers seams to me the obvious choice), "OK"; the selected (found) driver becomes C:\winnt\inf\oem40.inf. Puching "Next" the Scope PC reboots, but then XSTream continue to crash and Windows Device Manager continues to show "Unknown devices". Trying the othe option in the "Driver" tab, "Update driver", "Next", ", "Display the list of the known drivers...": the selected one is respectively "LeCroy Acquisition Device (S65)" and "LeCroy Pichu driver" (for the two unknown devices). Answering "Continue" the scope shows very rapidly a blue screen with some messages (that seems to me like the BIOS screen), then a black screen with white messages (that seeme to me like the DOS cmd window), but it happens so fast that I am not capable to confirm or read something. They are soon followed by PC reboot, "start DSO" autorun and again XStream crash.Hereafter I try to show some pictures taken from the scope screen.(other will follo in next message ...)

author: MBla56
author_rank: Newbie
timestamp: June 05, 2025, 09:41:59 pm
content: ... other screenshots ...

author: MBla56
author_rank: Newbie
timestamp: June 05, 2025, 09:45:25 pm
content: ... and others ...

author: MBla56
author_rank: Newbie
timestamp: June 05, 2025, 09:46:40 pm
content: ... last.

author: coromonadalix
author_rank: Super Contributor
timestamp: June 06, 2025, 01:34:49 am
content: ds2433 are one wire eeprom, normally you should be able to read and write into it, some interfaces exists, normally i would held in reset the system and read iti have modded almost all the language in english for the ds2433 software, but you will need an 1wire interfacehttps://www.eevblog.com/forum/projects/dallas-ds2433-software-modded-in-english-searching-for-an-ds2431-equivalent/

author: ollopa
author_rank: Regular Contributor
timestamp: June 06, 2025, 06:35:04 am
content: I think you are selecting the wrong drivers for the WP7100. Pichu is a driver for a PXI module and S65 is the driver for the WR6K scope.Try the Aladdin driver inf file(s) and don't manually choose the driver, let it match the correct driver based on the PCI vendor and device id.

author: MBla56
author_rank: Newbie
timestamp: June 06, 2025, 07:50:37 am
content: Thank-you very much for your precious answers. I will do some trials with them.Quote from: coromonadalix on June 06, 2025, 01:34:49 ama) do you mean I have to procure the USB to 1-wire Dallas interface mentioned in the post of your link?b) what do you mean "held the system in reset (and read it)" ? That I may have access to the data contents of Dallas EEPROM while it is still mounted on the PCI board, live on the scope? I thought that the 1-wire USB interface is intended to be used on (another) PC, running the 1-wire programmer sw (the file attached to yor post), and the DS2433 isolated chip. Is it correct?Quote from: ollopa on June 06, 2025, 06:35:04 amI tried two approaches:a) "Search for a suitable driver for my device . The Win-2k automatic choice was "C:\winnt\inf\oem40.inf": Not working!b) "Display a list of known drivers for your device so that I can choose a specific driver". I selected the folder "C:\Program Files\LeCroy\XStream\Drivers" and the Win-2k automatic choices were respectively: "LeCroy Acquisition Device (S65)" and "LeCroy Pichu driver". Not working!.Shell I manually select another folder (different from "C:\Program Files\LeCroy\XStream\Drivers") ? or force the selection of a particular driver in that folder?The file list on that folder is the following: