Lecroy wavesurfer 3024 fail to boot

[kinero]

I rolled back to earlier firmware and it was OK.

Ollopa - thank you so much for your input. 

To clarify, was the roll-back in your case performed after the so-called "BIOS" update took place?  And if so, did you have to perform factory restore followed by installation of firmware that precedes V9.1.0.3?

Just a note, Teledyne lists the current firmware as V9.2.0.5. I registered and will try this new firmware as soon as my account is authorized.

[kinero]

I reached out to Teledyne support, and they immediately approved my request and provided the newest recovery package with instructions.

This recovery package contains firmware 9.1.0.3 and the keys are working now!

[kinero]

I had the same problem with the licenses no longer being installable with version 9.x firmware.  This seems like a bug in their software.  I rolled back to earlier firmware and it was OK.

Interesting that Teledyne states that the latest software for WX3000 is V9.2.0.5 while the restore package shared above contained V9.6.0.1, and that's the one that disables ability to use option keys.  I agree that this is likely an unofficial release and buggy.

The recovery software completely reformats flash so it is no problem to use it to go backwards after doing the upgrade.

This is actually not true.  In order to perform a complete erase of the NAND flash, which includes scope ID information and all calibration files stored in NAND, one must rename the _format.bin to format.bin on the SD card.  In order to restore the calibration data, you would need to activate the service mode and restore the calibration data from the EEPROM.  This process, according to Teledyne, constitutes the complete format procedure required to address various problems, including problems with the option keys, and that's the one they recommend.

The original restore package shared in this thread contains _format.bin with the underscore. For kicks and giggles, I tried renaming it to format.bin and running a complete format cycle, but this resulted in an inoperable scope, requiring to perform full restore + format using the new Teledyne restore package.

[kinero]

Were you able to resolve this, and if so, what steps did you take?

[ollopa]

Interesting that Teledyne states that the latest software for WX3000 is V9.2.0.5 while the restore package shared above contained V9.6.0.1, and that's the one that disables ability to use option keys.  I agree that this is likely an unofficial release and buggy.

It might actually be for the upgraded WS3KZ variant (which is up to firmware 10.3.0.2 now). 

Nevermind -- The firmware for the Z is not compatible with the non-Z (the .fla file will be rejected) so it couldn't be that.  Must have been a bad internal build as others have said.

[analogRF]

It is supposed to update the flash block number on the screen as it rewrites the ECC data.  The operation can take a while.
If you don't see the screen updating and you have patiently waited several minutes then there is probably an error it can not automatically fix.

My WS3K still had trouble writing to flash after the recovery.  I had to boot under Linux and erase the NAND flash, then perform the recovery.  Afterwards it has been operating fine.  I don't know if you will lose cal data because mine had calibration issues to begin with.  It was, and in some ways still is, a very sick scope.

If you want serial output you have to disassemble the scope until you have access to the main board, then solder a header or some wires to three pads and connect a 3.3V FTDI or equivalent.  I don't have a picture right now and my scope is partially reassembled so I cannot just go snap one.  If you want to go that far, however, I can pull the shielding back off and take pictures sometime in the next few days.

Hi Ollopa

Do you remember where approximately the serial console header is located on the board?
I scoped almost everywhere but i cannot find any activity.

I have not tried the recovery sd yet

[analogRF]

Hi,

Exact same thing happened to me two weeks ago. I was desperate

Turns out you have to re-flash your scope/run a recovery disk. This is done by the Micro-SD on the back of the file.
I've uploaded you the recovery disk here: https://tmp.yxc.ch/wl/?id=8qaTN2VHKrAbuceZwjrNxd629KcMKVvS
Extract all files on an SD and boot - it will do. After recovery make sure to remove the files again, or it will do a recovery over and over again.

After recovery make sure you update your bios, with the new bios it should not enter an infinite boot loop anymore. You can download the latest firmware here:
https://teledynelecroy.com/support/softwaredownload/documents.aspx?sc=12 ( I also uploaded the latest version for a WaveSurfer 3000 in above link)

Let me know if it worked

Cheers

worked for me too 
thank you so much for this
but I have a question: where did you get MAUI 9.6.0.1? From Lecroy website I can only download 9.2.0.5

I have not attempted 9.6.0.1 yet. I would like someone to confirm that it does indeed work for WS3000

[analogRF]

