Lecroy wavesurfer 3024 fail to boot

[gkmaia]

Hi,

My Wavesurfer got stuck on a blue screen while trying to boot.

I've uploaded a video on youtube showing the issue.



Also found the scope recovery notes, but seems it do not apply to my as the Wavesurfer does not have a recovery procedure.

Cheers
Gui

[kendor]

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

[gkmaia]

WOW! Thanks Kendor!

Amazing, I will try it right now!

[gkmaia]

I tried and it worked!!! Great tip mate. I really appreciate!

[tautech]

Oh so you nabbed it and you got quite a good scope now it's recovered.
https://www.eevblog.com/forum/testgear/teledyne-wavesurfer-3024-200mhz-oscilloscope-any-good/

Investigations at the time indicated only a LeCroy recovery package would fix it.

[gkmaia]

Investigations at the time indicated only a LeCroy recovery package would fix it.

Did you work with Martin Jet Packs?

I contacted Lecroy. They were quite friendly but did not want to go as far as providing files, etc... I was about to send it to them to fix. The re-flashing disk Kendor provided was the salvation.

Also it has the signal generator extra.

I will get the digital now and it will be a neat piece of equipment.

[tautech]

Investigations at the time indicated only a LeCroy recovery package would fix it.

Did you work with Martin Jet Packs?

No, only had interest in it as our customer Dazz1 that's not too far from you in the Hutt was interested in it and I recognized it as a Siglent rebrand.
Study the thread I linked.

I contacted Lecroy. They were quite friendly but did not want to go as far as providing files, etc... I was about to send it to them to fix. The re-flashing disk Kendor provided was the salvation.

Yes I could get the SDS3000 recovery files from Siglent but after it would have no longer been a LeCroy.
You certainly owe Kendor a beer or 2. 

Also it has the signal generator extra.
I will get the digital now and it will be a neat piece of equipment.

By the looks of the MSO socket the probe is most probably all passives and likely you can find one on EvilBay for not too much.

[tautech]

I will get the digital now and it will be a neat piece of equipment.

I had a vision the MSO probe set was the same as earlier 2k Siglents but no it's a SPL3016.
Scroll down to see it here:
https://www.siglent.com/products-ware/sds3000x/#navs

[heatsystem]

I've got the same problem with boot with WS 3024, MFG Date Sep-2015.
I tried the recovery disk from kendor but it still doesn't boot to UI.

Can someone help?

Thanks for help

heatsystem

[tautech]

I've got the same problem with boot with WS 3024, MFG Date Sep-2015.
I tried the recovery disk from kendor but it still doesn't boot to UI.

Can someone help?

Thanks for help

heatsystem

Welcome to the forum.

Did you format the SD card and have all files in the root ?

[gkmaia]

I've got the same problem with boot with WS 3024, MFG Date Sep-2015.
I tried the recovery disk from kendor but it still doesn't boot to UI.
Can someone help?
Thanks for help
heatsystem

The card I used was the original card and it was formatted as a Master Boot Record. I think this will play a role. Try formatting the card as FAT - MBR. My card root directory looked like the image attached.

[gkmaia]

By the looks of the MSO socket the probe is most probably all passives and likely you can find one on EvilBay for not too much.

Do you know if I require a key to activate the WS3K-MSO function? Or just by sticking probs there it will enable it. I tried pressing the digital button at the front panel and it does not do anything.

WS3K-FG has been included.

[tautech]

By the looks of the MSO socket the probe is most probably all passives and likely you can find one on EvilBay for not too much.

Do you know if I require a key to activate the WS3K-MSO function?

Yes, see the description of the option, it includes the SW license.
Hunt out the Options menu and check what is licensed and if any other options have trial use times remaining.
Don't know if LeCroy offer trial uses but Siglent do 30.

[heatsystem]

The card I used was the original card and it was formatted as a Master Boot Record. I think this will play a role. Try formatting the card as FAT - MBR. My card root directory looked like the image attached.

Thats it: I formatted with diskpart on command-line (clean disk, create partition primary, active, format fs=fat quick), copied all the files, started the WaveSurfer and after some minutes it started as expected!

Thanks to kendor and gkmaia! 

heatsystem

[gkmaia]

By the looks of the MSO socket the probe is most probably all passives and likely you can find one on EvilBay for not too much.

Do you know if I require a key to activate the WS3K-MSO function?

Yes, see the description of the option, it includes the SW license.
Hunt out the Options menu and check what is licensed and if any other options have trial use times remaining.
Don't know if LeCroy offer trial uses but Siglent do 30.

I checked. Has all the decoding options plus the function generator. But does not have the MSO. Still an amazing score for $800!

[peter-h]