The WS3K (non-Z) uses the TI DM3730 OMAP3 SoC, for which there is no such thing as a "BIOS".  By watching the serial console output during boot I can see that what this "BIOS" update actually does is upgrade the NAND flash ECC algorithm.  I think they were using the default Hamming correction which can only correct for 1 bit error.  The DM3730 is capable of hardware computed BCH-4 and BCH-8 however the silicon errata says that BCH-4 is completely broken.  I think we can assume they are upgrading to BCH-8.  The MT29F4G16ABBDA3W NAND flash used also has OOB size 64 which is large enough for BCH-8.

The nature of NAND flash is to have a high probability of bit errors and it requires error correction.  I think we can assume that the initial ECC algorithm used was too weak and eventually all scopes will need this recovery process and the "BIOS upgrade" which actually just re-computes NAND flash ECC data.


First boot after confirming the "BIOS  upgrade" (The screen shows four colored squares and updates the block number during each ScreenPrint call logged)

can you please point me to the location of the serial console header on the board. even approximately, I can then located it.
I believe I have scoped all headers but I could not find anything. I thought maybe some pin must be grounded or pulled up 

[analogRF]

I just recovered my WS3024 thanks to the recovery SD card image posted by kendor
I didnt see any 4 color squares on the screen during the restoration, just a blank screen. and it went relatively fast. Faster than what I was expecting

after the recovery I did NOT install the included 9.6.01 but I got the 9.2.0.5 from lecroy and upgraded with that and then the so-called BIOS upgrade
all went ok
However now I have a problem.
As you see in the picture all 4 traces have a red line overlay on them and at higher V/div when noise is not visible and trace becomes thin the red line
completely masks the color of trace so they all look red!! 
unless I STOP the trigger then I can see the actual colors

has anyone seen this problem? there is no place to get rid of that thing. Right after recovery with 8.4.1.5 it looked OK

by the way I can still enter license keys on 9.2.0.5. Good thing I didnt upgrade to the 9.6

[analogRF]

can someone share the 9.1.0.3 firmware?

I think 9.2.0.5 may have a bug. I cannot get rid of that red overlay on traces...scope works fine otherwise
but all 4 traces are red even though at the bottom I have the colored boxes for each channel

EDIT:
Never mind 
I just reloaded 9.2.0.5 two more times and the problem went away.

I suspect having a sd card inserted at the back interfered with updates...Eventhough the software was updated and showed 9.2.0.5 but
I was getting that nasty traces. The last time I tried the the same update I took out the SD card (which I just remembered was there)
and this time unit came back as expected although there was no change in the update process or messages.
weird stuff but seems to be working fine now 

[analogRF]

here are the pictures of the main board of the scope front and back
I have assembled the unit now but I can open it again and try...

I did scope around those marked connectors/headers but I did not see any activity at the time (when the scope was still corrupted)

[analogRF]

this is the back side

[analogRF]

it seems upgrading the BW needs the board to be replaced or the front end be tuned and/or some passives in the front end to be replaced
these scopes had 350MHz,500MHz,750MHz models but I think the board must be the same except changes in the front end under those shields

plus some ID resistors perhaps? because there is no bandwidth license...

[tautech]

However now I have a problem.
As you see in the picture all 4 traces have a red line overlay on them and at higher V/div when noise is not visible and trace becomes thin the red line
completely masks the color of trace so they all look red!! 
unless I STOP the trigger then I can see the actual colors

has anyone seen this problem?

Problem ?
Maybe you never had a DSO with color intensity display before ?

[analogRF]

However now I have a problem.
As you see in the picture all 4 traces have a red line overlay on them and at higher V/div when noise is not visible and trace becomes thin the red line
completely masks the color of trace so they all look red!! 
unless I STOP the trigger then I can see the actual colors

has anyone seen this problem?

Problem ?
Maybe you never had a DSO with color intensity display before ?

I do... quite a few of them

it was indeed a problem....fixed as I explained...

[tautech]

However now I have a problem.
As you see in the picture all 4 traces have a red line overlay on them and at higher V/div when noise is not visible and trace becomes thin the red line
completely masks the color of trace so they all look red!! 
unless I STOP the trigger then I can see the actual colors

has anyone seen this problem?

Problem ?
Maybe you never had a DSO with color intensity display before ?

I do... quite a few of them

it was indeed a problem....fixed as I explained...

Understood.
However one firmware update may boot with color intensity set to ON and in a later version not.

From your pic I instantly spotted color intensity was set to ON when a scope Default or just tuning it OFF should remove it. Did it not ?

[analogRF]

However now I have a problem.
As you see in the picture all 4 traces have a red line overlay on them and at higher V/div when noise is not visible and trace becomes thin the red line
completely masks the color of trace so they all look red!! 
unless I STOP the trigger then I can see the actual colors

has anyone seen this problem?