I had the same boot problem with a 3034 about 2 years ago; 1 year from new. They fixed it under the warranty, but next time it will be expensive; AFAIK their fixed repair charge is about 1k.

[ollopa]

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)

Lecroy NAND XLDR, Jun 26 2020 at 23:39:17 Version BSP_WINCE_ARM_A8 2.30.00.03...............JMP
Lecroy EBOOT 0.0, BSP BSP_WINCE_ARM_A8 2.30.00.03
TPS659XX Version 0x10 (ES1.1)
>>>>> EBoot Boot Perf timer 1
Preparing for download...
ECC 0
Checking bootloader blocks are marked as reserved (Num = 32). Min:29
IsFlashBlockConfiguredForInternalEccCorrection 4, ff,ff, rc:0

ECC 0
INFO: Boot CFG ... OK
>>>>>Boot configuration Duration 21ms
ECC 0
ECC 0
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
ECC 0
>>>>>LCD.BIN extracted from NAND Duration 71ms
 >>>>>>>spi load fpga start time=93
 >>>>>>>-SPI_WriteRead(rc = 465028)
 >>>>>>>spi load fpga end time=372
>>>>>LCD.BIN written to FPGA Duration 279ms
ECC 0
>>>>>Logo displayed Duration 356ms
>>>>>Partitions checked Duration 0ms

>>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<
>>>>>Reset checked Duration 9ms
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
SDCard: menu.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
SDCard: format.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
SDCard: recovery.bin not found
>>>>>BLShowInitLogo displayed Duration 621ms
ScreenPrint
Reconfiguring flash for 0 to 3 ECC correction
ECC 0
 ReconfigureFlashIntToExtECC - Updating block:4
ScreenPrint
ECC 0
ECC 3
FMD_EraseBlock  4
 ReconfigureFlashIntToExtECC - Updating block:5
ScreenPrint
ECC 0
ECC 3
.
.
.
FMD_EraseBlock  4094
 ReconfigureFlashIntToExtECC - Updating block:4095
ScreenPrint
ECC 0
ECC 3
FMD_EraseBlock  4095
ECC 3
ECC 3
FMD_EraseBlock  5
ScreenPrint
ECC 3
FMD_EraseBlock  5
>>>>>Special files checked Duration 175580ms
>>>>>Logo displayed Duration 0ms
ECC 3
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
BP_SetDataPointer at 0x0
>>>>>OS Image loaded Duration 21960ms
Launch Windows CE image by jumping to 0x81002000...

And then on the next boot post-upgrade:

Lecroy NAND XLDR, Jun 26 2020 at 23:39:17 Version BSP_WINCE_ARM_A8 2.30.00.03...............JMP
Lecroy EBOOT 0.0, BSP BSP_WINCE_ARM_A8 2.30.00.03
TPS659XX Version 0x10 (ES1.1)
>>>>> EBoot Boot Perf timer 1
Preparing for download...
ECC 0
Checking bootloader blocks are marked as reserved (Num = 32). Min:29
IsFlashBlockConfiguredForInternalEccCorrection 4, 3,fc, rc:1
ECC 3

ECC 3
INFO: Boot CFG ... OK
>>>>>Boot configuration Duration 22ms
ECC 3
ECC 3
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
ECC 3
>>>>>LCD.BIN extracted from NAND Duration 82ms
 >>>>>>>spi load fpga start time=105
 >>>>>>>-SPI_WriteRead(rc = 465028)
 >>>>>>>spi load fpga end time=383
>>>>>LCD.BIN written to FPGA Duration 279ms
ECC 3
>>>>>Logo displayed Duration 377ms
>>>>>Partitions checked Duration 0ms

>>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<
>>>>>Reset checked Duration 9ms
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
SDCard: menu.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
SDCard: format.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists:  fileio init failed
SDCard: recovery.bin not found
>>>>>Special files checked Duration 371ms
>>>>>Logo displayed Duration 4ms
ECC 3
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
BP_SetDataPointer at 0x0
>>>>>OS Image loaded Duration 21969ms
Launch Windows CE image by jumping to 0x81002000...

Windows CE Kernel for ARM (Thumb Enabled)
OAL: CPU revision 0x12:DM3730
OAL: CPU L2 Aux register 0x400042
****Profiler Build****
---High Performance Frequency is 26000847 hz---

[eevChrissy]

Hello,

I have similar issue with a WS3024.

After doing recovery, it hangs now in the screen with the 4 colours in each quadrant.
May, I am missing something!?

How can I watch that nice "serial console output during boot"?

And, as a last option, is it possible to recover to a SIGLENT SDS3000? Guess the calibration would be lost...?


Very Best Thanks, for any help!

[ollopa]

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.

[eevChrissy]

@ollopa
Very Best Thanks for that help...

Think, I can open it, and create a serial COM connection over FTDI...

But, right now, I didn't understand the second step...
How to Boot Linux and erase the NAND flash

Thanks for further help... and Best regards

[scopeman]

Hello,

Also you might want to join and post to my LeCroy group on groups.io

Thanks and great to see that your scope is up and running!

https://groups.io/g/LeCroyOwnersGroup

Sam
W3OHM
LeCroy Group Moderator on groups.io
 

[zhongzuocheng520]

According to the recovery method you provided, the recovery can only be performed until the 4-color screen has been waiting and cannot be entered.

[kinero]

Kendor, do you know if you the restore procedure would work on a unit where the BIOS update already took place?

[kinero]

This recovery worked well for my scope, but....after the unit was recovered, the supplied 9.6 firmware was installed, and the BIOS was updated, I noticed two things:

(1) "ADD KEY" button for options does nothing, so I'm not able to add options that I purchased.
(2) can no longer browse system files; only contents of USB DRIVE or SD card are displayed.

I want to perform a factory restore again to see if these problems go away, but I don't know if the updated BIOS would also be rolled back. If not, the system will attempt to run factory firmware on new BIOS which I don't believe will work.

Does anyone know?

[ollopa]

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.

This is an ARM SoC, not x86 architecture.  There is no such thing as a BIOS.  As I explained already, that step is actually changing the error correction algorithm for the NAND flash.  The recovery software completely reformats flash so it is no problem to use it to go backwards after doing the upgrade.

[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.

[bson]

My WS3054 has started acting up again and the micro-SD based recovery doesn't seem to help. It displays the logo and steps through "Upgrading Logo", "Upgrading FPGA", and "Upgrading Boot IMG" (or "Image", forget off hand as I'm typing this); it stops at the latter for 5 seconds or so, then starts over.  I take this to mean it failed and reset.  I've tried both 32GB and 8GB (SDHC) cards, MBR partition tabled, with a single primary partition set to active.  FAT32 with 16k and 8k extents, respectively. (I used diskpart on Win10.)  No dice, both cards behave exactly the same...
The file I have and used is WS3K_ACQ3ND_8.4.1.5.zip

I have a gut feel this means the NAND flash has too many errors for the CRC to be recoverable and it needs to be reformatted (presumably the bad sectors will be replaced).  But if I'm going to do that and go through a complete reformat and reinstall I might be better off replacing them (assuming not super high density BGA).  If BGA there might also be a detached or cracked ball...

Looking for ideas...

[bson]

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

Super belated comment... but yes, 9.6.0.1 is what I have on my non-Z 3054 and it worked great.  I assume you already figured out the answer, but maybe this is of some use to someone else coming across this thread in the future.

[analogRF]

My WS3054 has started acting up again and the micro-SD based recovery doesn't seem to help. It displays the logo and steps through "Upgrading Logo", "Upgrading FPGA", and "Upgrading Boot IMG" (or "Image", forget off hand as I'm typing this); it stops at the latter for 5 seconds or so, then starts over.  I take this to mean it failed and reset.  I've tried both 32GB and 8GB (SDHC) cards, MBR partition tabled, with a single primary partition set to active.  FAT32 with 16k and 8k extents, respectively. (I used diskpart on Win10.)  No dice, both cards behave exactly the same...
The file I have and used is WS3K_ACQ3ND_8.4.1.5.zip

I have a gut feel this means the NAND flash has too many errors for the CRC to be recoverable and it needs to be reformatted (presumably the bad sectors will be replaced).  But if I'm going to do that and go through a complete reformat and reinstall I might be better off replacing them (assuming not super high density BGA).  If BGA there might also be a detached or cracked ball...

Looking for ideas...

by "again" you mean you had done recovery before and it had worked for a while?

I think formatting the flash should fix it. In case you want to replace it, the FLASH chip is MT29C4G96MAZBACKD-5 (marking JW732)
but the board is HUGE and very thick, so personally I dont have the courage to replace that chip frankly 

[bson]

by "again" you mean you had done recovery before and it had worked for a while?

I think formatting the flash should fix it. In case you want to replace it, the FLASH chip is MT29C4G96MAZBACKD-5 (marking JW732)
but the board is HUGE and very thick, so personally I dont have the courage to replace that chip frankly 

Yeah, got stuck in a boot loop before and I restored it back to working order.  This was about a year ago.

Will I need anything else other than rename '_format.bin' to 'format.bin'?  I see there's a 182MB file there (LecroyNK.up), is this some sort of compressed package file?  Or do I need some sort of separate installer or packages afterwards?