Problem ?
Maybe you never had a DSO with color intensity display before ?

I do... quite a few of them

it was indeed a problem....fixed as I explained...

Understood.
However one firmware update may boot with color intensity set to ON and in a later version not.

From your pic I instantly spotted color intensity was set to ON when a scope Default or just tuning it OFF should remove it. Did it not ?

No there was no way to remove it anywhere. I have that on my other Lecroy scopes and I can turn it on/off. Besides it is the same FW I reloaded and now it is fixed.
There was something wrong no doubt but dont know how. This FW was developed on Windows xp/7/10 for years and I think when they migrated to wince for this cheap line of scopes they screwed up in some places...

[ollopa]

can you please point me to the location of the serial console header on the board. even approximately, I can then located it.
I believe I have scoped all headers but I could not find anything. I thought maybe some pin must be grounded or pulled up

You have a newer revision of the PCB than I do and I don't see the UART header on yours.  Here is where it is on mine.

[ollopa]

here are the pictures of the main board of the scope front and back
I have assembled the unit now but I can open it again and try...

I did scope around those marked connectors/headers but I did not see any activity at the time (when the scope was still corrupted)

The DM3730 is the CPU.  It is the same CPU used on the BeagleBoard-xM.
The 14-pin header near it which you have circled is the JTAG connector.  It is normally driven by a level converter which is why in my picture you see I have lifted the driver OE pin so I can override it.  I was able to connect with OpenOCD and dump some of the flash but it's incredibly slow and you're better off just booting up Linux if you can find the UART connections.

You can see my FTDI hanging off here and my custom boot screen.

[ollopa]

It's a weak CPU with too little RAM for Maui -- enabling too many options at once causes you to quickly run out of memory.  WinCE / WEC7 is a decent RTOS, I guess, but it's not a very useful environment even if you gain access to it.  I was able to compile and run my own software on the WS3K as well as use the CE remote tools and remote debugger.  Cute but utterly useless.

[analogRF]

Ollopa

WOW! You basically made a new device out of this scope.

yes my board seems different than yours. But if you notice on mine, there is a 5 pin header just above the power button (top left corner of the photo) which yours does not have
On the back of the board next to that pin header says:"MCU 1_5V" whatever that means
My suspicion is that should be the UART but I think I probed that and could not find anything. i have to check again

By the way, does the UART stream flows as soon as you power it on without doing anything?

[ollopa]

By the way, does the UART stream flows as soon as you power it on without doing anything?

Very shortly after powerup there is some bootloader output as it loads the WEC7 kernel and then depending on the boot flags there is some kernel output.  You should see some serial output on a scope immediately.  115200 baud.

[GRA]

I kindly ask for your help to share the firmware with me; you would greatly assist me. On the official Teledyne LeCroy website, the firmware upgrade for the WaveSurfer 3000 oscilloscope version 9.2.0.5 did not approve my registration, and I cannot download the firmware because I am from Ukraine (It's very strange that they didn't ask about the color of my skin  ). Unfortunately, if you don't help me, I'll have to discard the LeCroy WaveSurfer 3000 and switch to an oscilloscope from another company without racism, such as Tektronix or LeCroy.

[tooki]

I kindly ask for your help to share the firmware with me; you would greatly assist me. On the official Teledyne LeCroy website, the firmware upgrade for the WaveSurfer 3000 oscilloscope version 9.2.0.5 did not approve my registration, and I cannot download the firmware because I am from Ukraine (It's very strange that they didn't ask about the color of my skin  ). Unfortunately, if you don't help me, I'll have to discard the LeCroy WaveSurfer 3000 and switch to an oscilloscope from another company without racism, such as Tektronix or LeCroy.

It’s not racism, it’s export controls.

And another company, such as… LeCroy?!?

[2N3055]

I kindly ask for your help to share the firmware with me; you would greatly assist me. On the official Teledyne LeCroy website, the firmware upgrade for the WaveSurfer 3000 oscilloscope version 9.2.0.5 did not approve my registration, and I cannot download the firmware because I am from Ukraine (It's very strange that they didn't ask about the color of my skin  ). Unfortunately, if you don't help me, I'll have to discard the LeCroy WaveSurfer 3000 and switch to an oscilloscope from another company without racism, such as Tektronix or LeCroy.

It’s not racism, it’s export controls.

And another company, such as… LeCroy?!?

Slavic languages form sentences differently. It does not always translate directly.

"Not translates itself directly" is valid structure...

I think he mentions LeCroy and Tek as an example of companies that do export control and therefore which he might avoid.

Translation between slavic languages and English is more like a "explain it in your own words but keep the meaning" activity.