Also, if it's self-contained, which I assume it is - will it also recover the S/N, licenses and cal data from a more reliable or duplicate record?  If so I would guess it reverts to factory defaults plus licenses, so will need at least an auto cal.

And, yeah, I'd rather not start replacing chips.  But a 0.5mm QFP isn't a big deal, it's just fine-pitch BGAs that I've had mixed results with.

BTW, I'm astonished this scope is powered by a 1GHz Cortex-A8 from 2011, with its firmware fitting in something like a 185MB archive, even if compressed... simply astonishing.

[analogRF]

Will I need anything else other than rename '_format.bin' to 'format.bin'?  I see there's a 182MB file there (LecroyNK.up), is this some sort of compressed package file?  Or do I need some sort of separate installer or packages afterwards?

Also, if it's self-contained, which I assume it is - will it also recover the S/N, licenses and cal data from a more reliable or duplicate record?  If so I would guess it reverts to factory defaults plus licenses, so will need at least an auto cal.

And, yeah, I'd rather not start replacing chips.  But a 0.5mm QFP isn't a big deal, it's just fine-pitch BGAs that I've had mixed results with.

BTW, I'm astonished this scope is powered by a 1GHz Cortex-A8 from 2011, with its firmware fitting in something like a 185MB archive, even if compressed... simply astonishing.

yes just change to format.bin.
you will lose cal data and S/N and options. must be restored from EEPROM from the service menu (PW 9472) /BTD calibration/ restore BTD from EEPROM

[bson]

yes just change to format.bin.
you will lose cal data and S/N and options. must be restored from EEPROM from the service menu (PW 9472) /BTD calibration/ restore BTD from EEPROM

Tried it; still no go.  It adds a FORMAT step on boot, but then still resets on Boot IMG Update...

Starting to think something is truly borked, will have to take it apart and check if there's anything on the console output.

[analogRF]

yes just change to format.bin.
you will lose cal data and S/N and options. must be restored from EEPROM from the service menu (PW 9472) /BTD calibration/ restore BTD from EEPROM

Tried it; still no go.  It adds a FORMAT step on boot, but then still resets on Boot IMG Update...

Starting to think something is truly borked, will have to take it apart and check if there's anything on the console output.

that doesn't sound good. Usually the formatting should have fixed it. Please keep us posted on your findings. At this point it seems like a bad NAND flash chip
debug boot record should be very helpful.

it may not be important but Lecroy specifically says after you clean and format the SD card (fat32) first copy the MLO file on to the root of SD and then copy the rest of the files next to it. I dont know why that should be important but maybe you want to keep that in mind too

[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?!?

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.

Translation is the art of taking a text in one language and rewriting it in another language, such that it is understandable to the reader of the target language. It’s always “in your own words” because it has to be. Taking a sentence in one language and replacing its words with the equivalent words of the target language (without rearranging, adapting to grammar, etc) is not translating, it’s just word-by-word transliterating, and is typically useless. Every proper translation is a rewording. Source: I used to work as a translator. (And I studied linguistics at university.)

None of what you said has anything to do with translation, though. A person’s native language will influence what mistakes they make when speaking or writing a foreign language. (I have so much experience with German and its native speakers that I have become quite adept at decoding what they mean when they write broken English, for example.) With that said, I don’t know any Slavic languages so I can’t “decode”, so I have to take what is written at face value. With that said, I don’t think the issue here was a language barrier, but a slip-up: I assume they meant to write “…Tektronix and [Keysight or R&S or Rigol or Siglent]”.

[bson]

the FLASH chip is MT29C4G96MAZBACKD-5 (marking JW732)

It's also totally obsolete and finding one requires going fishing on the various scam markets.  It's a 137 pin BGA, which isn't too bad, but I'd rather not go through 5 to find one that is the genuine article!  Being BGA I'd also want to reball with leaded solder paste.

Debating whether to bother with this or to sell it for parts...  I might take the board out to take a look at the other side to see if I can put it on a heater - but I suspect it's going to have a bunch of passives on the opposite side that would need to come off first for that.

[analogRF]

the FLASH chip is MT29C4G96MAZBACKD-5 (marking JW732)

It's also totally obsolete and finding one requires going fishing on the various scam markets.  It's a 137 pin BGA, which isn't too bad, but I'd rather not go through 5 to find one that is the genuine article!  Being BGA I'd also want to reball with leaded solder paste.

Debating whether to bother with this or to sell it for parts...  I might take the board out to take a look at the other side to see if I can put it on a heater - but I suspect it's going to have a bunch of passives on the opposite side that would need to come off first for that.

were you able to find a UART debug port and look at the boot record?